[Guide] GSB_1_ "Modding 101" Guide

{{ Last edited on: July 21, 2021 }}

{{ All hyperlinks are broken. Repairs must be made manually. }}


“Give a player a mod, and they play for a day;
Teach a player HOW TO mod, and they play for a lifetime”. . . . . .

Throughout the GSB_1_ sub-forums there are many, many posts containing details about how to begin modding this game’s files. I thought it would be a good idea to create a collection for all the the curious new modders who wish to create playable content for the community to enjoy alongside GSB_1_'s official content.

As a “meta-guide full of smaller guides,” it also serves as a vast library holding the combined wisdom that resulted from the persistence, detective work, trial-and-error testing, and individual initiative of nearly too many GSB_1_ forum members to count.

This guide is dedicated to all those who constructively contributed to it.

I invite anyone out there to post their own guide (or a link to a guide!) on how to mod GSB_1_.

1 Like

[size=115]Making your own hulls for GSB:[/size]
This thread gives you an idea on how to get a ship into the game

[size=115]Editing the text file for your new ship:[/size]

[size=115]When your ship explodes:[/size]
SirJamon has written an excellent explosion guide - it also highlights traps for modders.
The original post can be found here - viewtopic.php?f=23&t=5067&view=unread#p32997

Here is a summary:

[explosions]       //Here we determine the ship explosion sequence shown
**BUG ALERT!!! If there isn't any explosion the ship is never destroyed, then the battle never ends**
- Always, when ends the sequence of ship destruction, there's a shockwave from the center of the ship & some smoke
- Explosions sizes are relative to the ship size
- Each explosion generates 1 escape pod (except for fighters and STARTBREAKUP)

The line format looks like this
0 = t,x,y,EXP_?????

- 0 = index number (0,1,2,etc . . )
- x = Part of the coordinated to locate where the explosion occurs (0 - 256)
- y = Other part of the coordinate to locate where the explosion occurs  (0 - 256)
- t = Timer (Determines in ms how much time will last after the ship destruction for this effect to happen
- EXP_?????-> Explosion effect when ship is destroyed [i]**????? is replaced by the following names for different desired effects:[/i]
     - STARTBREAKUP (This determines when the ship will break and change its img to the hulk img. x,y are useless here so they can be 0,0) **ALERT!!! THIS EFFECT MUSTN'T BE THE LAST OF THE EXPLOSION CHAIN (Indestructible bug)**
     - FRIGATE (Medium explosion)
     - ANGLED_DEBRIS (Large debris blast)
     - DESTRUCTION_PLACED (A few debris)
     - FRIGATEBREAKUP (Medium expanded explosion)
     - CRUISERDEBRIS (Some debris)
     - FRIGATEDEBRIS (Small debris)
     - PLUMES (Fragments large explosion)
     - BLASTGLARE (White blast)
     - BLASTGLARESMALL (Small white blast)

[size=115]Creating Damage Textures on Hulls:[/size]
Cliffski has posted a really rough guide for anyone wanting a similar ‘look’ to the current damage textures on their ships
How The Damage Textures Were Done

Other Damage guides
Damage overlays of Awesomeness
Damage Underlays and Tutorial, Image Heavy

[size=115]Fighter Sprites:[/size]
These ships are put together a little differently then the other two types of ships. I have highlighted the differences below.

In the configuration file there are two main differences when turing your sprite into a playable ship:
Damage & Hulk.

Looking at the Federation Falcon you have the following lines
classname = fighter
name = Federation Falcon Fighter
guiname = Federation Falcon Fighter Hull
sprite = Federation Falcon Fighter.dds
damagetexture = Federation Falcon Fighter_damaged.dds
hulktexture = federation_hulks.dds
hulkUVstart = 0
hulkUVend = 3
width = 11
height = 11
powerproduced = 3
cost = 44
racename = federation

::Modders’ Note::
To avoid a ship that looks like it is being affected by gravity (stretched), keep the width and height the same.

You will notice that the damagetexture file has an _damaged at the end of it like frigates and cruiser. However when we navigate to where the hull file is kept you will only see these two files:
(found in\Gratuitous Space Battles\data\bitmaps\ships\federation\Federation Falcon Fighter)
Federation Falcon Fighter.dds
Federation Falcon Fighter_sprite.dds

The _sprite.dds file provides the damaged look for the ship. It is a combination of the Hull sprite and the Damage sprite placed side by side in the same image.

NOTE: It is important to have the name of the Hull file and the _sprite file the same. So when your endering the line damage texture copy/paste your file name in and replace _sprite with _damaged and you can avoid that annoying “white square” error.

::Modders’ Note::
Now, when you combine your Hull and Damage file to create the _sprite file, keep the damage file with the others. It will prove useful when you use the Hull Editor to place the damage on the ship. (You can do the same for hulks but you then have to rename the hulk texture to your fighter hulk map)

With Cruisers and Frigates, you have a unique hulk file thich the game will generate leaving various peices of the wreckage to twist and turn independantly. With fighters the hulk is one complete image however you can have multiple hulk images to be randomly choosen by the game. The random selection of fighter hulks is controled with the following code:

hulktexture = federation_hulks.dds <-Which file has the hulks
hulkUVstart = 0 <-Where the hulks start
hulkUVend = 3 <-Where the hulks end

This tells the game that when the fighter goes kaboom, choose a image between the start and end numbers and display that image as the chared remains on screen. (In this case when they die the game will randomly select from the locations 0,1,2 or 3 in the federation_hulks.dds file)

So you desire, you can have several hulk images for a single fighter if you desire. AFAIK - this image is static, there is no way to make it twist and turn like frigates and cruisers.) If you want (and you have the time) each fighter have its own fighter hulk maps so you can have multiple ways (max of 16) for each fighter to meet its demise.

