Luigi Auriemma

hi,
Just a quick question :
Which arguments and which calling convention to use to call this function from CPP code,


Thanks :)

it should be __cdecl

in fact usually it's often __cdecl except the Windows APIs and some rare cases.
for example some hours ago I was taking a look to the SteamUser function of steam_api.dll where it returns a structure where is located also a pointer to a function then used by the main program to get the path of "userdata".

well in this case I needed to wrote a proxy dll for doing a test (curiosity without a purpose... ah freetime) and found that while all the exported functions in steam_api.dll must be __cdecl the internal one which gives the path of "userdata" must be __stdcall (aka WINAPI) otherwise the stack says bye bye

ok, I've tried the calling convention, but I think that my code is not correct.
I'm not an assembly expert, so here come your handy help.
I've located where a player is added to the list on the server assembly, and I think that protocol is not handled by this "player list" (connections are handled elsewhere and associated with a player?)
So, I want to connect a "ghost" on the server, yes, that do nothing but idle on the server and no connection behind that player.
Here from OllyDBG, a calling sample

the parameters seem to be a pointer to a std::string or a C$tring containing the player name and a dword that appear to be always 0
Hmmm, is it depending from others value from the stack than these?

uhmm if you want to add the ghost isn't simpler to add the missing packets to bf2fp?
because I have not understood how you want to call or reach that function.

post what follows after call. if there is addition to esp, then this is cdecl. if theres no addition, its prolly stdcall.

also you can check inside callin function what it does with stack. you can read differences between stdcall, cdecl, fastcall on wiki.