Guide for lobby development

here

dropped sound effects because i realized it was so insignificant atm that it really didnt matter.

Sounds are the single most important thing holding zerok back from becoming the worlds premier eSport.

Short notes for installing Visual Studio here

Other than that, your only real guide is to read the source and ask on forum or in #zkdev if you get stuck. What do you plan on doing in particular?

[BM]Parzival your question is an equivalent to sending a letter to NASA with a request for them to send you a space rocket building instructions because you want to go into space.

Your best option is to reverse engineer the code and ask other lobby devs such as ikinz, Car Repairer, Licho and cleanrock about particular parts of the code but don't expect for any of them to write you a manual.

OK, thanks guys. And I already have KSP, no worries there.

"Your best option is to reverse engineer the code and ask other lobby devs such as ikinz, Car Repairer, Licho and cleanrock about particular parts of the code but don't expect for any of them to write you a manual. "

Allow me to tranlate this for you.

"We pretend to ask for help from people to allow this game to be further developed but in secret we harbour an elitist mentality and resent additional help. Don't expect us to make this easy for you."

Do you have a GitHub account? I would suggest you start with making an account, and installing git first.

If you are on windows: https://windows.github.com/
Also as was previously mentioned, Visual Studio for editing code: https://www.visualstudio.com/
It is possible to develop without these tools, but why?

Linux has similar equivalents, (eg. the command-line git and mono-develop).

Once you've got that all set up, you can download the source for the ZK Infrastructure project: https://github.com/ZeroK-RTS/Zero-K-Infrastructure.git
(try reading some git tutorials if you're unfamiliar how this works)

A list of known, outstanding issues are here:
https://github.com/ZeroK-RTS/Zero-K-Infrastructure/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen

But you don't have to limit yourself to those either. There are several things that are not documented, but still need improving. If you come across something that looks bad, or doesn't work, feel free to figure out why and fix it.

Also, apparently its all coded in c#?