So lets have a look at the federation_hulks.dds:
(found in\Gratuitous Space Battles\data\bitmaps\ships\federation)

We can see the hulks are arranged in a 4x4 grid (yes the last row is blank)

So if we number them it would go like this

0 1 2 3
4 5 6 7
8 9 . .
. . . .

Disclaimer - as far as i am aware the game will split the hulk file into a 4x4 grid (total of 16)- so if you have 5 fighters and want to have 4 hulks for each, (total of 20 hulks) you will need to make a second hulk file.

::Modders’ Note::
The naming of sprites, textures and hulks is CASE SENSITIVE. Be careful when entering them into the config file. One way to avoid errors is to use “copy” and “paste”.

1 Like

[size=115]Scenario Editing Tips:[/size]

[size=115]Modifying the Shaders for a Scenario:[/size]

[size=115]How to make a campaign map for use within Galactic Conquest:[/size]
Props to ekalin for posting this comprehensive guide.

Hi, here is everything I know. I will use “…/gratuitous space battles/” to denote the root folder where the game is located on your machine.

In order to build your own campaign map the very least you will need to do is define a campaign map configuration file in “…/gratuitous space battles/campaign/maps/”, and planet configuration files (one for each planet you want on your map) anywhere in “…/gratuitous space battles/”.

[size=170]Campaign Map Configuration[/size]

Your map’s configuration file should be a .txt file in “…gratuitous space battles/campaign/maps/”. It should contain two sections: config and encounters. I’ll try and describe every field you must define each section.


Homeworld: This is the encounter ID of the planet that will serve as the homeworld (the starting planet for the player)
MapSizeX: This defines the width of your map.
MapSizeY: This defines the height of your map. You do not need to be afraid about exceeding a player’s resolution. If the map is large then GSB will let you scroll the map.

Name: This is the internal name for your campaign map, it should be unique.
GUIName: This is the name of your campaign map as shown to the user.
MapTexture: This is a file in “…/gratuitous space battles/campaign/data/bitmaps/ui/”. It is the background for your campaign map. It will be stretched/shrunk according to the player’s resolution. There is no need to match the dimensions of the MapTexture to your MapSizeX/MapSizeY values.


This is a list of file paths for your planet configuration files. Say you only had three planets in your map, then your encounters list would look something like this:

0 = campaign/data/path/to/planets/planet1.txt 1 = campaign/data/path/to/planets/planet2.txt 2 = campaign/data/path/to/planets/planet3.txt
Planet configuration files should exist anywhere in “…/gratuitous space battles/” (including its subdirectories).

[size=170]Planet Configuration[/size]
There are five sections possible: config, terrain, variables, facilities, and hopcounts.


MapPosition.X: A number between 0 and 1 inclusive. Determines the position of your planet along the x-axis.
MapPosition.Y: A number between 0 and 1 inclusive. Determines the position of your planet along the y-axis.

The top left corner of your map is the origin and will always have the coordinates 0,0. The higher the Y coordinate, the lower the planet will appear on the map. The higher the X coordinate, the farther right the planet will appear. Examples: 1,1 is the bottom right corner of map; 0.5, 0.5 is the exact center of map.

