Custom Asset Importing - Revision history

Joshcamas at 17:38, 23 May 2026

2026-05-23T17:38:37Z

← Older revision		Revision as of 13:38, 23 May 2026
Line 39:		Line 39:
	\|gltf_scene		\|gltf_scene
	\|path: the path to the gltf file		\|path: the path to the gltf file
			shader: (optional) the shader id to import.
	\|-		\|-
	\|Texture		\|Texture
Line 76:		Line 77:
	\|The path to the gltf / glb file		\|The path to the gltf / glb file
	\|-		\|-
	\|~~material~~		\|shader
	\|NO		\|NO
	\|"Ardenfall/SimpleDiffuse"		\|"Ardenfall/SimpleDiffuse"
	\|Defines the shader to be imported.		\|Defines the shader to be imported.
	Only a single shader per scene is supported at the moment.		Only a single shader per scene is supported at the moment.

	See Common Shaders for a list of shaders to try out.		See Common Shaders for a list of shaders to try out.

			If you leave it blank, will not import any materials.
	\|}		\|}

Joshcamas at 17:36, 23 May 2026

2026-05-23T17:36:11Z

@@ Line 26: / Line 26: @@
 === Built in Importers ===
 {| class="wikitable"
 |+
@@ Line 33: / Line 34: @@
 !Properties
 |-
-|SimpleModel
+|GLTFScene
 |Imports a GLTF file as a GameObject. Ideal for weapons, items, simple objects.
 You can define a built in material to use, and it will automatically apply said material + hook up included textures.
-|simple_model
+|gltf_scene
 |path: the path to the gltf file
 |-
@@ Line 55: / Line 56: @@
 |}
