ΔV: Wiki - Recent changes [en]

Mod List

Hev — Sat, 19 Sep 2026 19:01:03 GMT

Updated obsolescence for old Discord RPC and added HevLib's sub-modules

@@ Line 212: / Line 212: @@
 A download can be found from it's Github releases page [https://github.com/rwqfsfasxc100/Hevs-More-Minerals/releases/latest here].
 === [https://github.com/1-WT-1/ToggleDrone ToggleDrone] ===
@@ Line 270: / Line 261: @@
 A download can be found from it's Github releases page [https://github.com/1-WT-1/DVHudHueMod/releases/latest here].
 == DLC ==
@@ Line 490: / Line 491: @@
 Download can be found on the Github [https://github.com/JCalebBR/Realistic-Minerals/releases/latest here], however requires MoreMinerals which can be found from the ZKY collection above, or a direct link [https://github.com/ZakrinYoran/ZKYs-of-Saturn/tree/main/MoreMinerals here]

Troubleshooting

Hev — Fri, 18 Sep 2026 15:15:00 GMT

Added note on driver-side FPS limiters

← Older revision		Revision as of 15:15, 18 September 2026
Line 13:		Line 13:

	* Please make sure your system meets the minimum hardware requirements for the game.		* Please make sure your system meets the minimum hardware requirements for the game.
			* Driver-side FPS limiters (V-Sync, FPS limit, etc.) should be disabled in favour of using the game's built-in equivalents. The command injection that these do to the game's draw call stream has been known to crash OpenGL.
	* If using AMD Ryzen hardware, make sure that your system runs in the Ryzen-dedicated power plan. [https://asapguide.com/ryzen-balanced/ See this guide].		* If using AMD Ryzen hardware, make sure that your system runs in the Ryzen-dedicated power plan. [https://asapguide.com/ryzen-balanced/ See this guide].
	* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.		* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.

Modding:Writing Your Own Mod

Hev — Thu, 17 Sep 2026 17:57:57 GMT

@@ Line 44: / Line 44: @@
 * Launch the Delta-V Project, and let Godot import all of the files.
-The initial import process will take a couple of minutes at worst if everything is followed. In the case where it takes a significant amount of time, you may have used a newer version of GDRE. If it appears to freeze, don't worry, it is still processing, and can be used regardless. After the first import, future loading times usually will be significantly better, although it is always better to use GDRE 0.5.3 to ensure quick loading times.
+It is highly recommend to develop mods with the help of the Godot Editor, a guide to [[Modding:Using the Godot Editor|which can be found here]].
-It may also be worth taking a look at the guide for modding with the Godot Editor, [[Modding:Using the Godot Editor|which can be found here]].
+= GDScript =
 = Mod Structure =
@@ Line 400: / Line 409: @@
 <code>manifest_version</code> The manifest formatting version. If not provided, a version number of <code>1</code> is assumed.

Modding

Hev — Sat, 05 Sep 2026 04:34:41 GMT

← Older revision		Revision as of 04:34, 5 September 2026
(One intermediate revision by the same user not shown)
Line 4:		Line 4:
	* [[Mod List]] - A list of every known mod and tool repository for anyone looking for preexisting mods.		* [[Mod List]] - A list of every known mod and tool repository for anyone looking for preexisting mods.
	* [[Modding:Writing Your Own Mod\|Writing Your Own Mod]] - Beginning of a collection of guides that cover the basics on writing a mod.		* [[Modding:Writing Your Own Mod\|Writing Your Own Mod]] - Beginning of a collection of guides that cover the basics on writing a mod.
	* [[Using the Godot Editor]] - Guide to setting up mods to be run in the Godot Editor.		** [[Modding:Using the Godot Editor\|Using the Godot Editor]] - Guide to setting up mods to be run in the Godot Editor.
			**

Modding:Writing Your Own Mod

Hev — Sun, 30 Aug 2026 05:29:35 GMT

← Older revision		Revision as of 05:29, 30 August 2026
Line 46:		Line 46:
	The initial import process will take a couple of minutes at worst if everything is followed. In the case where it takes a significant amount of time, you may have used a newer version of GDRE. If it appears to freeze, don't worry, it is still processing, and can be used regardless. After the first import, future loading times usually will be significantly better, although it is always better to use GDRE 0.5.3 to ensure quick loading times.		The initial import process will take a couple of minutes at worst if everything is followed. In the case where it takes a significant amount of time, you may have used a newer version of GDRE. If it appears to freeze, don't worry, it is still processing, and can be used regardless. After the first import, future loading times usually will be significantly better, although it is always better to use GDRE 0.5.3 to ensure quick loading times.

	It may also be worth taking a look at the guide for modding with the Godot Editor, [[Using the Godot Editor\|which can be found here]].		It may also be worth taking a look at the guide for modding with the Godot Editor, [[Modding:Using the Godot Editor\|which can be found here]].

	= Mod Structure =		= Mod Structure =

Using the Godot Editor

Hev — Sun, 30 Aug 2026 05:29:20 GMT

Hev moved page Using the Godot Editor to Modding:Using the Godot Editor without leaving a redirect

New page

Ever since [https://github.com/GDRETools/gdsdecomp/releases/tag/v0.9.1 GDRE 0.9], it has been economical to use the Godot Editor to run the game to test mods instead of packaging them and launching the standalone game to test.

Mods can currently be run through two methods: placing a mod's zip in a mods folder next to the Godot executable, or manually patching the modloader to load mods from the filesystem. The latter is preferred, as it lets you more effectively modify code without repackaging it as a zip, as a mod loaded from Zip will always override code in the filesystem.

Enabling mods is as simple as setting the <code>areModsEnabled</code> variable to true in the <code>ModLoader.gd</code> file. This lets mods be loaded from a mods folder just fine, however loading mods directly from the editor requires additional patching.

A complete mod loader replacement can be found from a Github page here: https://github.com/rwqfsfasxc100/Delta-V-Useful-Files/blob/main/ModLoader.gd. Alternatively, you can copy-paste the following code to replace the <code>ModLoader.gd</code> file. The array <code>addedMods</code> lists all <code>res://</code> paths to mods that you want to load. Anything commented out will not be registered. The mods in the file are used purely as an example.
extends Node

var areModsEnabled = true

var addedMods = [
# "res://ModMenu/ModMain.gd",
# "res://HevLib/ModMain.gd",
# "res://No Simulation Hex/ModMain.gd",
# "res://DerelictDelights/ModMain.gd",
# "res://IndustriesOfEnceladusRevamp/ModMain.gd",
# "res://Better Recon Drones/ModMain.gd",
# "res://NTCED Parts Pack/ModMain.gd",
# "res://Remove Ring Restrictions/ModMain.gd",
]

const is_debugged = true

func _init():
for arg in OS.get_cmdline_args():
if arg == "--enable-mods":
areModsEnabled = true

if not areModsEnabled:
return

Debug.l("ModLoader: Loading mods...")
_loadMods()
Debug.l("ModLoader: Done loading mods.")

Debug.l("ModLoader: Initializing mods...")
_initMods()
Debug.l("ModLoader: Done initializing mods.")

var _modZipFiles = []

func _loadMods():
var gameInstallDirectory = OS.get_executable_path().get_base_dir()
if OS.get_name() == "OSX":
gameInstallDirectory = gameInstallDirectory.get_base_dir().get_base_dir().get_base_dir()
var modPathPrefix = gameInstallDirectory.plus_file("mods")

var dir = Directory.new()
if dir.open(modPathPrefix) != OK:
Debug.l("ModLoader: Can't open mod folder %s." % modPathPrefix)
return
if dir.list_dir_begin() != OK:
Debug.l("ModLoader: Can't read mod folder %s." % modPathPrefix)
return

while true:
var fileName = dir.get_next()
if fileName == "":
break
if dir.current_is_dir():
continue
var modFSPath = modPathPrefix.plus_file(fileName)
var modGlobalPath = ProjectSettings.globalize_path(modFSPath)
if not ProjectSettings.load_resource_pack(modGlobalPath, true):
Debug.l("ModLoader: %s failed to load." % fileName)
continue
_modZipFiles.append(modFSPath)
Debug.l("ModLoader: %s loaded." % fileName)
dir.list_dir_end()

func _initMods():
var initScripts = []
for modFSPath in _modZipFiles:
var gdunzip = load("res://vendor/gdunzip.gd").new()
gdunzip.load(modFSPath)
for modEntryPath in gdunzip.files:
var modEntryName = modEntryPath.get_file().to_lower()
if modEntryName.begins_with("modmain") and modEntryName.ends_with(".gd"):
var modGlobalPath = "res://" + modEntryPath
Debug.l("ModLoader: Loading %s" % modGlobalPath)
var packedScript = ResourceLoader.load(modGlobalPath)
initScripts.append(packedScript)

for m in addedMods:
var packedScript = ResourceLoader.load(m)
initScripts.append(packedScript)

initScripts.sort_custom(self, "_compareScriptPriority")

for packedScript in initScripts:
Debug.l("ModLoader: Running %s" % packedScript.resource_path)
var scriptInstance = packedScript.new(self)
add_child(scriptInstance)

func _compareScriptPriority(a, b):
var aPrio = a.get_script_constant_map().get("MOD_PRIORITY", 0)
var bPrio = b.get_script_constant_map().get("MOD_PRIORITY", 0)
if aPrio != bPrio:
return aPrio < bPrio

var aPath = a.resource_path
var bPath = b.resource_path
if aPath != bPath:
return aPath < bPath

return false

func installScriptExtension(childScriptPath:String):
var childScript = ResourceLoader.load(childScriptPath)

childScript.new()

var parentScript = childScript.get_base_script()
var parentScriptPath = parentScript.resource_path
Debug.l("ModLoader: Installing script extension: %s <- %s" % [parentScriptPath, childScriptPath])
childScript.take_over_path(parentScriptPath)

func addTranslationsFromCSV(csvPath:String):
var translationCsv = File.new()
translationCsv.open(csvPath, File.READ)
var TranslationParsedCsv = {}

var translations = []

var csvLine = translationCsv.get_csv_line()
for i in range(1, csvLine.size()):
var translationObject = Translation.new()
translationObject.locale = csvLine[i]
translations.append(translationObject)

while not translationCsv.eof_reached():
csvLine = translationCsv.get_csv_line()
if csvLine.size() == 1 and csvLine[0] == "":
break
var translationID = csvLine[0]
for i in range(1, csvLine.size()):
translations[i - 1].add_message(translationID, csvLine[i])

translationCsv.close()

for translationObject in translations:
TranslationServer.add_translation(translationObject)

func appendNodeInScene(modifiedScene, nodeName:String = "", nodeParent = null, instancePath:String = "", isVisible:bool = true):
var newNode
if instancePath != "":
newNode = load(instancePath).instance()
else :
newNode = Node.instance()
if nodeName != "":
newNode.name = nodeName
if isVisible == false:
newNode.visible = false
if nodeParent != null:
var tmpNode = modifiedScene.get_node(nodeParent)
tmpNode.add_child(newNode)
newNode.set_owner(modifiedScene)
else :
modifiedScene.add_child(newNode)
newNode.set_owner(modifiedScene)

var _savedObjects = []

func saveScene(modifiedScene, scenePath:String):
var packed_scene = PackedScene.new()
packed_scene.pack(modifiedScene)
packed_scene.take_over_path(scenePath)
_savedObjects.append(packed_scene)

Modding

Hev — Sun, 30 Aug 2026 05:28:48 GMT

← Older revision		Revision as of 05:28, 30 August 2026
Line 1:		Line 1:
	This page acts as a bridge to multiple pages related to modding ΔV:		This page acts as a bridge to multiple pages related to modding ΔV:

	* [[Introduction to Modding]] - A how-to on installing and uninstalling mods with a lot of useful information for anyone looking to mod.		* [[Modding:Introduction to Modding\|Introduction to Modding]] - A how-to on installing and uninstalling mods with a lot of useful information for anyone looking to mod.
	* [[Mod List]] - A list of every known mod and tool repository for anyone looking for preexisting mods.		* [[Mod List]] - A list of every known mod and tool repository for anyone looking for preexisting mods.
	* [[Modding:Writing Your Own Mod\|Writing Your Own Mod]] - Beginning of a collection of guides that cover the basics on writing a mod.		* [[Modding:Writing Your Own Mod\|Writing Your Own Mod]] - Beginning of a collection of guides that cover the basics on writing a mod.
	* [[Using the Godot Editor]] - Guide to setting up mods to be run in the Godot Editor.		* [[Using the Godot Editor]] - Guide to setting up mods to be run in the Godot Editor.

Guides

Hev — Sun, 30 Aug 2026 05:28:27 GMT

← Older revision		Revision as of 05:28, 30 August 2026
Line 33:		Line 33:
	== Modding ==		== Modding ==

	* [[Introduction to Modding]]		* [[Modding:Introduction to Modding\|Introduction to Modding]]
	* [[Modding:Writing Your Own Mod\|Writing Your Own Mod]]		* [[Modding:Writing Your Own Mod\|Writing Your Own Mod]]

Launch Parameters

Hev — Sun, 30 Aug 2026 05:28:14 GMT

← Older revision		Revision as of 05:28, 30 August 2026
Line 2:		Line 2:

	=== [[--enable-mods]] ===		=== [[--enable-mods]] ===
	This option enables the modloader, which allows the game to run mods whilst disabling achievements and the leaderboard while it is enabled. Check the [[Introduction to Modding\|introduction to modding page]] to read more		This option enables the modloader, which allows the game to run mods whilst disabling achievements and the leaderboard while it is enabled. Check the [[Modding:Introduction to Modding\|introduction to modding page]] to read more

	=== [[--debug-console]] ===		=== [[--debug-console]] ===

Introduction to Modding

Hev — Sun, 30 Aug 2026 05:27:58 GMT

Hev moved page Introduction to Modding to Modding:Introduction to Modding without leaving a redirect

New page

Delta-V: Rings of Saturn supports mods, and has provided modding support since mid-2021. The game's modloader, when active, loads mods as .zip files from a 'mods' folder within the game's directory.

Mods can execute unsafe or dangerous code on your computer, and may carry bugs or game-breaking issues. Mods are not guaranteed to be compatible with another mod, and it is advised to use only a small handful of mods at a time to get the best experience from them. Contact the mod author if you have problems, as Kodera Software cannot and will not help with problems caused by mods, and will flag bugs reported as "using mods".

If you want to make your own mod, check out [https://github.com/ZakrinYoran/Delta-V-Modding Za'krin's Modding Helper Guide], and the [https://discord.com/channels/426287934870781952/1252866978075512863 modding help channel] in the [https://discord.gg/dv Kodera Software Discord] where you can ask for assistance, or the (currently under construction) [[Technical Info|technical info]] page which goes into how various numbers and mechanics work and are formatted. (if the first discord link does not work, you may need to have joined the Discord server, which you can do [https://discord.gg/dv here]

If you are already familiar with how modding works and are aware of the dangers, you can find a list of every known mod and mod repository on it's [[Mod List|dedicated page]].

It is highly advised you give the ''Getting Started section'' a read, as mods can very easily cause irreparable damage to your save. '''YOU HAVE BEEN WARNED!!!'''
==Getting Started With Installing Mods==
This part of the guide will assume you're on Steam, and using Windows given it is a port of [https://steamcommunity.com/sharedfiles/filedetails/?id=3406497378 this guide], however they will work with alternatives on other Operating Systems and launchers. If you need any help, feel free to ask on the [https://discord.gg/dv ΔV Discord]

=== Part One: Installing Mods ===
Starting off with this section may seem counter-intuitive to some, however it is one of the easiest steps, and provides the setup needed for when you actually come to download mods.

==== Creating the Mods Folder ====
The first step is making a folder for the mods to go. To start off with, you either right click on the game, or click the gear icon on the game page, then go to the "Manage" tab, then "Browse local files".

[[File:Modding Guide - Browse Local Files.png]]

This will open up a file explorer (or your OSes equivalent) at the location of the game's executable and .pck files. Here, you will want to create a new folder, and name it '''mods'''.

[[File:Mod Guide - Mod Folder.png]]

From here, this is the folder where you'll be placing the .zip files of the mods you want to install.

[[File:Modding Guide - zip examples.png]]

==== Enabling Mods ====
Similar to accessing the executable's folder, you'll want to either right click or press the gear icon, and this time go to the properties section.

[[File:Modding Guide - Properties.png]]

From here, you'll want to select the launch options, and put '''--enable-mods'''. While this is in the launch options (as long as there's no typo), mods will load and you will no longer be able to earn achievements or leaderboards, however achievement progress won't be blocked internally and can be granted after disabling mods.

[[File:Modding Guide - Launch params.png]]

Once this has been enabled, mods will load. If you want to stop loading a mod, you can change the file extension to anything that isn't a '''.zip''' file, move it to a different folder, or if you want to stop loading all mods, you can remove the '''--enable-mods''' flag.

=== Part Two: Downloading Mods ===

==== Where Do I Find Mods ====
Mods will be distributed through a multitude of ways. Most have their own Github or Gitlab repository, many have threads on the ΔV Discord's workshop board, and a handful are available on the [https://www.nexusmods.com/dvringsofsaturn Nexusmods page for ΔV]. If you want an easy way to look over available mods, a list is maintained on the [[Mod List|wiki]] containing every known mod for the game, including redundant or currently broken mods.

==== Downloading Mods from Github ====
Most mods have a Github release, and depending on how they're set up, will have different ways of downloading them.

===== Github Releases Tab =====
The first and most common way to download a mod is through the releases tab of the mod. The releases section is on the right-hand-side of the page. Clicking on the Releases text shows all releases, with the most recent release being displayed directly below it. I'm using my own mod as an example, as many mods follow a similar scheme.

[[File:Modding Guide - Github Releases Button.png|1080x1080px]]
From here, you will want to go to the release of choice. Clicking on the latest release is usually the best way, but some may have several releases for different mods, especially those with multiple mods in the same repository (such as [https://github.com/digitalbarrito/BootlegIndustries Bootleg Industries]). In this case, there is one mod release to check, being the latest, and you'll want to download the pre-compiled zip. Some mods may have several pre-compiled zips, where you can choose specific mod versions to your liking.

[[File:Modding Guide - Github Releases Download.png|1080x1080px]]

===== Pre-compiled Zips In the Repository =====
Some mods (such as for this example, [https://github.com/Kadaire/K-Tech-Industrial-of-Mars/ K-Tech Industrial of Mars]) have the pre-compiled zips stored within the repository itself. There are a few ways to download these. The first is to download the entire repository using either the download zip from the code button, or the download source button from the releases tab. From there, you can open the zip, go through the folders and extract the zip files you want.

[[File:Modding Guide - Github Download A.png]][[File:Modding Guide - Github Download B.png]]

The second way is to download each zip individually. For this, navigate through the repository's folder structure, open the desired zip, and press the download button. This method is considerably slower, and only a good idea if you only want one or two of the mods offered through this method.

[[File:Modding Guide - Github Download C.png|1080x1080px]]

===== Compiling Uncompiled Mods =====
Several mods are provided on the repository, but don't have either a release or compiled zip elsewhere. These are more difficult as you have to manually zip each mod yourself. First you'll want to do similar to the last section with downloading the repository's files (see above). After this, you'll want to extract the entire folder to an accessible folder (the downloads folder is usually a reliable choice). Next, you'll decide which mod you want to download. For this example, I'll be using Bootleg Industries's TurnNBurn mod, which unlike the PDT laser and ERM420 mods from that collection, lacks a release.
The first step is to find the mod's ModMain.gd file. This file is the core to where the game loads the mod, and if it's not in the right place, it will fail to load.

[[File:Modding Guide - Compiling Part A.png]]

Once you have found the ModMain.gd file, you go to the previous folder above it, and compress the folder that the ModMain is contained in. On Windows 11, this can be done by right clicking the folder, then clicking 'Compress to...", then clicking "ZIP File". On Windows 10, this can be done by right clicking the folder, then "Send to", then "compressed folder" (no screenshot for the latter as I don't have a Win10 device on hand while writing this).

[[File:Modding Guide - Compiling Part B.png]]

This should produce a zip that can be loaded by the game.

==== Downloading Mods from Nexus ====
This step is rather straightforward. Each mod on Nexus has a manual download button, which should show you the steps needed to download the zip just fine. Just follow through with the free options and you should have it downloaded in seconds.

[[File:Modding Guide - Downloading from Nexus.png|1080x1080px]]

==== Downloading Mods from Gitlab ====
Most of the old mods (pre-Za'Krin era mods) were hosted on the [https://gitlab.com/Delta-V-Modding/Mods modding Gitlab]. Most of these mods are very old, and are not guaranteed to work, however you can always ask for an updated version on the Discord in case you want a patch made.

[[File:Modding Guide - Downloading from Gitlab A.png]]

Once you have chosen the mod you want, most will provide a link to a CI artefacts link, where a large and obvious download button is provided for the zip.

[[File:Modding Guide - Downloading from Gitlab B.png]]

[[File:Modding Guide - Downloading from Gitlab C.png|1080x1080px]]

==== Downloading Mods from Other Places ====
This guide has gone over most of the hosting sites used for mods, however some may be downloaded from elsewhere. Most others you'll find will be on the Discord, which is rather easy and intuitive to download from and will work out of the box. Other sites may be used in future, after this guide was written, and if they become common enough, may get a section of their own.
== Uninstalling mods ==
Removing mods is generally an easy of a step as installing, and in many cases easier as if you just want to stop using mods entirely, as you only need to remove the <code>--enable-mods</code> launch parameter. Stopping mods from loading is effectively as easy as moving them to a different folder or changing the file's extension. The most common methods involve creating a subfolder named <code>disabled</code> and moving unwanted mods there, or adding a <code>.disabled</code> extension to the mod to disable it. '''NOTE:''' these methods may not work when loaded using mods that extend modloader functionality.

However, some mods (namely mods that add content in the form of ships, equipment, locations, and the like) may need extra steps to go through before a save that had been used can be loaded without that mod. Mods generally fall into one of three categories when it comes to footprint: none (lightweight mods), null equipment, and ghost slots.

==== None (Lightweight Mods) ====
These mods generally don't add much in terms of functionality. Most of the time they compliment without adding anything 'new', or add onto existing vanilla mechanics that the vanilla game can handle perfectly fine.

You will be free to add and remove these mods at will.

==== Null Equipment ====
Although these mods will have slight differences depending on which equipment becomes unavailable (ships or equipment), they're classified under the same category as both require a very minor task to be vanilla-compatible.

'''New Equipment:''' Any equipment added by mods that is compatible with vanilla slots will just not appear on the slots they were fitted to, and it will act like an empty equipment worth 0 E$. The only loss with this is whatever the equipment cost to apply, which could easily be sold with the mod enabled to get the money back.

'''New Ships:''' New ships will work very similarly to new equipment, in the fact they just disappear from the fleet menu. '''HOWEVER''', if the ship is the active ship, it will crash the game. The solution is to just switch to a vanilla ship before removing the mod.

==== Ghost Slots ====
Ghost slots appear when any mod that physically changes how slots are handled on a ship gets removed, and act in one of two ways:

'''Mirrored Slots:''' these appear with two or more slots on the equipment screen with the same title, and always share the same equipment regardless when one changes. These can also work vice versa where one slot type on the equipment screen changes equipment on the ship in more than one place.

'''Empty Slots:''' these are slots on the equipment screen that can be interacted with and have equipment changed on, but doesn't get applied on the ship.

These happen when a mod that altered the way slots are used on a ship gets removed. This can be counteracted by buying a new ship from the dealer.

== Useful Links ==

* [https://discord.gg/dv ΔV Discord] ([https://discord.com/channels/426287934870781952/1175491436788060301 Workshop Postboard], [https://discord.com/channels/426287934870781952/1252866978075512863 Mod Dev Discussion/Help thread])
* [[Mod List|Wiki mod list]]
* [https://www.nexusmods.com/dvringsofsaturn ΔV Nexusmods]
* [https://gitlab.com/Delta-V-Modding/Mods ΔV Gitlab]

Special thanks goes to Za'Krin for helping spark the recent surge in mods for this game (including the small handful of mods I've written), as well as providing the backbone for most mods produced starting from the mod Industries of Enceladus a few months back.

Wiki:Style guide

Hev — Sun, 30 Aug 2026 05:27:12 GMT

← Older revision		Revision as of 05:27, 30 August 2026
Line 10:		Line 10:
	* Image used to showcase equipment should be shown on a K37, and uses the leftmost hardpoint (if applicable). Images can be different resolutions, but a good size to use is a 500x330 resolution and use the thumbnail image type.		* Image used to showcase equipment should be shown on a K37, and uses the leftmost hardpoint (if applicable). Images can be different resolutions, but a good size to use is a 500x330 resolution and use the thumbnail image type.
	* If you want to source a layered file that was used to produce an image, given restrictions for the wiki's file uploads, you would have to link it externally and add the URL to the file's description when uploading.		* If you want to source a layered file that was used to produce an image, given restrictions for the wiki's file uploads, you would have to link it externally and add the URL to the file's description when uploading.

			=== Page Prefixes ===

			Some pages should preferably use a suffix for specific content:

			* '''Mod:''' - Page dedicated to a specific mod
			* '''Modding:''' - Guide that covers a modding topic

Modding

Hev — Sun, 30 Aug 2026 05:23:25 GMT

Added `Modding:` prefix to mod guides

← Older revision		Revision as of 05:23, 30 August 2026
Line 3:		Line 3:
	* [[Introduction to Modding]] - A how-to on installing and uninstalling mods with a lot of useful information for anyone looking to mod.		* [[Introduction to Modding]] - A how-to on installing and uninstalling mods with a lot of useful information for anyone looking to mod.
	* [[Mod List]] - A list of every known mod and tool repository for anyone looking for preexisting mods.		* [[Mod List]] - A list of every known mod and tool repository for anyone looking for preexisting mods.
	* [[Writing Your Own Mod]] - Beginning of a collection of guides that cover the basics on writing a mod.		* [[Modding:Writing Your Own Mod\|Writing Your Own Mod]] - Beginning of a collection of guides that cover the basics on writing a mod.
	* [[Using the Godot Editor]] - Guide to setting up mods to be run in the Godot Editor.		* [[Using the Godot Editor]] - Guide to setting up mods to be run in the Godot Editor.

Guides

Hev — Sun, 30 Aug 2026 05:23:08 GMT

Added `Modding:` prefix to mod guides

← Older revision		Revision as of 05:23, 30 August 2026
Line 34:		Line 34:

	* [[Introduction to Modding]]		* [[Introduction to Modding]]
	* [[Writing Your Own Mod]]		* [[Modding:Writing Your Own Mod\|Writing Your Own Mod]]

Writing Your Own Mod

Hev — Sun, 30 Aug 2026 05:22:34 GMT

Hev moved page Writing Your Own Mod to Modding:Writing Your Own Mod without leaving a redirect

New page

This guide covers the basics to getting started with writing a mod for ΔV. It is a modified version of [https://github.com/ZakrinYoran/Delta-V-Modding Za'krin's modding guide], where a large portion of the credit will be given.

This guide is written for Windows users, however the equivalent for operating systems such as Linux and OS X should work extremely similarly.

= Setup =
This section will cover the resources used for modding. They are heavily encourage to be used, as it will make your life considerably easier with their use.

=== Downloaded Resources ===
First off, you will need a copy of [https://store.steampowered.com/app/846030/DV_Rings_of_Saturn/ ΔV: Rings of Saturn] as a decompiled copy of the game will be used as a reference.

* A demo build will work fine as well, as at the time of writing, it and the full release are identical.

Second, the [https://godotengine.org/download/archive/3.6-stable/ Godot Game Engine], specifically version 3.6, which is used for the writing and editing of mods.

Third, [https://github.com/GDRETools/gdsdecomp/releases/latest Godot Reverse Engineering Tools] (a.k.a. GDRE), which is used to decompile the game.

Extract and move these to somewhere accessible.

=== Decompiling ===
The process for decompiling ΔV is fairly straightforward when using GDRE.

* Open the folder containing <code>gdre_tools.exe</code> in your file explorer.
* Open the ΔV game folder (on steam it's Right-Click -> Manage -> Browse Local Files).
* Copy <code>Delta-V.pck</code> (not <code>.exe</code>!) into the GDRE folder.
* Open GDRE and select "Recover Project" from the "RE Tools" menu.
* Select <code>Delta-V.pck</code> and wait for the file verification process to finish.
* Leave the default settings, set the folder location, and extract the project.
* Once the extraction process is finished, ΔV should be ready for import into Godot.

In the case where there have been problems using the GUI, the command line can be used instead. To use that instead of the GUI, follow the below steps:

* Copy <code>Delta-V.pck</code> into the GDRE folder as before.
* Open windows command prompt and <code>cd</code> into the folder (e.g. <code>cd C:\godotTools\GDRE_tools</code>)
* Run <code>gdre_tools.exe</code> with the following command: <code>gdre_tools --headless --recover=Delta-V.pck</code>. This will create a new folder called containing the decompiled game files.
* Move the decompiled files to wherever you want your project located.

For more detail on the usage of GDRE, see the [https://github.com/bruvzg/gdsdecomp?tab=readme-ov-file#usage usage section of their readme].

=== Importing into Godot ===
Loading the decompiled game files into Godot is rather simple.

* Open your copy of Godot and select the 'Import' option.
* Navigate to where you stored your decompiled version of ΔV and select the <code>project.godot</code> file.
* Launch the Delta-V Project, and let Godot import all of the files.

The initial import process will take a couple of minutes at worst if everything is followed. In the case where it takes a significant amount of time, you may have used a newer version of GDRE. If it appears to freeze, don't worry, it is still processing, and can be used regardless. After the first import, future loading times usually will be significantly better, although it is always better to use GDRE 0.5.3 to ensure quick loading times.

It may also be worth taking a look at the guide for modding with the Godot Editor, [[Using the Godot Editor|which can be found here]].

= Mod Structure =
ΔV mods (and Godot projects in general) work in a hierarchical file structure centered around the project's root folder (referred to as <code>res://</code>). If any file isn't referenced relative to the executed code, it will be relative to <code>res://</code>. There are also other file system prefixes, such as <code>user://</code> and the OS's file system paths, however these are very rarely used, especially for modding, so will only be covered briefly later down the line.

=== Mod Folder Structure ===
Mod zips will be mounted to the root as how they appear in the zip. For example, a zip with the structure of <code>A_Mod.zip/ModFolder/ModMain.gd</code> is the equivalent to having added a folder named ModFolder to the root folder and adding the ModMain.gd file in it. In terms of <code>res://</code>, it appears like <code>res://ModFolder/ModMain.gd</code>. Mods don't need to follow this structure explicitly, however it is extremely convenient when structured like this as it makes it easy to work with in the editor.

=== ModMain.gd ===
The <code>ModMain.gd</code> file is just about the most important file in the entirety of the mod. It is where the mod's resources are initially loaded and run. Even if only a single file is needed to be loaded to get the entire mod to run, it will not work if not referenced here.

It can be as simple or complex as you like, however the commonly utilized format works as follows:
extends Node
# Set mod priority if you want it to load before/after other mods
# Mods are loaded from lowest to highest priority, default is 0
const MOD_PRIORITY = 0
# Name of the mod, used for writing to the logs
const MOD_NAME = "Example Mod"
const MOD_VERSION = "1.0.0"
# Path of the mod folder, automatically generated on runtime
var modPath:String = get_script().resource_path.get_base_dir() + "/"
# Required var for the replaceScene() func to work
var _savedObjects := []
var modConfig = {}
#Initializes the configuration variable. Used by loadSettings.
# Initialize the mod
# This function is executed before the majority of the game is loaded
# Only the Tool and Debug AutoLoads are available
# Script and scene replacements should be done here, before the originals are loaded
func _init(modLoader = ModLoader):
l("Initializing DLC")

loadDLC() # preloads DLC as things may break if this isn't done

# At this point, you are free to start modifying your code.
installScriptExtension("Example/Script.gd") # Example of how the file structure. Folders are relative to this file
replaceScene("Example/Scene.tscn") # Similar to the example script

# Do stuff on ready
# At this point all AutoLoads are available and the game is loaded
func _ready():
l("Readying")
l("Ready")

# Helper function to extend scripts
# Loads the script you pass, checks what script is extended, and overrides it
func installScriptExtension(path:String):
var childPath:String = str(modPath + path)
var childScript:Script = ResourceLoader.load(childPath)
childScript.new()
var parentScript:Script = childScript.get_base_script()
var parentPath:String = parentScript.resource_path
l("Installing script extension: %s <- %s" % [parentPath, childPath])
childScript.take_over_path(parentPath)

# Helper function to replace scenes
# Can either be passed a single path, or two paths
# With a single path, it will replace the vanilla scene in the same relative position
func replaceScene(newPath:String, oldPath:String = ""):
l("Updating scene: %s" % newPath)
if oldPath.empty():
oldPath = str("res://" + newPath)
newPath = str(modPath + newPath)
var scene := load(newPath)
scene.take_over_path(oldPath)
_savedObjects.append(scene)
l("Finished updating: %s" % oldPath)
# Instances Settings.gd, loads DLC, then frees the script.
func loadDLC():
l("Preloading DLC as workaround")
var DLCLoader:Settings = preload("res://Settings.gd").new()
DLCLoader.loadDLC()
DLCLoader.queue_free()
l("Finished loading DLC")
# Func to print messages to the logs
func l(msg:String, title:String = MOD_NAME, version:String = MOD_VERSION):
Debug.l("[%s V%s]: %s" % [title, version, msg])
The additional functions provided with this script are not necessary, however are used by effectively every mod, and are left for convenience.

'''<big>Runtime variables</big> ('''variables used by the mod menu for the workings of other functions'''):'''

<code>const MOD_PRIORITY = 0</code>: The load priority of the mod. Zero by default, but can be changed to any integer. If a mod has the same priority, then it will go in alphabetical order of the zip files.

<code>const MOD_NAME = "" AND const MOD_VERSION = "1.0.0"</code>: Mod name and versions. Directly used for logging purposes with the <code>l()</code> function later down the line, however is also used by the mod menu if you choose to install it (more on that later)

<code>var modPath:String = get_script().resource_path.get_base_dir() + "/"</code>: used to get the ModMain's file path. Used for other functions so is best leaving alone.

<code>var _savedObjects := []</code>: variable used by the <code>replaceScene()</code> function. This should be left blank.

'''<big>System functions</big> ('''static functions that should be where the body of your ModMain are'''):'''

<code>func _init(modLoader = ModLoader):</code>: Any functions loaded in this function are done as soon as the script is run. The modloader variable is used to load various functions from the modloader as autoloads are not available yet.

<code>loadDLC()</code> should be loaded as early as possible in the <code>_init()</code> function. Ensures DLC loads properly as it breaks when mods are loaded for whatever reason

<code>func _ready():</code>: Functions loaded here will be loaded once everything else has loaded and all autoloads are available.

'''<big>Load Functions</big> ('''functions used to load resources from your mod'''):'''

'''replaceScene'''

<code>replaceScene()</code> overrides or replaces a vanilla scene.

* <code>newPath:String</code> is the path to your modded scene, relative to the mod folder.
* <code>oldPath:String</code> is an optional path to the vanilla scene you are overriding, if no path is provided, the same path as your new scene will be used, but relative to <code>res://</code> instead.
* Replacing scenes requires loading the scene, which loads any resources present in the scene. Make sure any resources present (e.g. scripts) are modified before the scene is replaced.

'''Examples:'''

<code>replaceScene("ships/RA-TRTL.tscn")</code> loads a scene from your mod at <code>res://ModFolder/ships/RA-TRTL.tscn</code> that modifies the K37 ship scene at the vanilla location <code>res://ships/RA-TRTL.tscn</code>.

<code>replaceScene("modifications/ships/RA-TRTL.tscn","res://ships/RA-TRTL.tscn")</code> loads a scene in your mod's folder at <code>res://ModFolder/modifications/ships/RA-TRTL.tscn</code> which modifies the K37 scene at the vanilla location <code>res://ships/RA-TRTL.tscn</code>.

'''installScriptExtension'''

<code>installScriptExtension()</code> is used to override vanilla script behavior.

* <code>path:String</code> is the path to the new script, relative to the root of the mod folder.
* The [https://docs.godotengine.org/en/3.5/tutorials/scripting/gdscript/gdscript_basics.html#inheritance inherited] script gets overridden, whenever it is used, your modified script will instead be applied.
* Inheritance is very powerful, and can be used to override most vanilla behavior, with some exceptions.
* Scripts must be extended before they are loaded. Once applied to a node, the script is locked in and modifying the script resource will not affect existing instances.
* It can be used to load new scripts, however it is best used to modify preexisting scripts from the vanilla game.

'''Example:'''

<code>installScriptExtension("ships/Shipyard.gd")</code> loads a script from <code>res://ModFolder/ships/Shipyard.gd</code>

==== Add Translations ====
Translations are a useful part of any mod that adds something visually. They can be useful both for providing localized resources for anyone willing to translate, as well as giving names to any system names that couldn't be written as plain text (such as ship names). Translations are best handled through the <code>updateTL()</code> function, with the following function itself being placed somewhere within the ModMain file.:

# Helper script to load translations using csv format
# `path` is the path to the transalation file
# `delim` is the symbol used to seperate the values
# `useRelativePath` setting it to false uses a `res://` relative path instead of relative to the file
# `fullLogging` setting it to false reduces the number of logs written to only display the number of translations made
# example usage: updateTL("i18n/translation.txt", "|")
func updateTL(path:String, delim:String = ",", useRelativePath:bool = true, fullLogging:bool = true):
if useRelativePath:
path = str(modPath + path)
l("Adding translations from: %s" % path)
var tlFile:File = File.new()
tlFile.open(path, File.READ)
var translations := []

var translationCount = 0
var csvLine := tlFile.get_line().split(delim)
if fullLogging:
l("Adding translations as: %s" % csvLine)
for i in range(1, csvLine.size()):
var translationObject := Translation.new()
translationObject.locale = csvLine[i]
translations.append(translationObject)
while not tlFile.eof_reached():
csvLine = tlFile.get_csv_line(delim)
if csvLine.size() > 1:
var translationID := csvLine[0]
for i in range(1, csvLine.size()):
translations[i - 1].add_message(translationID, csvLine[i].c_unescape())
if fullLogging:
l("Added translation: %s" % csvLine)
translationCount += 1
tlFile.close()
for translationObject in translations:
var pms = translationObject.get_message_list()
var pmL = []
for m in pms:
var pt = translationObject.get_message(m)
pmL.append([m,pt])
var tr = TranslationServer.translate(pms[0])
TranslationServer.add_translation(translationObject)
var pms2 = translationObject.get_message_list()
var tr2 = TranslationServer.translate(pms[0])
pass
l("%s Translations Updated" % translationCount)

Syntax for the command is handled as <code>updateTL(path, delim)</code> where <code>path</code> is the path relative to the ModMain, and <code>delim</code> is the character or string which the translation identifier and text are split with. <code>|</code> is commonly used as it is used very rarely. Other optional booleans include <code>useRelativePath</code> which while it's enabled (and is by default), lets you use paths relative to the ModMain.gd file instead of the full paths, and <code>fullLogging</code> makes the command more verbose and logs everything that it is doing, and is enabled by default.

'''Example''':

<code>updateTL("i18n/en.txt","|")</code>

this loads a translation file at <code>res://ModFolder/i18n/en.txt</code> and used the <code>|</code> character as a delimiter.

Formatting for each translation file goes as follows:
locale<delim character><localization code>

LOCALIZATION_STRING<delim character>This is a translated string
<delim character> is whatever character is used as the delimination character in the <code>updateTL()</code> call.

locale|<localization code> is the identifier for the language to translate to. The translations currently supported by the game are as follows:

* cs_CZ - Czech (Czech Republic)
* de - German
* el_GR - Greek (Greece)
* en - English
* es - Spanish
* fr - French
* hu_HU - Hungarian (Hungary)
* it_IT - Italian (Italy)
* ja - Japanese
* ko_KR - Korean (South Korea)
* nb_NO - Norwegian Bokmål (Norway)
* nl_NL - Dutch (Netherlands)
* pl - Polish
* pt_BR - Portugese (Brazil)
* ru_RU - Russian (Russia)
* th - Thai
* uk_UA - Ukrainian (Ukraine)
* zh_CN - Chinese (China)
* zh_HK - Chinese (Hong Kong)

==== Config File ====
Config files are useful for making variables or settings configurable to the user. Given the nature of it, it does require a bit more setup and a lot of extra work outside of the ModMain, which will be deferred to it's own wiki page once it is written. In the meantime, you may benefit at looking at mods that use it for reference.

To load a config file, you'll need this script at the bottom of your ModMain.gd file:
# This function is a helper to provide any file configurations to your mod
# You may want to replace any "Example" text with your own identifier to make it unique
# Check the example Settings.gd file for how to setup that side of it
func loadSettings():
installScriptExtension("Settings.gd")
l(MOD_NAME + ": Loading mod settings")
var settings = load("res://Settings.gd").new()
settings.load_ExampleMod_FromFile()
settings.save_ExampleMod_ToFile()
modConfig = settings.ExampleMod
l(MOD_NAME + ": Current settings: %s" % modConfig)
settings.queue_free()
l(MOD_NAME + ": Finished loading settings")
Replace any instance of <code>ExampleMod</code> with a unique identifier, preferably your mod's name. Remember this as you'll be using this later. It's best to use the find and replace tool (Ctrl + R in Godot) for this to make it easier, as well as prevent mistakes.

Once you've added this, add a line calling <code>loadSettings()</code> (leaving it just like that and pasting it in will work) in the <code>_init()</code> function before you make a call to <code>loadDLC()</code> to ensure it gets loaded properly.

Now you'll want to setup the config file itself. Make a new script in the same folder as the ModMain.gd file, and name it <code>Settings.gd</code>

Once you've made the file, open it and insert the following text into it:
extends "res://Settings.gd"
# You may want to change many of the variable names to provide a unique identifier
# Make sure anything read by the ModMain is consistent with this file or they will not work
# These are default config values
# Any value not set in the config file will generate the missing values exactly as these are
var ExampleMod = {
   "section":{
   "setting":true,
   "string_option":"setting_value"
   },
   "section2":{
   "option":false,
   "numerical_option":1000,
   },
   "input":{ # Defaults for anything that uses keybinds
   "key_setting_a":[ "R" ],
   "key_setting_b":[ "Shift" ],
   },
}
# The config file name. Make sure you set something unique
# Config is set to the cfg folder to make it easy to find
var ConfigPath = "user://cfg/ExampleMod.cfg"
var CfgFile = ConfigFile.new()
func _ready():
   var dir = Directory.new()
   dir.make_dir("user://cfg")
   load_ExampleMod_FromFile()
   save_ExampleMod_ToFile()
func save_ExampleMod_ToFile():
   for section in ExampleMod:
   for key in ExampleMod[section]:
   CfgFile.set_value(section, key, ExampleMod[section][key])
   CfgFile.save(ConfigPath)
func load_ExampleMod_FromFile():
   var error = CfgFile.load(ConfigPath)
   if error != OK:
   Debug.l("Example Mod: Error loading settings %s" % error)
   return
   for section in ExampleMod:
   for key in ExampleMod[section]:
   ExampleMod[section][key] = CfgFile.get_value(section, key, ExampleMod[section][key])
   loadKeymapFromConfig()
# Keybind setting handlers
func loadKeymapFromConfig():
   for action_name in ExampleMod.input:
   var addAction = true
   for m in InputMap.get_actions():
   if m == action_name:
   addAction = false
   if addAction:
   InputMap.add_action(action_name)
   for key in ExampleMod.input[action_name]:
   var event = InputEventKey.new()
   event.scancode = OS.find_scancode_from_string(key)
   InputMap.action_add_event(action_name, event)
   emit_signal("controlSchemeChaged")
Once again, you'll need to change all instances of ExampleMod to the identifier you chose earlier. Find and Replace is heavily recommended with how many instances of ExampleMod there are.

Once set up, you can query the settings from anywhere in the game. An example of how it would be queried, based on the above example, is as follows:
var setting_value = Settings.ExampleMod["section"]["setting"]
print("setting value: %s") % setting_value
The <code>setting_value</code> variant queries the settings for the ExampleMod's settings list, looks for the section named "section", then gets the value of "setting" from that section. It then prints "setting value: true"

=== Mod.manifest File ===
The mod.manifest is a more recent addition to the modding scope. It's not a required file by any means, however it's an adopted standard to provide additional information to any mods looking to take info from said mod. It takes the form of a standard .ini config file, and as many or as few of these can be filled out, and blank sections can be left as <code>""</code>. Current mods that use this may or may not support the removal of lines, so it is best to leave them in anyway.

An example of the file's structure is as follows:
[package]

id="test.ExampleMod"
name="Example Mod"
version="1.0.0"
description="A example description"
group="testing"
github_homepage="<nowiki>https://github.com/example/repo/</nowiki>"
github_releases="<nowiki>https://github.com/example/repo/releases/</nowiki>"
discord_thread="<nowiki>https://discord.gg/dv/</nowiki>"
nexus_page="<nowiki>https://www.nexusmods.com/dvringsofsaturn/mods/</nowiki>"
donations_page="<nowiki>https://example.url</nowiki>"
wiki_page="<nowiki>https://example.url</nowiki>"
custom_link="<nowiki>https://example.url</nowiki>"
custom_link_name="Example url for the custom link"

[manifest_definitions]

manifest_version=1

<code>[package]</code> is the identifer for the manifest's data section in manifest versions 1 and 2, and should be left alone as such. It is planned to be depreciated in future manifest versions.

<code>id</code> The unique identifier of the mod. Useful for differentiation with other mods that may use the same name. The common formatting is <code>(nick)name.ModName</code>, but it can be whatever you like.

<code>name</code> The mod's display name. Used for any mods that may need to fetch other mods. Similar to the <code>MOD_NAME</code> constant in the ModMain file, however is preferred for use over that name.

<code>version</code> The mod's version number. Can be any string, however is best kept numerical for version comparing. Similar to the <code>MOD_VERSION</code> constant in the ModMain file, however is preferred for use over that version identifier.

<code>description</code> A string used to describe the mod. Can be either plain text or a translation string.

<code>group</code> Used to group mods together. It's not currently used by any known mods, but useful to have for future reference.

<code>github_homepage</code> The Github URL for the mod.

<code>github_releases</code> The Github releases page, if the mod has one. Same as the <code>github_homepage</code> string, just with <code>releases/</code> appended to the end.

<code>discord_thread</code> URL for an associated discord thread, channel or server. Current uses link to the #workshop channel in the ΔV Discord.

<code>nexus_page</code> URL for the Nexusmods page of the mod.

<code>donations_page</code> URL for a donations page if the writer chooses to add one.

<code>wiki_page</code> URL for any associated wiki page, be it ΔV Wiki, Github wiki, or another page.

<code>custom_link</code> A custom URL for an action button. Can be whatever you choose.

<code>custom_link_name</code> A string used for any text tooltips/labels used with the custom link. Can be either plain text or a translation string.

<code>[manifest_definitions]</code> is the identifier for the manifest-specific information. This currently contains only the manifest version number, but may contain more options in future manifest versions

<code>manifest_version</code> The manifest formatting version. If not provided, a version number of <code>1</code> is assumed.

Achievements

Hev — Sat, 29 Aug 2026 00:45:29 GMT

← Older revision		Revision as of 00:45, 29 August 2026
Line 368:		Line 368:
	\|[[File:Achievement DrivingStickUnlocked.jpg\|64x64px]]		\|[[File:Achievement DrivingStickUnlocked.jpg\|64x64px]]
	\|-		\|-
	\|And His Name Will Be Forty		\|And His Name Will Be Forty and Four
	and Four
	\|Play the game when there is more than 44 concurrent players		\|Play the game when there is more than 44 concurrent players
	\|Be online when there at least 44 players. In the main menu and pause menu, the number in the top corner displays the current number of players online		\|Be online when there at least 44 players. In the main menu and pause menu, the number in the top corner displays the current number of players online
Line 469:		Line 468:
	*The ''Firefly'' achievement is a reference to a TV show of the same name		*The ''Firefly'' achievement is a reference to a TV show of the same name
	*The ''Play Dead'' achievement's internal name is CrazyIvan, which is a reference to the [https://firefly.fandom.com/wiki/Crazy_Ivan maneuver of the same name]		*The ''Play Dead'' achievement's internal name is CrazyIvan, which is a reference to the [https://firefly.fandom.com/wiki/Crazy_Ivan maneuver of the same name]
			* The ''And His Name Will Be Forty and Four'' achievement is a reference to the Polish poem [https://en.wikipedia.org/wiki/Dziady_(poem) Dziady], more specifically the line in part III: "The Son of a foreign mother, in his blood old heroes And his name will be forty and four"
			* The ''Squadron 303'' achievement is a reference to the [https://en.wikipedia.org/wiki/No._303_Squadron_RAF 303rd Squadron of the RAF], one of the two Polish squadrons who fought in the battle of Britain