EncounterID: This is a number that will be used to identify this planet internally. It should be unique.
wormholes: A list of encounter IDs (separated by commas) of planets you can travel to
backdrop: This is the backdrop that is shown during a battle at the planet, the file must be in “…gratuitous space battles/campaign/data/bitmaps/backdrops/”

icon: This is the graphic used to display the planet on the map. It must be a file in “…gratuitous space battles/campaign/data/bitmaps/planets/”

name: Internal name. Probably should be unique, but I don’t know for sure.
guiname: This is the name displayed to the user. It can be different then the name field.

starfield = I think this is the flag to toggle background stars when in battle. 0 turns the starfield off, 1 turns it on.
mapiconsize = This is the size of this planet’s icon on the map. The larger the number, the bigger the planet on the map.
enemyfleetcost = The higher the number, the larger an enemy fleet can be when attacking this planet (perhaps others can shed light on this)

shader = This is optional. You can add a shader to give your planet a different look. The file must exist somewhere in “…/gratuitous space battles/campaign/”. The default shaders are all in “…/gratuitous space battles/campaign/data/shaders/”.


You need to define one cryptic little line under this section. Here is an example of what it could look like:

0 = 654,367,1.0,spindle_planet1.dds,0,0,0,1.0,1.0,662,662,0,1

Start the field with a ‘0 =’ and give 13 parameters separated by commas. All I know for sure is:

  • the first two parameters are the X,Y location of the planet image in pixels
  • the 4th parameter is the planet image to display in the background during battle. Typically this should be the same as what you set as ‘icon’ in [config]
  • the 10th and 11th are the width and height of the planet image respectively

The rest of the parameters appear to be always the same values in every planet’s configuration. Perhaps someone could add to this?


This section is optional. It is used to define planetary anomalies. Here are some examples you can use:


‘Multiplier’ variables above have an extra parameter after them. This is a number between 0 and 1 inclusive.


This section is also optional. It is a list of all facilities on your planet. If I wanted to add a small factory and academy to my planet I would add this under

0 = smallfactory
1 = smallacademy

Here is a list of the IDs of all (default) facilities for your convenience:

largeacademy largefactory mediumfactory repairyard shipyarda shipyardb shipyardc smallacademy smallfactory
And yes, it is possible to add custom facilities.


Used to defines the distances between planets. A typical list may look like this:

0 = 96,8 1 = 95,7 2 = 94,6
The number before the ‘=’ character is for ordering the list (start at 0 and increment by 1 as you add more hopcount entries). The first number after ‘=’ is the encounter ID of a planet. The second number after ‘=’ is the number of warps or hops it would take to get from this planet to the planet with the same encounter ID you. So this:

0 = 96,8

would mean that it would take 8 hops to get to the planet with encounter id 96 from here. I remember reading somewhere that hopcounts are used in calculating the spread of “fear” between planets.


If anyone sees any errors above or if there is anything confusing let me know.

For large maps, editing these configuration files is tedious (and painful). In order to create Atellian Expanse, I had to create my own campaign map editor to remove most of the difficulty. I have not made this editor public yet (it’s not done), though if you are still interested in building maps I am willing to send you the current version for you to use. You would also be helping me out in testing it before I release it to the community.

1 Like

A quick breakdown of the file “race.txt” -
very useful to know if your creating your own race.

In this case i will use my Uni-T mod race as an example :slight_smile:

name = “unit” <- Unique name of the race. This name will be used by the code to link other modules and hulls
guiname = “Uni-T” <- this is the name that the player will see in the game
logo = “unit.jpg” <- What picture will be displayed when the player looks at your race in the selection screen
debrisstartuv = 0 <- as your ship is shot, it will shead parts. This is the start of the range
debrisenduv = 31 <- this is the end of the range for debris graphics id
escapepodid = 1 <- when you ship is destroyed, use this escape pod graphic id (0-3)
shield = “Corrupt_shield.dds” <- if you have shields, use this graphics file to show them
description = "“Uni-T is a collective, …” <- a description of the race you have created
repairbotid = 3 <- When little bots are repairing your ship, use this graphic id (0-3)
contrailid = 3 <- as your fighters zoom around the screen, they leave coloured trails, use this graphic id (0-3)
music = unit_battle.ogg <- when your fighting against this race, play this music
shieldcollapseuv = 3 <- as your shields collape, use this graphic id (0-3)
defaultnames = warships <- when your placing ships on the deploy screen, refer to this file to retireve a name
guiid = 10 <- The order in which your race will appear in the race selection menu
lockable = 1 <- is this race locked (0 = no / 1 = yes)
unlockcost = 1500 <- if locked, how much honor to unlock it
unlock_texture = “Dominator Core.dds” <- in fleet HQ, display this image to represent the race

