Product Release

#1 What files to send... Well, using starter.fps as an example (assuming starter.fps was your game) you would give them the example directory with the starter.fps directory inside it. Anything in higher level directories than example can be ignored. The various other example games that have nothing to do with yours can be deleted.

You can delete any file ending with .cs because the .dso files can do their job. Make sure you actually play your game once after the last time you edited a cs and before you start deleting so that the dso files will be generated. This will generally prevent users from messing with your scripts, though it is theoretically possible to use a .cs to create a .dso.

Your other issue, about users making servers... How would they do that? Is it a commandline option? Is it a button they press in your gui? Whatever it is, find it in script and remove it so they don't have that option anymore.

The things I mentioned will stop casual hacking of your game. Are you looking to put some effort into stopping more determined hacking as well?

#2 I don't know what you're talking about in regards to users making servers, didn't mention anything about that.

Thanks for the help on the rest!

#3 "Keeping in mind, that the distribute version will only have client side functionality."

#4 "Keeping in mind, that the distribute version will only have client side functionality."

That means they can only function as a client. It wasn't a question, it was a statement letting people know that I only needed to distribute client side code.