[client21]

PHP Code:

stock X(v[])
{
    static key = 0;
    if (!key) key = 1;
    
    v[0] += key;

    PrintToServer("%d", v[0]);
}

public OnPluginStart()
{
    xz();
    xz();
    xz();
}

stock xz()
{
    X({2});
} 


Result:

3
4
5

What?

[Powerlord]

I haven't looked up how SourceMod handles array literals, but chances are it's converting it into either a static or global array variable.

[klippy]

The array literal {2} should be const and the compiler shouldn't allow you to pass it as a non-const parameter. Most likely a bug.

[client21]

PHP Code:

new Handle:hPack = CreateDataPack();
WritePackCell(hPack, 1);
WritePackCell(hPack, 2);
    
ResetPack(hPack);
PrintToServer("%d\n%d", ReadPackCell(hPack), ReadPackCell(hPack)); 


Result:

2
1

SM, you seriously again yes?
Omg.. Where logic in this world..

[client21]

SDKHooks_TakeDamage too stupid..

SDKHooks_TakeDamage(client, 0, owner, 99.0, DMG_BLAST); // client have 1 hp, ok work
SDKHooks_TakeDamage(client, 0, owner, 100.0, DMG_BLAST); // client have 27 hp, nice SM, nice

[klippy]

Originally Posted by client21 PHP Code: new Handle:hPack = CreateDataPack(); WritePackCell(hPack, 1); WritePackCell(hPack, 2);      ResetPack(hPack); PrintToServer("%d\n%d", ReadPackCell(hPack), ReadPackCell(hPack));  Result: 2 1 SM, you seriously again yes? Omg.. Where logic in this world..

You will find it working the same way in many languages. It's a common practice that parameters are pushed onto the stack in reverse order. Even C language does that. If you expect something to be done in specific order, don't do it within the function call.

Originally Posted by client21 SDKHooks_TakeDamage too stupid.. SDKHooks_TakeDamage(client, 0, owner, 99.0, DMG_BLAST); // client have 1 hp, ok work SDKHooks_TakeDamage(client, 0, owner, 100.0, DMG_BLAST); // client have 27 hp, nice SM, nice

You should post more code if you expect to whine about something and want it fixed in case it's a bug. Also given that it's a SDKHooks call and something is wrong indeed, it most likely isn't SM's fault.

[client21]

Originally Posted by KliPPy You should post more code if you expect to whine about something and want it fixed in case it's a bug. Also given that it's a SDKHooks call and something is wrong indeed, it most likely isn't SM's fault.

You should understand that publishing more code does not make sense, since I gave all the key information. If you do not understand it, this is your problem. Yes, this is a very important remark, sdkhooks is guilty, not SM.

[klippy]

Originally Posted by client21 You should understand that publishing more code does not make sense, since I gave all the key information. If you do not understand it, this is your problem. Yes, this is a very important remark, sdkhooks is guilty, not SM.

It absolutely makes sense, the context in which you call the function matters. To prove that there is a bug one must be able to replicate it. Also any additional information like what game it is, OS etc. would help resolve the issue if there's truly any.
What I meant is that SDKHooks doesn't care at all what value you passed to it, it doesn't differentiate between 99.0 and 100.0 and take action depending on what value it is, it just forwards it to the game AFAIK.

[Fyren]

The order parameters get pushed to the stack and the order of evaluation of function arguments don't have to be the same, though being the same is simpler. Pawn doesn't define the order of evaluation (and isn't the only language to not define it), though most do define it as left to right.

For SDKHooks_TakeDamage, it's more likely the black box that is the game is doing whatever it is that's weird.

[Powerlord]

For the TakeDamage part, if this is one of the Counter-Strike games, did either player have armor?