[turrets] - this area is dedicated to the turret mapping. it is covered in another tutorial further down
turret_auto_v1 = unit_turret_auto_v1.dds,turrets_unit.dds,0

turret_ecm_v1 = unit_turret_las_v5.dds,turrets_unit.dds,16

[victory_messages] - if you win with this race, display one of these messages.
0 = “This sector has been cleansed of garbage, continue the sweep”
1 = “No garbage detected, sector clear”
2 = “We are Uni-T, refuse is futile”

[defeat_messages] - if you lose with this race, display one of these messages.
1 = “We are Uni-T but you are defective, report to recycling”
2 = “The directive was clear, dispose of the garbage, is your programming defective ?”
3 = “You have failed, you will be cleansed!”

[crew] - in the comms chatter box, use this names.
0 = “Drone-OMGWTF”
1 = “Drone-001010”

Ship Modules:
Here is a quick A-Z of the variables you will find in the module files:
(and what I think they mean - if i have made a mistake, let me know so i can fix it)

armour_penetration - The amount of armor that the weapon can penetrate (if armor of target is higher, the weapon is not effective)
beam_duration - How long the beam is drawn on the screen (in milli seconds - ie 1000 = 1 second)
beam_texture - the dds file used to draw the beam between the target and the turret
beam_width - how wide the beam is
beampower - the size of the capacitor for the tractor beam
beamweight - the amount of weight applied by the tractor beam
blasttexture - the dds file used to draw the turret muzzle flare
category - what group the module will appear in (Weapons,Defense,Engines,Other)
classname - which type of module you are using and there are many:
- SIM_ArmourModule
- SIM_BeamWeaponModule
- SIM_BulletWeaponModule
- SIM_CamoflageShieldModule
- SIM_CarrierModule
- SIM_ECMBeamModule
- SIM_ECMShieldModule
- SIM_ECMShockModule
- SIM_EngineModule
- SIM_KineticWeapon
- SIM_LightningGunModule
- SIM_LimpetLauncher
- SIM_MissileModule
- SIM_PDScannerModule
- SIM_PlasmaLauncherModule
- SIM_PointDefenseModule
- SIM_PowerModule
- SIM_RepairModule
- SIM_ShieldModule
- SIM_SmartBombModule
- SIM_TargetBoosterModule
- SIM_TargetPainterModule
- SIM_TractorModule
cloak_consumptionrate - How quickly the cloak drains the power
cloak_rechargerate - how quickly the cloak regains power
color - Only used in SIM_BulletWeaponModule and can only have a value of 0 to 8
convergence - Used for when you want your beams to join forces (only works on turrets with multi hard points)
cost - how much money you need to have that weapon on the ship
crew_required - Number of crew needed to operate the module.
damage - How much hurt the module does when it penetrates the shield / armour
damage_duration - used for radiation weapons, how long the target is effected by radiation
description - Used in the ship build screen, its is used to tell the player what the module is and what it does.
drift_decelleration - How quickly a limpet slows down
ecm_strength - How strong the ecm is for beams/missiles - how much the module can withstand for ECM shields.
end_launch_speed - How fast the limpet travels
fire_interval - how often the module fires (in milli seconds - ie 1000 = 1 second)
firedelay - how long it takes for the beams to join and reach its target.
flareuvid - chooses the colour of the glowy blob over the missile value between 0 - 3
flaresize' (default 16) - the size of flare drawn on the missile
fuel - how long the missile / plasma will go for.
grain - the dds file that provides a overlay pattern for the beam
guiname - used in the ship build screen, its the name of the module
has_decoys - does the missile break into 4 separate missiles
has_flare - does the missile have a glowy blow drawn over it
has_grain - Does the beam have a pattern drawn over it
has_splines - does the missile travel along a spline path with a smoke trail
height - used to change how tall the bullet is
hitpoints - how much damage the module can take before destruction
icon - for weapons its "turret" for everything else its the dds file that has a picture of the module. Unless you have a specific icon for your weapon that you want to use :)
launch_duration - How long it takes for the limpet to slow down after launch
limpet_weight - how much weight the limpet adds to the target once attached
limpetsize - how big the limpet is drawn ingame
lockable - can this module be used right away or do you have to earn it
max_cloak_power - maximum power capacity of the cloak
max_range - maximum range that the module is effective
max_seek_speed - the top speed of the limpet when chasing a target
maxdamageabsorbable - how much damage the armour can take
maxrepairsupplies - how much damage the module can repair
min_range - the minimum range that the module is effective
missilelength - how long the missile is
missilewidth - how wide the missile is
name - the Unique name of the module, used by the code, not seen by the player.
num_submunitions' (max 6) - The number of warheads that missile will break into at decoy release range
optimum_range - the range when the module inflicts the most damage
payload - When your bullet hits the target, what type of damage can it do (at the moment its only RADIATION)
peace_interval - the minimum time for the module not to be under attack to activate.
powerconsumed - how much power the module needs to operate
powerproduced - how much power the module produces
powerrecharge - how quickly the tractor beam capacitor recharges
powerusage - how much power the tractor beam uses from the capacitor per cycle
radiation_damage - the initail amount of damage done by radiation
radiation_decay - how quickly the radiation damage falls off
range - how far the tractor beam can reach
recharge_rate - how quickly the shields can recharge after being damaged
repair_rate - how quickly the module can repair damage per second
repair_type - used if you want a repair module to focus on one aspect (at the moment its only armor)
resistance - how much the shield can reflect or the level of shield penetration required to cause damage
restricted - is this module only for one race
salvo_interval - length of time between volleys
salvo_size - how may shots in a volley
sb_trigger_percentage - the chance that the smart bomb will detonate the missile
scanner_accuracy - how well a module can determine the difference between a decoy and the warhead
seek_acceleration - how fast the limpet accelerates towards a target
seek_range - how far the limpet will look for a target
shield_penetration - The level of shield that the weapon can penetrate (if shield resistance of target is higher, the weapon is not effective)
shieldpoints - the amount of hitpoint the shield has
shock_duration - how long the ECM is in effect on the target ship (in milliseconds 1000 = 1 second)
size - what class of ship is the module fore (Fighter, frigate or cruiser)
slot_type - What type of module is it Standard or Turret
sound - what ogg sound file to play make when it fires.
soundvolume - controls the volume of the sound file
speed  - how fast the projectile moves
spritesize - how big to draw the sprite used for plasma weapons
stack_effectiveness - When you have more than one of the module, the performance will change by x%
start_launch_speed  - how fast the limpet is when launched
style - used in the PlasmaLauncherModule, you can switch between the 2 types FRAGMENTED & STANDARD
submunitionslive - used to make the decoys do damage
targetboost - how much faster to other modules track a target
texture - the dds file used to span between the turret and target
thrust - the amount of force generated by the module to move the ship
total_damage - the total amount of damage done by the radiation
tracking_speed - the turning spead of the module, the faster the module turns the better chance of hitting fast targets
trail_fade_time - time it takes for the missile trail to fade
turn speed - how quickly the missile / limpet can turn.
turret_sprite - a refence used by turret mapping which is found in the race file.  Determins the icon and sprite used in the game
turretsize - size of the turret in the game.
uisortpos - User Interface Sort Position.  Where about on the module list does it appear
unlockcost - how much honour do you need to unlock this module
warhead -  determines what type of damage the missile does (ECMSHOCK, RADIATION, DUMMY, EXPLOSION)
weight - how heavy is the module
width - how wide is the bullet / projectile
capacitorsize - Maximum amount of shield energy the unit can hold
ssb_beamrate - The quantity of shield energy beamed over to the target per pulse
mincaptodischarge - if the shield energy is below this number then it will not fire.
ssb_rechargerate = How much shield energy the unit creates per second
pulseduration = the amount of time between pulses of transfering shield energy.

