Spring RTS Engine

I am working on a (yet another) lobby client, please take a look at this post at ZK forums. In my second post in that thread i provided some details about the technical background. For now this was just a spike solution to test some things i read about but couldn't use in my job and to gain skills i...

A sentence following a word is therefore separated by space. This 'therefore' didn't crossed my mind :) It seems like sentences are used for values containing spaces (strings like messages, engine names, titles, etc.) while all other data types are transmitted as words. The different separators mak...

The protocol description says {} = sentence = several words (at least one!) separated by space characters {} {} ... = two or more sentences. They are separated by TAB characters. words are always separated by space characters. As an example here is the syntax of BattleOpened command: BATTLEOPENED ba...

Hello everyone, what happened to that documentation? If i read the thread correctly, it was documented at some time? The protocol description currently doesn't include BATTLEOPENEX. Also, the 'eb' flag isn't mentioned in the comatibility flags list. BATTLEOPENED contains the following: Sent by the s...

Perfect! Thank you very much, this is exactly what I was looking for.

(And yes, wonderful docs!)

Hello everyone - maybe this is a dev topic but as mapconv fixing is discussed here, too:
Is it possible to get the -x and -n params used during compile of a map with mapconv from a map file (smf inside an sd7)? Are they somehow extractable?