Any Tips etc. for those new to making mods?
Moderator: Moderators
-
- Recruit Womprat Killer
- Posts: 5
- Joined: Sat Jan 06, 2018 2:45 am
- Projects :: No Mod project currently.
- xbox live or psn: No gamertag set
Any Tips etc. for those new to making mods?
I am new to making mods in BF2 and want all the help i can get do you have any links,sites,discords,videos,or tips that would help any and all beginners in creating mods for SWBF2?
-
- Private First Class
- Posts: 80
- Joined: Thu Sep 01, 2016 3:41 pm
- Projects :: Tatooine - Jundland Wastes
- xbox live or psn: No gamertag set
Re: Any Tips etc. for those new to making mods?
You know what, I actually never thought of the idea of a modding Discord. If one doesn't already exist perhaps that's something Gametoast or one of us should consider making. As for your other questions, there are links in the FAQ / Everything You Need Thread.
-
- Recruit Womprat Killer
- Posts: 5
- Joined: Sat Jan 06, 2018 2:45 am
- Projects :: No Mod project currently.
- xbox live or psn: No gamertag set
Re: Any Tips etc. for those new to making mods?
Thank you very much
-
- Resistance Leader
- Posts: 5042
- Joined: Tue Feb 09, 2010 8:43 pm
- Projects :: DI2 + Psychosis
- xbox live or psn: Marth8880
- Location: Edinburgh, UK
- Contact:
Re: Any Tips etc. for those new to making mods?
http://www.gametoast.com/viewtopic.php?f=17&t=33389mrcluster wrote:You know what, I actually never thought of the idea of a modding Discord. If one doesn't already exist perhaps that's something Gametoast or one of us should consider making.
- EasyOvenOperator
- Private Recruit
- Posts: 23
- Joined: Thu Nov 16, 2017 12:03 am
- Projects :: No Mod project currently.
- xbox live or psn: No gamertag set
Re: Any Tips etc. for those new to making mods?
don't be so autistic. focus on one thing and then test that one thing you change/modify.
i'm sure most people are responsible in that manner, but i've always had the issue of modding one thing (unit or weapon), just to have an idea jump to mind and changing multiple things before i test the mod to make sure it works. which will put you in the situation of having to work backwards trying to figure out exactly what it could be causing an issue.
munge often, test often.
i'm sure most people are responsible in that manner, but i've always had the issue of modding one thing (unit or weapon), just to have an idea jump to mind and changing multiple things before i test the mod to make sure it works. which will put you in the situation of having to work backwards trying to figure out exactly what it could be causing an issue.
munge often, test often.
-
- Resistance Leader
- Posts: 5042
- Joined: Tue Feb 09, 2010 8:43 pm
- Projects :: DI2 + Psychosis
- xbox live or psn: Marth8880
- Location: Edinburgh, UK
- Contact:
Re: Any Tips etc. for those new to making mods?
Work iteratively - don't just make a single change and go with it if it's not 10000000% exactly how you want it to be. If it's even a little bit off, keep on making changes until it's exact.
Break down large, complex tasks into small pieces so they're easier to manage, quantify, and complete. For example, if you want to create, say, a Clone jet trooper from scratch (admittedly not the best example of a large, complex task), that could be broken down into the following sub-tasks:
Set up source control for your project, *especially* if there's more than one person working on the project. That way you can always go back to any changelist at any time, which is especially useful if you ever run into issues that you absolutely cannot seem to nail down. For SWBF2 modding, I personally recommend using Subversion for your SCM provider, TortoiseSVN for the shell application,
VisualSVN Server for your server solution, and then hosting the server and repository on a separate, newer hard drive (or in the cloud if possible) for your hosting solution. At some point I'm going to create a tutorial on how to do all of this.
In case you're unfamiliar with what exactly source control *is*:
Break down large, complex tasks into small pieces so they're easier to manage, quantify, and complete. For example, if you want to create, say, a Clone jet trooper from scratch (admittedly not the best example of a large, complex task), that could be broken down into the following sub-tasks:
- Create art assets
- Unit character
- Mesh
- Textures
- EMP Launcher weapon
- Mesh
- Textures
- Commando Pistol weapon
- Mesh
- Textures
- Unit character
- Create ODFs
- Unit class
- EMP Launcher weapon
- Weapon class
- Ordnance class
- Ordnance explosion class
- Commando Pistol weapon
- Weapon class
- Ordnance class
- Create particle effects
- Jetpack exhaust effect
- FX config file
- Particle textures
- EMP Launcher ordnance trail effect
- FX config file
- Particle textures
- EMP Launcher ordnance explosion effect
- FX config file
- Particle textures
- Commando Pistol ordnance impact effect
- FX config file
- Particle textures
- Jetpack exhaust effect
- Update REQ files
- Create sub-REQ for unit class
- Add entry for sub-REQ to REP side's REQ file
- Add entries for particle effects to side or ingame REQ file
- Jetpack exhaust effect
- FX config file
- Particle textures
- EMP Launcher ordnance trail effect
- FX config file
- Particle textures
- EMP Launcher ordnance explosion effect
- FX config file
- Particle textures
- Commando Pistol ordnance impact effect
- FX config file
- Particle textures
- Jetpack exhaust effect
- Create sub-REQ for unit class
- Update mission scripts
- <mission script for each applicable map/era/mode combination>
- Add entry for unit's sub-REQ to side's ReadDataFile section
- <mission script for each applicable map/era/mode combination>
Set up source control for your project, *especially* if there's more than one person working on the project. That way you can always go back to any changelist at any time, which is especially useful if you ever run into issues that you absolutely cannot seem to nail down. For SWBF2 modding, I personally recommend using Subversion for your SCM provider, TortoiseSVN for the shell application,
VisualSVN Server for your server solution, and then hosting the server and repository on a separate, newer hard drive (or in the cloud if possible) for your hosting solution. At some point I'm going to create a tutorial on how to do all of this.
In case you're unfamiliar with what exactly source control *is*:
Last edited by Marth8880 on Thu Aug 02, 2018 7:18 pm, edited 1 time in total.
-
- Lieutenant Colonel
- Posts: 545
- Joined: Mon Jul 04, 2016 10:56 pm
- Location: My other account
- Contact:
Re: Any Tips etc. for those new to making mods?
As said there, testing is vital. Play test your mod/map a lot. You COULD see it as slacking off and playing, but you`re playing your mod, and the only way to find bugs/glitches is to play test it. Sometimes these bugs/glitches are very well hidden, so before you release a mod to the public and THEY discover these problems, make sure you play it enough so YOU discover them first, then you can fix them, and the public will praise your mod for being so polished ^_^EasyOvenOperator wrote:... munge often, test often.