A quick guide on how a beam effect graphics file works

  1. The blast effect is placed at the start of the turret
  2. The main beam effect is stretched from the turret to the target
  3. The grain section is repeatedly placed along the effects (without stretching) back to back

Creating your own Turrets:
Quick guide on what is required to get your own custom turrets into the game

Instructions to make your modded weapons compatible with the battle stats screen
Locking down a new turret without causing a conflict in Fleet HQ:
In all module files you have the following line:
Icon = <>

This line is used to display an icon in areas like your weapon selection window in your ship building screen and for fleet HQ when you are choosing which module to unlock next.

Modules such as engines, shields etc look something like this: icon = turbocharged_engine_mkIV.dds
while turrets have look something like this: icon = turret

When the game finds icon = turret, the program heads down a few lines to turret_sprite to find the name of this particular turret - for example:
turret_sprite = “mega_tach_v1”

Then it heads over to (in this case) unity.txt and to obtain the dds filename from the turret mapping section. In this example:
mega_tach_v1 = turret_mega_tach_v0.dds,turrets_unit_mega.dds,5
Therefore the game will display turret_mega_tach_v0.dds in the weapon display menu

So far so good.
However if your modded turret is locked which is controlled through lockable = 1 the program will use federation.txt to display in in Fleet HQ. In this example there is no “mega_tach_v1” in federation.txt so the game will crash.

