[GoD-Tony]

Originally Posted by Afronanny I'll have to think about the best way to implement this, seeing as array members can consist of any of the other types. Additionally, what if you only wanted to proxy one of the array members?

Maybe you could allow the current hooks to handle array members directly (similar to the 'element' param in GetEntProp). As long as individually hooking the entire array wouldn't be a problem then that could work. The element could then be in the callback for ease of use.

[Afronanny]

Originally Posted by GoD-Tony Maybe you could allow the current hooks to handle array members directly (similar to the 'element' param in GetEntProp). As long as individually hooking the entire array wouldn't be a problem then that could work. The element could then be in the callback for ease of use.

What I'm trying is doing hooks by offset, as opposed to SendProp name. For instance:

PHP Code:

new offset = FindSendPropInfo("CTFPlayer", "m_bPlayerDominatingMe");
    SendProxy_HookByOffset(client, offset + 4, Prop_Int, ProxyCallback); 


The only problem with this is sometimes it cannot find the prop located at that offset.
ducks

[Afronanny]

Updated (1.0.9):

Added support for hooking array props.

PHP Code:

native bool:SendProxy_HookArrayProp(entity, const String:name[], element, SendPropType:type, SendProxyCallback:callback); 


ducks

[GoD-Tony]

Originally Posted by Afronanny Updated (1.0.9): Added support for hooking array props.

Thanks! Going to test this soon.

if (params[1] < 0 || params[1] > 2048)
{
	return pContext->ThrowNativeError("Invalid Edict Index %d", params[1]);
}

Should that be > 2047?

[Afronanny]

Originally Posted by GoD-Tony Should that be > 2047?

Perhaps.
ducks

[Zephyrus]

Originally Posted by GoD-Tony Thanks! Going to test this soon. if (params[1] < 0 || params[1] > 2048) { return pContext->ThrowNativeError("Invalid Edict Index %d", params[1]); } Should that be > 2047?

or >= 2048

[zeroibis]

So from what I understand this allows us to change the netprops of an entity without the server being aware of the changes. For example in your example the client's team is changed but to the server the client's team was not changed. Thus the client would if ff was off be able to kill (from the servers prospective) their own team but not the other while having the same model and appearing on the same team the server thinks they are on?

Is my understanding of how this works correct? Also is their any particular advantage to modifying the entities without the actual server being aware of the changes such as performance ect?

I run a server for war3 so I am looking for anything that may give me the ability to create cool abilities or ways to reduce load for existing ones.

[Afronanny]

Originally Posted by zeroibis So from what I understand this allows us to change the netprops of an entity without the server being aware of the changes. For example in your example the client's team is changed but to the server the client's team was not changed. Thus the client would if ff was off be able to kill (from the servers prospective) their own team but not the other while having the same model and appearing on the same team the server thinks they are on? Is my understanding of how this works correct? Also is their any particular advantage to modifying the entities without the actual server being aware of the changes such as performance ect? I run a server for war3 so I am looking for anything that may give me the ability to create cool abilities or ways to reduce load for existing ones.

That is correct. It only changes the value sent to all clients, not the value on the server.
ducks

[KyleS]

While I realize this is just for hooking the sending of props, is there any chance you can add the ability to hook prop changes to this? ie hook a change to m_iTeamNum.

Why? Just trying to not have it check every frame if something has changed then going from that. The amount of calls each hook goes through is a bit over the top.

[Afronanny]

Originally Posted by KyleS While I realize this is just for hooking the sending of props, is there any chance you can add the ability to hook prop changes to this? ie hook a change to m_iTeamNum. Why? Just trying to not have it check every frame if something has changed then going from that. The amount of calls each hook goes through is a bit over the top.

That can be done, yes. However, checking if it has changed every frame is the only way to detect if the value has been changed or not.
ducks