kremsy wrote:I just think it can get sometimes weird [...] if the Method names are differing from the official DedicatedServer Method names
imo the dedi-api is an interface to the dedi and not a framework that does additional logic
Then we should:
- add all the *ToId or *Id methods
- split methods which automatically calls the *ToLogin variant when a player/login is provided, something chatSend and chatSendServeMessage were already doing (but there are lots of other cases where it's done)
- remove structures classes
- remove callVoteKick, callVoteBan, callVoteNextMap, callVoteRestartMap, writeFileFromFile and tunnelSendDataFromFile methods which doesn't exist at all in the official API
Imo, if people want to use only the "official" methods then they don't need the Connection class and should use only the Xmlrpc classes. The Connection class is here to help by providing documentation and autocompletion while coding but also by adding this additional logic when you don't want to bother with similar method names doing almost the same thing.
Thanks to additional logic, there are around 250 methods in the Connection class (excluding those which aren't making call to the dedicated, like factory and such) compared to the almost 300 from the official API. I don't understand why you're suddenly worried about differing method names while there were already tens of them that you weren't complaining about...
Edit: about unpack, whatever the time it takes, there are no other function anyway.
Edit2: and it really is 5ms in your screen, it's a dot not a comma.