To fix this you either

  • add in the new turret mapping to federation.txt
  • follow the following steps: (I will be using my Unity Mod as an example)

Step 1:
Copy the file turret_mega_tach_v0.dds
from \unit\data\bitmaps\turrets\Unit
to \unit\data\bitmaps\modules\

Step 2:
Rename the file in the modules directory to mega_tachyon_turret.dds

Step 3:
Open the Mega Tachyon ini module and change the line
icon = turret
icon = mega_tachyon_turret.dds

the following steps are for locking your module in Fleet HQ
lockable = 0
lockable = 1

unlockcost = 0
unlockcost = 5000

Run the game.
Now the Mega Tachyon Cannon will be locked without the need to modify the federation.txt. The only drawback to this method is that the more you lock down, the larger your mod becomes since you have to copy the file into 2 locations. Its a small increase in size, but becomes noticable if you unlock 100 turrets.

Please note that you do not have to use the turret sprite as your icon image, you may choose a different icon, say an image of the laser firing from a certian small moon sized battle station . .

If you still have questions or problems, feel free to PM me :slight_smile:

ECM Payload
classname = “SIM_ECMBeamModule”

ecmpayload = "RETURNTOSENDER"

What it does:
By adding this new ECM payload into your missile scrambler code it will scramble the missiles guidance system so badly that the missile will try and hit the ship that fired it.

Hints and tips.
while a missiles that has been affected by the RETURNTOSENDER can not be turned around again. It still can be shot down by.

  • Guidance Scrambler
  • Anti Missile Point Defence.

Plasma Burst.
classname = “SIM_PlasmaLauncherModule”

maxsimultaneous = 4

What it does:
This new addition enables your plasma weapons to have up to a maximum of 4 flaming plasma spheres of death flying across the screen at any one time.

Hints and tips.
Remember to lower your fire_interval to get that Plasma Burst Goodness.

Custom Bullets.
classname = “SIM_BulletWeaponModule”

New Code

bullet_texture = "moddedbullets.dds"

What it does:
The Community have been bugging Cliff for a long time about this. With the bullet texture override, you can change that bullet into ANYTHING you want.

unlockcost = 12000
lockable = 1
armour_penetration = 60
blasttexture = “turret_cannon_blueII.dds”
category = “WEAPONS”
classname = “SIM_BulletWeaponModule”
bullet_texture = “bullets_II.dds” [i]<- it will look for the file here: <>\data\bitmaps\fx[/i]
color = 4
cost = 1280
crew_required = 28

::More Examples of what you can do::

Hints and tips.
After you have added in bullet_texture, remember to change
height =
width =
to help get the image the way you want it.

Another point to remember:
the larger the image of the custom bullet, the more you will slow down GSB!!!
(especially if you have an extremely short refire rate for the weapon)
Be a friendly modder, and do not go insane with this modding feature.

AoE / Area of Effect damage (also known as Flak).
classname = “SIM_BulletWeaponModule”

payload = FLAK
aoe_radius = 50
aoe_scalar = 0.5

What it does:
This section of code will create damage over an area at the intended target when the bullet either:

  • Hits the target
  • Misses the target and Expires.

Payload = FLAK - This activates the Area of Effect mechanic for the bullet. Please note that Tracking of the weapon is no longer a determining factor on what the turret can and cant hit. Once your using FLAK as a payload, the bullet will always damage the target and any surrounding ships (friend or foe)

aoe_radius = number - This determines the radius of the area of effect. Anything within this distance of the epicentre will receive damage if their shields / armour are not strong enough.

aoe_scalar = number - This determines the percentage of the damage any ship will receive that is caught in the area of effect and did not have strong enough shields / armor to protect it. For example
aoe_scalar = 0.5 - any ships in AoE will receive half of the weapons damage
aoe_scalar = 1.0 - any ships in AoE will receive the full weapons damage
aoe_scalar = 2.0 - any ships in AoE will receive twice the weapons damage