-=== Custom Importers ===
+==== GLTFScene ====
-Mods can define their own importers. Perhaps you built a tool that can easily create item data assets from a json file. You can register your own importer to read this file, and then you can easily import them as assets! Other mods can also rely on other's importers.
+A GLTF scene / model importer. Will import the GLTF object as a gameobject.
-Note an Importer doesn't need to only import a single path (this is why 'path' is a property). Perhaps a single importer takes in a model_path and a data_path, for example.
+Supports material applying using ModMaterialResolver.
-TODO
+Built on the [https://docs.unity3d.com/Packages/com.unity.cloud.gltfast@6.0/manual/index.html GLTFFast] library.
 === Example: A Custom Weapon ===
 TODO

Joshcamas at 18:09, 22 May 2026

2026-05-22T18:09:07Z

← Older revision		Revision as of 14:09, 22 May 2026
Line 25:		Line 25:
	</syntaxhighlight>		</syntaxhighlight>

	=== ~~Supported~~ Importers ===		=== Built in Importers ===
			{\| class="wikitable"
	~~====~~ SimpleModel ~~====~~		\|+
	Imports a GLTF file as a GameObject. Ideal for weapons, items, simple objects. You can define a built in material to use, and it will automatically apply said material + hook up included textures.		!Name
			!Description
	~~====~~ Texture ~~====~~		!ID
	Imports a .png or .jpeg as a Texture2D		!Properties
			\|-
	~~==== <u>~~AudioClip~~</u> ====~~		\|SimpleModel
	Imports a .mp3, .wav, or .ogg as an ArdenAudioClip		\|Imports a GLTF file as a GameObject. Ideal for weapons, items, simple objects.
			You can define a built in material to use, and it will automatically apply said material + hook up included textures.
			\|simple_model
			\|path: the path to the gltf file
			\|-
			\|Texture
			\|Imports a .png or .jpeg as a Texture2D
			\|texture
			\|path: the path to the image file
			\|-
			\|AudioClip
			\|Imports a .mp3, .wav, or .ogg as an ArdenAudioClip
			\|audio_clip
			\|path: the path to the audio file
			\|-
			\|AssetBundle
			\|Imports a unity asset bundle.
			\|asset_bundle
			\|path: the path to the asset bundle file
			\|}

	=== Custom Importers ===		=== Custom Importers ===

Joshcamas at 01:12, 22 May 2026

2026-05-22T01:12:26Z

← Older revision		Revision as of 21:12, 21 May 2026
Line 6:		Line 6:
	Every mod can have an asset manifest file defined. This lists out all assets you want to import.		Every mod can have an asset manifest file defined. This lists out all assets you want to import.

	~~TODO~~		Create a file called manifest.txt in your mod directory.

			''Example Asset Manifest''<syntaxhighlight lang="json">
			{
			"assets": [
			{
			"assetId": "testmod.dog",
			"type": "texture",
			"properties": [
			{
			"name": "path",
			"value": "Assets/dog.png"
			}
			]
			}
			]
			}
			</syntaxhighlight>

	=== Supported Importers ===		=== Supported Importers ===
	~~<u>SimpleModel:</u> Imports a GLTF file as a gameobject. You can define a built in material to use, and it will automatically apply said material + hook up included textures.~~

	~~<u>Texture:</u>~~ Imports a .~~png or~~ .~~jpeg as~~ a ~~Texture2D~~		==== SimpleModel ====
			Imports a GLTF file as a GameObject. Ideal for weapons, items, simple objects. You can define a built in material to use, and it will automatically apply said material + hook up included textures.

	<u>AudioClip:</u> Imports a .mp3, .wav, or .ogg as an ArdenAudioClip		==== Texture ====
			Imports a .png or .jpeg as a Texture2D

			==== <u>AudioClip</u> ====
			Imports a .mp3, .wav, or .ogg as an ArdenAudioClip

	=== Custom Importers ===		=== Custom Importers ===
	Mods can define their own importers. Perhaps you built a tool that can easily create item data assets from a json file. You can register your own importer to read this file, and then you can easily import them as assets! Other mods can also rely on other's importers.		Mods can define their own importers. Perhaps you built a tool that can easily create item data assets from a json file. You can register your own importer to read this file, and then you can easily import them as assets! Other mods can also rely on other's importers.

			Note an Importer doesn't need to only import a single path (this is why 'path' is a property). Perhaps a single importer takes in a model_path and a data_path, for example.

	TODO		TODO

Joshcamas: Created page with "At some point you may want to import a new model, texture, sound, etc. This can be done one of two ways - manually via scripting, or by using the built in mod asset importer feature. I suggest the latter, unless you want to do something funky. === Asset Manifest === Every mod can have an asset manifest file defined. This lists out all assets you want to import. TODO === Supported Importers === SimpleModel: Imports a GLTF file as a gameobject. You can define a..."

2026-05-20T20:27:40Z

Created page with "At some point you may want to import a new model, texture, sound, etc. This can be done one of two ways - manually via scripting, or by using the built in mod asset importer feature. I suggest the latter, unless you want to do something funky. === Asset Manifest === Every mod can have an asset manifest file defined. This lists out all assets you want to import. TODO === Supported Importers === SimpleModel: Imports a GLTF file as a gameobject. You can define a..."

New page

At some point you may want to import a new model, texture, sound, etc.

This can be done one of two ways - manually via scripting, or by using the built in mod asset importer feature. I suggest the latter, unless you want to do something funky.

=== Asset Manifest ===
Every mod can have an asset manifest file defined. This lists out all assets you want to import.

TODO

=== Supported Importers ===
SimpleModel: Imports a GLTF file as a gameobject. You can define a built in material to use, and it will automatically apply said material + hook up included textures.

Texture: Imports a .png or .jpeg as a Texture2D

AudioClip: Imports a .mp3, .wav, or .ogg as an ArdenAudioClip

=== Custom Importers ===
Mods can define their own importers. Perhaps you built a tool that can easily create item data assets from a json file. You can register your own importer to read this file, and then you can easily import them as assets! Other mods can also rely on other's importers.

TODO

=== Example: A Custom Weapon ===
TODO