removing editing functionality for GameBuild

#1 Well, you can disable the fn keys. That's a first step.

Then, you could make stub scripts for the current editors. That pretty much takes care of that side of the issue.

Of course, if the base code is still in the app, if someone had the editors/scripts and hooked their own fkeys up, well, c'est la vie. Not much you can do at that point.

If you're just trying to prevent accidental/incidental editor use, just the fkeys would be enough.

d

#2 "stub script"?

#3 I think by stub scripts he just means mostly empty scripts that do nothing in place of the current editor scripts.

#4 gotcha. on another note..

How do you package up a game or game build? Meaning, someone dloads and they don't get to see all my script etc...

#5 Only provide the .dso compiled scripts with your game, not the .cs files.

#6 You can delete all the *.cs files as long as you leave the *.dso files. The one file you must leave is the main.cs in the root dir of your game I believe. Also I think you can make your game's data directory in a zip file of the same name (like "fps" or "rw"), but I believe this was broken at some point and I don't know if it was ever fixed (probably was, it's been months since I've checked).

edit: argghhh you beat me to it James... barely, barely... ;)

#7 I'll probably ask again when that time comes...was just checkin...you were very close ben...very very close.

#8 Zip files work fine. You must remember that the zip file name becomes a folder in the path.

So if you have a zip file namded foo with a folder named bar containing a file named main.cs stored in the example directory the path to main.cs would be:

/example/foo/bar/main.cs