Hints and tips.

  • If you are using the AoE payload for a modded weapon, it is a very good idea that you are fully aware of how it works.
  • Ignorant use, or deliberate abuse, of AoE will both seriously hurt GSB’s balance and quality of gameplay!!!
  • There is a discussion on this new feature you can read here.

1 Like

He, he. It’s about time someone collected all the data that is scattered around the forum :smiley:

I was the one who wrote that info :slight_smile:


Cliff posted information about scenarios here (if you look the posts below the first one, there’s also information about hulls and deployments)


BTW, I made some time ago (for me) a visual guide for coding explosions, it’s just some pics to help me remind each one of them.
Attached down here :slight_smile:
GMM Explosions.zip (181 KB)

Ow, i was looking for this info time ago, specially the variable section xD. THX very much!!!.

Looking to the explosions section, i was wondering if the game will “allow” bigger ships modifying those explosion parameters ¿is that even possible?.

Thanks! I’ve been wanting something like this.

Can we get a sticky on this thread, Cliff?

Hmm, wats the difference between style = standard / fragmented in the plasma module??? i noticed if i change it to fragmented, the game picks another portion of the texture, wats the purpose??

The purpose is just that . . if you look at the dds file you will see the two sprites.
Style = standard / fragmented is just tells the game which sprite to use.

Another example is for bullets. Where the “color = 0” changes the bullet.
If you look at bullets.dds you will see 10 different images of bullets
by changing the color you can select the one you want.

The thing is using the fragmented style the plasma doesnt seem like a plasma torpedo anymore xD, and it looks really awful. So thats my point. Usually, the parameters that only changes from a texture to another are kinda xxxx = 1. But a parameter “style” should be more useful. I dont think anyone uses the fragmented mode…well, if u make bubble mod… lol.

I use the fragment mode for plasma . . but yes it would be nice to change style to refer a .dds file instead

Okay if someone can please literally take a screen shot every step and highlight the areas needed to implement your own turrets i for the life of me cant get it to work game keep crashing with a turret mapping error, i mad a .dds for the turrent i wanted (nothing crazy), i then made a turret_crusader.dds file and placed said turret in the top left and then made this line in the crusaders text file.

turret_auto_v1 = crusader_v1.dds,turrets_crusader.dds,0

I even deleted every other turret line in the text file (was just basic federation turrets nothing special)

I am at a loss i was hoping to implement a crusader missel/beam laser, nothing to special just slightly more powerful (not a lot really) and slightly more expensive/more crew needed.

I just can not figure out why it crashing on me.


p.s i have the turret_crusader.dds out side of the crusader folder, and the .dds for the turret it self inside the crusader folder is this is issue?

Here is what my turret_crusader.dds looks like

Should I resize the turret image within the .dds? is that whats causing the issue?

I assumed you tried to follow this:

From the guide
“. .It is worth to note that the turret mapping is for both your new custom weapons and the weapons avaliable to all races.”

So in your crusader.txt file you will need to have the standard turret mappings (ie copy from the federation file) plus your own.

Yes i made a text file that points to the original .dds first then to the turret_crusader.dds next and use 0 as it was the first one inside only problem is it for some reason can not find the mapping? When i made the turret_crusader.dds file i did not resize the turret i noticed the turrets inside the other files were smaller so is this an issue?


Ah, its not your new turrets, that are causing problems, its the fact that you have removed the standard turret mapping:

Quick Summary - you have your three files:

  • <>\data\bitmaps\turrets\turrets_crusader.dds ← this holds all your new in game images, the file is broken down into an 8 x 8 grid.
  • <>\data\bitmaps\turrets\crusader\crusader_v1.dds <-this file holds a single image. It is used in the ship building screens
  • <>\data\races\crusader.txt ← this is your turret mapping. It tells the game what the file names are and where they are located on the grid

Then your crusader.txt code should at least look like this:

