Modding:Writing Your Own Mod - Revision history

Hev at 17:57, 17 September 2026

2026-09-17T17:57:57Z

← Older revision		Revision as of 17:57, 17 September 2026
Line 47:		Line 47:

	= GDScript =		= GDScript =
	Delta-V (and by extension, any and all mods written for it) are written in the GDScript language, Godot's duck-typed language. You are not required to know it or even use it for mods, even relatively large mods can be made without ever writing a line of code (~~e.g.~~ Derelict Delights was completely codeless for a good while), however it is still highly recommended that you are at least able to understand it and be able to write some code if needs be.		Delta-V (and by extension, any and all mods written for it) are written in the GDScript language, Godot's duck-typed language. You are not required to know it or even use it for mods, even relatively large mods can be made without ever writing a line of code (for example, Derelict Delights was completely codeless for a good while), however it is still highly recommended that you are at least able to understand it and be able to write some code if needs be.

	~~Some~~ good resources to learn would be [https://www.gdquest.com/ GDQuest] (it is intended for writing a game, but the same concepts can transfer pretty easily), and by reading the [https://docs.godotengine.org/en/3.6/ Godot Docs]. You can also access the docs from within the Godot editor.<blockquote>		If you're not well versed in GDScript, or in programming in general, the best thing you can do is ask on the [https://discord.gg/dv Delta-V Discord], specifically in the [https://discord.com/channels/426287934870781952/1252866978075512863 Modding Help/Discussion thread]. There are a few users who are perfectly willing to provide you directions and other help when making a mod, even with some more advanced concepts if needs be.

			Additionally, some good resources to learn would be [https://www.gdquest.com/ GDQuest] (it is intended for writing a game, but the same concepts can transfer pretty easily), and by reading the [https://docs.godotengine.org/en/3.6/ Godot Docs]. You can also access the docs from within the Godot editor.<blockquote>
	'''<big>NOTICE:</big>'''		'''<big>NOTICE:</big>'''

Hev at 16:10, 16 September 2026

2026-09-16T16:10:55Z

← Older revision		Revision as of 16:10, 16 September 2026
Line 51:		Line 51:
	Some good resources to learn would be [https://www.gdquest.com/ GDQuest] (it is intended for writing a game, but the same concepts can transfer pretty easily), and by reading the [https://docs.godotengine.org/en/3.6/ Godot Docs]. You can also access the docs from within the Godot editor.<blockquote>		Some good resources to learn would be [https://www.gdquest.com/ GDQuest] (it is intended for writing a game, but the same concepts can transfer pretty easily), and by reading the [https://docs.godotengine.org/en/3.6/ Godot Docs]. You can also access the docs from within the Godot editor.<blockquote>
	'''<big>NOTICE:</big>'''		'''<big>NOTICE:</big>'''
	'''DO NOT USE LLMs/AI'''. The only thing that will teach you is how to ask the LLM to do things. You, personally, won’t learn a thing. And LLMs, by design, will give you false information as they’re just very advanced word-suggestion-algorithms. They’re not programmed to say, “I don’t know” so they just put words together that statistically should go together, but don’t always. So it’ll give you a ton of wrong/broken/bloated/vulnerable code. So please, for the love of anything you hold dear, do it right.
			'''DO NOT USE LLMs/AI'''. The only thing that will teach you is how to ask the LLM to do things. You, personally, won’t learn a thing. And LLMs, by design, will give you false information as they’re just very advanced word-suggestion-algorithms. They’re not programmed to say, “I don’t know” so they just put words together that statistically should go together, but don’t always. So it’ll give you a ton of wrong/broken/bloated/vulnerable code. So please, for the love of anything you hold dear, do it right.
	</blockquote>		</blockquote>

Hev at 16:10, 16 September 2026

2026-09-16T16:10:31Z

← Older revision		Revision as of 16:10, 16 September 2026
Line 49:		Line 49:
	Delta-V (and by extension, any and all mods written for it) are written in the GDScript language, Godot's duck-typed language. You are not required to know it or even use it for mods, even relatively large mods can be made without ever writing a line of code (e.g. Derelict Delights was completely codeless for a good while), however it is still highly recommended that you are at least able to understand it and be able to write some code if needs be.		Delta-V (and by extension, any and all mods written for it) are written in the GDScript language, Godot's duck-typed language. You are not required to know it or even use it for mods, even relatively large mods can be made without ever writing a line of code (e.g. Derelict Delights was completely codeless for a good while), however it is still highly recommended that you are at least able to understand it and be able to write some code if needs be.

	Some good resources to learn would be [https://www.gdquest.com/ GDQuest] (it is intended for writing a game, but the same concepts can transfer pretty easily), and by reading the [https://docs.godotengine.org/en/3.6/ Godot Docs]. You can also access the docs from within the Godot editor.		Some good resources to learn would be [https://www.gdquest.com/ GDQuest] (it is intended for writing a game, but the same concepts can transfer pretty easily), and by reading the [https://docs.godotengine.org/en/3.6/ Godot Docs]. You can also access the docs from within the Godot editor.<blockquote>
	'''<big>NOTICE:</big>'''		'''<big>NOTICE:</big>'''
	'''DO NOT USE LLMs/AI'''. The only thing that will teach you is how to ask the LLM to do things. You, personally, won’t learn a thing. And LLMs, by design, will give you false information as they’re just very advanced word-suggestion-algorithms. They’re not programmed to say, “I don’t know” so they just put words together that statistically should go together, but don’t always. So it’ll give you a ton of wrong/broken/bloated/vulnerable code. So please, for the love of anything you hold dear, do it right.		'''DO NOT USE LLMs/AI'''. The only thing that will teach you is how to ask the LLM to do things. You, personally, won’t learn a thing. And LLMs, by design, will give you false information as they’re just very advanced word-suggestion-algorithms. They’re not programmed to say, “I don’t know” so they just put words together that statistically should go together, but don’t always. So it’ll give you a ton of wrong/broken/bloated/vulnerable code. So please, for the love of anything you hold dear, do it right.
			</blockquote>

	= Mod Structure =		= Mod Structure =

Hev: Updated GDRE note and added section for GDScript

2026-09-16T16:10:08Z

Updated GDRE note and added section for GDScript

← Older revision		Revision as of 16:10, 16 September 2026
Line 44:		Line 44:
	* Launch the Delta-V Project, and let Godot import all of the files.		* 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 =
			Delta-V (and by extension, any and all mods written for it) are written in the GDScript language, Godot's duck-typed language. You are not required to know it or even use it for mods, even relatively large mods can be made without ever writing a line of code (e.g. Derelict Delights was completely codeless for a good while), however it is still highly recommended that you are at least able to understand it and be able to write some code if needs be.

			Some good resources to learn would be [https://www.gdquest.com/ GDQuest] (it is intended for writing a game, but the same concepts can transfer pretty easily), and by reading the [https://docs.godotengine.org/en/3.6/ Godot Docs]. You can also access the docs from within the Godot editor.
			'''<big>NOTICE:</big>'''
			'''DO NOT USE LLMs/AI'''. The only thing that will teach you is how to ask the LLM to do things. You, personally, won’t learn a thing. And LLMs, by design, will give you false information as they’re just very advanced word-suggestion-algorithms. They’re not programmed to say, “I don’t know” so they just put words together that statistically should go together, but don’t always. So it’ll give you a ton of wrong/broken/bloated/vulnerable code. So please, for the love of anything you hold dear, do it right.

	= Mod Structure =		= Mod Structure =

Hev at 01:47, 10 September 2026

2026-09-10T01:47:27Z

← Older revision		Revision as of 01:47, 10 September 2026
Line 408:		Line 408:

	==== Forking / copying code from other mods with a license ====		==== Forking / copying code from other mods with a license ====
	It is common for mods to have parts taken to help with the creation of someone else's mod, or be entirely forked (making a copy of the source) and modified for a user to make their own changes / additions that are either to help the original project or to make a copy that takes from the original works. ~~It is~~ always ~~a good idea to~~ make sure that you are properly respecting a mod's license if you are taking code from it.		It is common for mods to have parts taken to help with the creation of someone else's mod, or be entirely forked (making a copy of the source) and modified for a user to make their own changes / additions that are either to help the original project or to make a copy that takes from the original works. You should always make sure that you are properly respecting a mod's license if you are taking code from it.

	Depending on how the code is copied, the process for attributing a mod's license will vary:		Depending on how the code is copied, the process for attributing a mod's license will vary:

Hev at 22:51, 9 September 2026

2026-09-09T22:51:08Z

← Older revision		Revision as of 22:51, 9 September 2026
Line 400:		Line 400:

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

			== Licensing / Copyright ==

			==== Licensing code within your mod ====
			Licensing and/or copyrighting your work can be important if you want to have a set of guidelines for how you want others to use your code. Most authors choose an open source license that permits others to make use of their code with a basic set of limitations (e.g. no liability, does not provide rights to the mod's trademark, requiring the license to be appropriately copied by works incorporating it, etc.)
			If you are unsure of what license to use, check out https://choosealicense.com/ which provides a list of some very common open-source licenses and gives a breakdown as to what each one does. For a list of all licenses, check their [https://choosealicense.com/appendix/ appendix page].

			==== Forking / copying code from other mods with a license ====
			It is common for mods to have parts taken to help with the creation of someone else's mod, or be entirely forked (making a copy of the source) and modified for a user to make their own changes / additions that are either to help the original project or to make a copy that takes from the original works. It is always a good idea to make sure that you are properly respecting a mod's license if you are taking code from it.

			Depending on how the code is copied, the process for attributing a mod's license will vary:

			* Forking a mod:
			** Making a fork of a mod through the usual means (i.e. GitHub's fork feature) should keep the license from the original, since all files would have a copy
			** It is still worthwhile double checking to make sure the license is there regardless.
			** If you want to include your own license (if doing so is even permitted by the license of the source material, which most licenses may not without explicit permission from the author), check the next section on using code from others.
			* Using code from other mods and/or sources:
			** Current courtesy is to copy the licenses of all sourced materials into a folder named <code>.licenses</code> and have the license filename match the exact name of the source project.
			** It is also recommended to include a link to the source project within the license file to make sure the correct project is provided and credited.
			** For an example, check the [https://github.com/rwqfsfasxc100/IndustriesOfEnceladusRewrite/tree/main/.licenses .licenses folder for IoER] to see an example of the precedent.

Hev at 05:29, 30 August 2026

2026-08-30T05:29:35Z

← 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 =

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

2026-08-30T05:22:34Z

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

← Older revision

Revision as of 05:22, 30 August 2026

Hev: added manifest versioning to the mod.manifest section. still needs to be updated for ManifestV2

2025-08-12T02:53:17Z

added manifest versioning to the mod.manifest section. still needs to be updated for ManifestV2

← Older revision		Revision as of 02:53, 12 August 2025
Line 346:		Line 346:

	=== Mod.manifest File ===		=== 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. 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.		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:		An example of the file's structure is as follows:
Line 364:		Line 364:
	custom_link="<nowiki>https://example.url</nowiki>"		custom_link="<nowiki>https://example.url</nowiki>"
	custom_link_name="Example url for the custom link"		custom_link_name="Example url for the custom link"
	<code>[package]</code> is the identifer for the ~~mod~~ manifest, and should be left alone as such
			[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>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.
Line 391:		Line 396:

	<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>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.

Hev: improved the section on recommended modding requirements

2025-08-11T16:26:42Z

improved the section on recommended modding requirements

← Older revision		Revision as of 16:26, 11 August 2025
Line 11:		Line 11:
	* A demo build will work fine as well, as at the time of writing, it and the full release are identical.		* 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] which is used for the editing of mods.		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.

	* At the time of writing, Experimental versions past 1.74.5 have started to use Godot Engine 3.6, so we'll be using Godot 3.6 to edit the game, which should still support 3.5.3 for the current stable release builds.		Third, [https://github.com/GDRETools/gdsdecomp/releases/latest Godot Reverse Engineering Tools] (a.k.a. GDRE), which is used to decompile the game.

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

	* <s>0.5.3 is the optimal version to use, as versions newer than this can take between 30 mins to several hours to load into the editor. I have no idea why this happens, it just does.</s>
	* As of [https://github.com/GDRETools/gdsdecomp/releases/tag/v0.9.0-rc.2 0.9.0-rc2], this bug was fixed. The issue revolved around the MD5 hashes of resources being wrong, and Godot needing to re-import several hundred files (more info from my own explanation in the discord: [https://discord.com/channels/426287934870781952/1252866978075512863/1361841508294328362 here])

	Extract and move these to somewhere accessible.		Extract and move these to somewhere accessible.