.
by Unlisted · in Torque Game Engine · 05/22/2006 (1:50 pm) · 7 replies
.
#2
Why not just eliminate any and all script references to f10 and f11. Then, when you distribute your game with only the pre-compiled scripts (in .dso format), those editor functions will no longer be available. You should be able to find those references in editor.cs and EditorGUI.cs.
Just off the top of my head, that should be the easiest non-C++ way to solve the problem. Haven't tried it myself yet though. :)
Aaron E.
05/22/2006 (4:04 pm)
Pload,Why not just eliminate any and all script references to f10 and f11. Then, when you distribute your game with only the pre-compiled scripts (in .dso format), those editor functions will no longer be available. You should be able to find those references in editor.cs and EditorGUI.cs.
Just off the top of my head, that should be the easiest non-C++ way to solve the problem. Haven't tried it myself yet though. :)
Aaron E.
#3
05/23/2006 (10:14 am)
. 
#4
i think Manoel probably meant the .gui files, not .cc files.
ie, i think common/editor.
05/23/2006 (10:21 am)
Pload,i think Manoel probably meant the .gui files, not .cc files.
ie, i think common/editor.
#5
05/23/2006 (10:25 am)
.
#6
I'm afraid you'll have to dig down all those includes (and derivated code, like anything which touches smEditorHandle) and fix/comment them out.
But maybe you can simply break the editor code to stop it from working, without breaking the rest of TGE. Maybe you can get away by commenting out the contents of most major methods in important GUI controls like GuiEditCtrl, GuiInspector and such.
Since you're concerned about security, you should also try to prevent users from messing with the missions in other ways. You should remove the console too, since they could use it to modify and ssave the mission without problems, and I strongly suggest using the encrypted zip stuff, since someone could simply replace a GUI or a minor CS file and add code to modify the mission or something.
05/23/2006 (10:46 am)
Pload, I haven't done it myself, but after doing a few quickk searches on the source, I notice there are some other GuiControls and classes which include some of the headers in the gui/editor folder. guiControl.cc itself includes guiEditCtrl.h.I'm afraid you'll have to dig down all those includes (and derivated code, like anything which touches smEditorHandle) and fix/comment them out.
But maybe you can simply break the editor code to stop it from working, without breaking the rest of TGE. Maybe you can get away by commenting out the contents of most major methods in important GUI controls like GuiEditCtrl, GuiInspector and such.
Since you're concerned about security, you should also try to prevent users from messing with the missions in other ways. You should remove the console too, since they could use it to modify and ssave the mission without problems, and I strongly suggest using the encrypted zip stuff, since someone could simply replace a GUI or a minor CS file and add code to modify the mission or something.
#7
05/24/2006 (9:26 pm)
. 
Associate Manoel Neto
Default Studio Name
But you also must make sure the players cannot simply open the .MIS file in a text editor and change it directly. You could use the encrypted zip resource.