turret_auto_v1 = crusader_v1.dds,turrets_crusader.dds,0
turret_auto_v2 = fed_turret_auto_v2.dds,turrets_federation.dds,1
turret_auto_v3 = fed_turret_auto_v3.dds,turrets_federation.dds,2
turret_auto_v4 = fed_turret_auto_v4.dds,turrets_federation.dds,3
turret_auto_v5 = fed_turret_auto_v5.dds,turrets_federation.dds,4
turret_auto_v6 = fed_turret_auto_v6.dds,turrets_federation.dds,5
turret_bull_v1 = fed_turret_bull_v1.dds,turrets_federation.dds,6
turret_bull_v2 = fed_turret_bull_v2.dds,turrets_federation.dds,7
turret_bull_v3 = fed_turret_bull_v3.dds,turrets_federation.dds,8
turret_bull_v4 = fed_turret_bull_v4.dds,turrets_federation.dds,9
turret_las_v1 = fed_turret_las_v1.dds,turrets_federation.dds,10
turret_las_v2 = fed_turret_las_v2.dds,turrets_federation.dds,11
turret_las_v3 = fed_turret_las_v3.dds,turrets_federation.dds,12
turret_las_v4 = fed_turret_las_v4.dds,turrets_federation.dds,13
turret_las_v5 = fed_turret_las_v5.dds,turrets_federation.dds,14
turret_miss_v1 = fed_turret_miss_v1.dds,turrets_federation.dds,15
turret_miss_v2 = fed_turret_miss_v2.dds,turrets_federation.dds,16
turret_miss_v3 = fed_turret_miss_v3.dds,turrets_federation.dds,17
turret_miss_v4 = fed_turret_miss_v4.dds,turrets_federation.dds,18
turret_miss_v5 = fed_turret_miss_v5.dds,turrets_federation.dds,19
turret_pd_v1 = federation_turret_pd_v1.dds,turrets_federation.dds,22
turret_pd_v2 = federation_turret_pd_v2.dds,turrets_federation.dds,23
tractor_turret_v1 = tractor_turret_v1.dds,turrets_federation.dds,27
tractor_turret_v2 = tractor_turret_v2.dds,turrets_federation.dds,29
turret_plasma_v1 = plasma_turret_v1.dds,turrets_federation.dds,24
turret_plasma_v2 = plasma_turret_v2.dds,turrets_federation.dds,25
turret_plasma_v3 = plasma_turret_v3.dds,turrets_federation.dds,26
turret_plasma_v4 = plasma_turret_v3.dds,turrets_federation.dds,26
turret_ecm_v1 = fed_turret_ecm_v1.dds,turrets_federation.dds,31

You need to keep those other lines in - this tells the game how your crusader race displays the standard turrets :slight_smile:
Hope this helps with the turret mapping problem.

If the game displays the turret incorrectly ingame, then yes, your right, resize the image.

I don’t know what the issue is it loaded the game up fine then i realized (i had previously deleted everything) i forgot to remake the modules text file in the modules folder, so i remake it and i get the mapping issue again =/

I will just put it on hold for now as i have more work to do on hull bonuses and module layout:

I also have an issue with my fighters if i class them fighters they appear as white dots and lag like crazy, yet if i class them as frigs they spawn just fine? Of course thats no good as with frig weapons and fighter speed…yeah op’d XD

so i appreciate the help i will just completely redo it later on after i have a basic build down.


That also happened to me while trying to get corvettes as fighters >.<
The reason is that fighters go slightly differently from normal hulls (frigates and cruisers).

To fix it you need:

Something like this at the start of the hull file

[config] classname = fighter name = Federation Mole Corvette guiname = Federation Mole Corvette Hull sprite = Federation Mole Corvette.dds damagetexture = Federation Mole Corvette_damaged.dds hulktexture = experimental_hulks.dds hulkUVstart = 0 hulkUVend = 2 width = 50 height = 50 powerproduced = 6 cost = 50 racename = federation
Then add a sprite called Ship name_sprite.dds (Ship name is the name of your hull) inside the folder where you have the other sprites of that ship. That sprite must be similar to this one:

And if you want your fighters to leave hulks you need yo know how this three lines work

hulktexture = experimental_hulks.dds Sprite where are your fighter hulks hulkUVstart = 0 First hulk from the series of hulks in the sprite picked for this fighter hulkUVend = 2 Last hulk from the series of hulks in the sprite picked for this fighter
To see an example of hulktexture look for federation_hulks.dds in gsb/data/bitmaps/ships/federation

[size=150]If you use any DLC (official “add-on” downloaded content) in your mods, then please say so in the first post of your mod’s forum thread!!![/size]

I am very tired and frustrated of trying out mods and I MUST remove or add renamed sound files to new folders to make them work. I have tried two separate mods recently and both of those player mods did not have the warning saying what is needed to play them.

I do have the knowledge to edit them to work without the DLC files, its just a pain in the butt to have to rework them after finding out I have to edit the files to play the player’s mod. Thank you for not doing that to other players in the future.

im starting to mod weapons and modules, and i have a question, how i can change the std bullet sprites for new custom sprites? NOT beams. Laser bullets.

im not shure, but i dont think that you can make new bullets. just modify the ones that already exist…