Game Development Community

How to merge the starter FPS into the common.

by Ryan Mick · 07/04/2005 (2:08 pm) · 28 comments

1. Make a copy of your example directory. Place this copy any where you like,
I placed mine in my torque directory (c:\torque). I renamed the folder FPS.

2. Replace the root main.cs with the one included. The modifications are
simple but would take too long to list out. Basically all I did was to
merge the root main with the Starter.Fps main.


3. Next copy the Starter.Fps/client directory to the common directory.

4. Copy Starter.Fps/data to common.

5. Copy Starter.Fps/server to common.

6. Modify the common/main.cs file with the following:
a. Function initBaseClient, remove:
i. exec("./editor/editor.cs"); and
exec("./editor/particleEditor.cs");

ii. The reason for removing these lines is because we
will be implementing the editors as a mod. That way
deploying the finished game will be easier.

b. Remove the common package section, we don
Page«First 1 2 Next»
#21
07/22/2005 (6:21 pm)
Thanks for posting this. I've been wanting to do this to solve some various chicken and egg problems associated with changing guiprofiles and whatnot. Saved me a lot of time.
#22
12/12/2005 (11:44 am)
This is sticky worthy, if the boards supported that feature. I've been trying for a bit to articulate why I needed this -- separating the engine from the editors -- and getting a proper build env working. Thanks very much for this.
#23
12/12/2005 (2:36 pm)
Glad I could help.
#24
03/16/2006 (3:18 am)
Hello! Sorry to ask but I am new to Torque... what is this for and why should one do it? Does it allow a client to edit the game world on a dedicated server or something?
#25
03/16/2006 (7:07 am)
Dennis, what this did was take all the files from the starter.fps and the common directory and merge them into one directory. That way you have only one place to look for all your functions. It also split out the editors into it's own folder so that they could be used as a mod. That functionality is already in 1.4 so you can ignore that part of the instructions. I haven't tried to implement this in 1.4 yet so I'm not sure if the instructions need to be updated for the rest of it.
#26
05/05/2006 (12:24 pm)
nice work!
thanks.
#27
08/20/2007 (11:09 pm)
THANK YOU SO MUCH!!!

this saved me so much time!!!

Nate
#28
12/26/2007 (11:38 pm)
IT WOULD BE USEFUL if it didnt cut the text off on step ii !
Page«First 1 2 Next»