Script protection and modding

#1 Yes, when you run your game all your *.cs files are converted to *.dso. These *.dso files are encrypted, so they cannot be edited by other people unless you give them the *.cs files.

So when you release your game, simply package the *.dso files and not the *.cs ones. That will prevent anyone from doing any modding.

#2 Thanks Matthew,
those *.dso are in some kind of bytecode i suppose.
so there shouldn't be a big penalty interpreting them, right?
any hints on what parts of the game better be implemented 'natively'
(i'm thinking on a rts multiplayer game)

#3 How about protecting the assets? Ogg's, png's and jpgs for example? Also can DTS and DIF's be reverse engineered?

#4 Any asset that has a "functional" base (or not depending on popularity of the asset or game in question) can be reverse engineered. Whether it be by someone who is used to dealing with binary formats (say a traditional database programmer who has made their way in translating singular codification systems to modular ones...much like very many high paying companies desire...and which many educational facilities try to precipitate).

Anything can be hacked depending on the availability of resources and desire.

One has to acknowledge and evaluate their propensity for "being hacked" or "cracked" or whatever one wants to call it at the time.