This tutorial is based on my ISO modding guide and goes more in-depth about the actual coding and file structure.
Code units are grouped into fast files (.ff) with different .gsc files which contain source code in a C-like scripting language similar to classes in Java or structs in C. In order to read .ff files and/ or modify their .gsc files one requires the program FF Viewer.
Okay, which one do we modify?
The maps/mp/gametypes/_rank.gsc file contains the onPlayerSpawned() thread, so it's a good candidate for injecting some mods. Use CTRL + F to find the snippet. It should look like this...
Commands
In order to know which commands or console names exist, simply look through some .gsc files or check out some mods or posts on the Internet. Also take a look at this scripting wiki.
Let's use the following...
Let's go ahead and add it to our .gsc file. It should look like this:
Comments
Once finished with the code make sure the file size is equal to before and save. In order to gain space, delete some unnecessary code like comments. In order to fill up space, add comments with e.g. containing gibberish like this:
Note that for editing .gsc files, basic text editors like Notepad++ can be used instead:
Tutorial
Have fun
Code units are grouped into fast files (.ff) with different .gsc files which contain source code in a C-like scripting language similar to classes in Java or structs in C. In order to read .ff files and/ or modify their .gsc files one requires the program FF Viewer.
Okay, which one do we modify?
The maps/mp/gametypes/_rank.gsc file contains the onPlayerSpawned() thread, so it's a good candidate for injecting some mods. Use CTRL + F to find the snippet. It should look like this...
Commands
In order to know which commands or console names exist, simply look through some .gsc files or check out some mods or posts on the Internet. Also take a look at this scripting wiki.
Let's use the following...
- Code:
self giveWeapon("ak47_mp", 0, 0);
Let's go ahead and add it to our .gsc file. It should look like this:
Comments
Once finished with the code make sure the file size is equal to before and save. In order to gain space, delete some unnecessary code like comments. In order to fill up space, add comments with e.g. containing gibberish like this:
Note that for editing .gsc files, basic text editors like Notepad++ can be used instead:
Tutorial
Have fun