OniGalore - Recent changes [en]

Restless Souls/Glossary/Artifacts

Paradox-01 — Fri, 24 Apr 2026 13:15:27 GMT

Staatsräson

@@ Line 821: / Line 821: @@
 ==Imperialismus==
 ==Staatsräson==
 ==Demokratie==
 ===Selbstverteidigungsdefizite von Demokratien===

Talk:Restless Souls/Technology

Paradox-01 — Thu, 23 Apr 2026 11:50:33 GMT

Estimation of risks

← Older revision		Revision as of 11:50, 23 April 2026
Line 715:		Line 715:
	First of all, technology is dual use. Humans decide how to use a tool. The greatest threat to humans are humans.		First of all, technology is dual use. Humans decide how to use a tool. The greatest threat to humans are humans.

	There is a number of "unfixable" problems with AI. But we can manage them if the '''national state has the mightiest AI(s)''' and provides '''selected services''' for the citizens. The assortment must be so '''ridiculous powerful and attractive''' that criminal individuals have neither much interest nor good success rates in creating own AIs and in prevailing against the '''"overpowered" state AIs.'''		There is a number of "unfixable" problems with AI. But we can manage them if the '''national state has the mightiest AI(s)''' and provides '''selected services''' for the citizens. The assortment must be so '''ridiculous powerful and attractive''' that criminal individuals have neither much interest nor good success rates in creating own AIs and in prevailing against the '''"[https://www.heise.de/news/271-Firefox-Luecken-dank-Mythos-KI-geschlossen-Durchbruch-fuer-IT-Sicherheit-11267401.html overpowered]" state AIs.'''

	Let's hope we won't need a full-fledged TCTF. Or how Lobo [https://www.spiegel.de/netzwelt/web/kuenstliche-intelligenz-die-top-3-der-derzeit-sinnvollsten-aengste-kolumne-a-801b5421-1d75-42eb-9ed5-acc2fd9da297 said]: "The bad consequences of a technology come by themselves. For the good effects you have to work long and intensively."		Let's hope we won't need a full-fledged TCTF. Or how Lobo [https://www.spiegel.de/netzwelt/web/kuenstliche-intelligenz-die-top-3-der-derzeit-sinnvollsten-aengste-kolumne-a-801b5421-1d75-42eb-9ed5-acc2fd9da297 said]: "The bad consequences of a technology come by themselves. For the good effects you have to work long and intensively."

Talk:Modifying an existing level

Paradox-01 — Wed, 22 Apr 2026 23:11:56 GMT

Show changes

Media creation with artificial intelligence

Iritscen — Wed, 22 Apr 2026 18:58:06 GMT

fixed WP link with 301 response; I guess the lack of capital letter was the problem

← Older revision		Revision as of 18:58, 22 April 2026
Line 149:		Line 149:
	In context of its limitations, chatbot-based workflows are most often nonetheless a big '''improvement over pure manual workflows''': They '''speed up prototyping''' and let you explore different creative directions for drafts.		In context of its limitations, chatbot-based workflows are most often nonetheless a big '''improvement over pure manual workflows''': They '''speed up prototyping''' and let you explore different creative directions for drafts.

	When you want to work with chatbots, you effectively have to learn '''[[wp:~~prompt_engineering~~\|prompt engineering]]''': You basically learn how to write ''good prompts''.		When you want to work with chatbots, you effectively have to learn '''[[wp:Prompt engineering\|prompt engineering]]''': You basically learn how to write ''good prompts''.

	=====General notes on image upgrading=====		=====General notes on image upgrading=====

Restless Souls/Technology

Iritscen — Wed, 22 Apr 2026 18:38:28 GMT

at least we made it a year and a half without this section name changing…

← Older revision		Revision as of 18:38, 22 April 2026
Line 463:		Line 463:
	Pensatore: "Usually revolutions turn out to be quite bloody. Many people will die in the chaos. From a scientist, I would expect a more ethical suggestion."		Pensatore: "Usually revolutions turn out to be quite bloody. Many people will die in the chaos. From a scientist, I would expect a more ethical suggestion."

	: "Ethics for its own sake is not an option. Look at history. On the verge of death, men [[wp:Uruguayan Air Force ~~Flight_571~~#Resorting to cannibalism\|ate other men]]<!--[[wp:Cannibalism_in_Europe#World_War_II]]-->, even corpses, for one simple reason: to survive. And even devout Christians have come to the conclusion that death to a megalomaniac dictator can be justified. -- Ethics are only as good as the situation allows them to be! Of how much worth are rules and laws which don't let you survive?"		: "Ethics for its own sake is not an option. Look at history. On the verge of death, men [[wp:Uruguayan Air Force Flight 571#Resorting to survival cannibalism\|ate other men]]<!--[[wp:Cannibalism_in_Europe#World_War_II]]-->, even corpses, for one simple reason: to survive. And even devout Christians have come to the conclusion that death to a megalomaniac dictator can be justified. -- Ethics are only as good as the situation allows them to be! Of how much worth are rules and laws which don't let you survive?"

	"And you believe we are in such a situation? Certainly, the WCG isn't the optimal solution, but this is a bit too much in my opinion. -- What do you have in mind? Do you want as a geneticist to make a biological intervention that takes away all of the control humans have wrested from mother nature in the last [[wp:Control_of_fire_by_early_humans\|125,000 years]]?"		"And you believe we are in such a situation? Certainly, the WCG isn't the optimal solution, but this is a bit too much in my opinion. -- What do you have in mind? Do you want as a geneticist to make a biological intervention that takes away all of the control humans have wrested from mother nature in the last [[wp:Control_of_fire_by_early_humans\|125,000 years]]?"

Talk:Modifying an existing level

Paradox-01 — Wed, 22 Apr 2026 14:25:48 GMT

← Older revision		Revision as of 14:25, 22 April 2026
(2 intermediate revisions by the same user not shown)
Line 226:		Line 226:

	=====Agent.md example=====		=====Agent.md example=====
	* ~~Add notes about resources there~~. ~~Like a downloaded Onisplit wiki page and what to expect from it~~. ~~Commands and args. Be consistent using known terms, like "export" and "extract", in their proper use cases~~.		For autodetection you can use the expected '''default directories''' and respect the '''naming convention''' for agent files: *.agent.md
	* Add general working instructions like for reading and writing test data.
			Standard directories for agents.

			For global selection
			%USERPROFILE%/.github/agents/

	~~Example of an Agent.md; for "..." use your own start path~~.		For local selection
			''solutionName''/.github/agents/

	~~The display name is not determined by the filename but by the internal name. Either add manually or tell the IDE chatbot~~ to ~~add~~ your agent ~~directory to~~ the ~~'''project file'''~~. ~~After~~ that agents ~~can be picked. For roundtripping and autoimproving new C# via old C# agent 1 is picked. For roundtripping and autoimproving VB via new C# agent 2 is picked~~.		Bug: empty agent selection list
			* There seems to be a section bug: When you decide to remove all agents from your workspace folder also the global agent won't show up in the list. In that case delete the now empty workspace agents folder.

			Examples for content
			* Add general working instructions like for reading and writing test data.
			* Add notes about resources there. Like a downloaded Onisplit wiki page and what to expect from it. Commands and args. Be consistent using known terms, like "export" and "extract", in their proper use cases.
			* The display name is not determined by the filename but by the internal name.<!-- Either add manually or tell the IDE chatbot to add your agent directory to the '''project file'''. After that agents can be picked.--> For roundtripping and autoimproving new C# via old C# agent 1 is picked. For roundtripping and autoimproving VB via new C# agent 2 is picked.<!--
			//optional
	This way, agents also can have a global directory.		This way, agents also can have a global directory.
	<pre>		<pre>
	<ItemGroup>		<ItemGroup>
	<None Include="$(UserProfile)\.github\agents\*.md" />		<None Include="$(UserProfile)\.github\agents\*.agent.md" />
	</ItemGroup>		</ItemGroup>
	</pre>		</pre>
			-->
			* The bigger idea is to write '''universal information into agent md''' so the actual '''prompts can be shortened'''. For "..." use your own start path.

	~~The bigger idea is to write '''universal information into~~ agent ~~md''' so the actual '''prompts can be shortened'''~~.		Example of agent #2 Oni-Ni-Kanabo-csNet10-vs-vb.agent.md

	~~Agent~~ md
	<pre>		<pre>
	---		---

OBD:Instance file format

Iritscen — Tue, 21 Apr 2026 22:15:25 GMT

using the engine term "placeholder" instead of "empty" because it's clearer

Talk:Modifying an existing level

Paradox-01 — Tue, 21 Apr 2026 22:06:03 GMT

@@ Line 17: / Line 17: @@
 ==AE package==
   mods.oni2.net
+   |
-   +-- 08030LevelRecycler#.zip (# = Upload version)
+   +-- 08040LevelRecycler#.zip (# = Upload version)
+        |
-        +-- 08030LevelRecycler_Win
+        +-- 08040LevelRecycler_Win
+             |
              +-- Mod_Info.cfg
@@ Line 334: / Line 335: @@
 I consider the work on Onisplit as training. But now knowing that ''the community'' has another tool in the making, there is less motivation to work on Onisplit updates in a faster pace as the bigger goal is the recycler. After all, the entire pipeline depends on the main conversion tool.
   game data -> converter -> level recycler -> Blender / Blender addon -> converter -> updated game data

Creating a level

Paradox-01 — Tue, 21 Apr 2026 09:45:53 GMT

extended version of build.cmd, releasing the FURN updater app later

← Older revision		Revision as of 09:45, 21 April 2026
(2 intermediate revisions by the same user not shown)
Line 153:		Line 153:

	==Setting up a workflow==		==Setting up a workflow==
	If not noted ~~differentely~~ you need OniSplit v0.9.82.0 or a newer version. Onisplit comes with the [[AE]] and is found in the Tools directory of the installation; ~~but~~ it can also be downloaded from [http://mods.oni2.net/node/38 mod depot].		'''Onisplit'''
			* If not noted differently you need OniSplit v0.9.82.0 or a newer version.
			* Onisplit comes with the [[AE]] and is found in the Tools directory of the installation; it can also be downloaded from [http://mods.oni2.net/node/38 mod depot].

	The level import demo files can be downloaded [http://mods.oni2.net/node/299 HERE].		'''Level project'''
			* The level import demo files can be downloaded [http://mods.oni2.net/node/299 HERE].
			* When you unpacked the folders <code>shared</code> and <code>lab</code> into the <code>GameDataFolder</code> your setup should look like in the overview beneath.
			* With the <code>shared</code> folder in the GDF you can easily create more level projects. Be sure to update the <code>build.cmd</code> for these projects.

	When you unpacked the folders shared and lab into the GameDataFolder your setup should look like this. With the shared folder in the GDF you can easily create more level projects. Be sure to update the build.cmd for these projects.		'''Overview (with only most important items)'''
	{{Tree list}}		{{Tree list}}
	* Oni		* Oni
Line 164:		Line 169:
	**** OniSplit.exe		**** OniSplit.exe
	*** GameDataFolder		*** GameDataFolder
	**** level3_Final.dat (created from lab.xml via build.cmd)
	**** level3_Final.raw (created from lab.xml via build.cmd)
	**** shared (global resource folder)		**** shared (global resource folder)
	**** lab (local project folder)		**** lab (local project folder)
	***** lab.xml		***** lab.xml
	***** build.cmd		***** build.cmd
	***** out
	***** post-create-patches (for overwriting the static image lab\env\images\GOO.tga)		***** post-create-patches (for overwriting the static image lab\env\images\GOO.tga)
	****** TXMPGOO.oni
	****** TXMPGOO.xml (provided as example for combined oni creation and patching via build.cmd)		****** TXMPGOO.xml (provided as example for combined oni creation and patching via build.cmd)
	****** TXMPGOO_*.tga		****** TXMPGOO_*.tga
			****** TXMPGOO.oni
			***** out
			**** level3_Final.dat (created from lab.xml via build.cmd)
			**** level3_Final.raw (created from lab.xml via build.cmd)
	{{Tree list\|end}}		{{Tree list\|end}}

	Content of build.cmd		'''Content of build.cmd'''
	..\..\..\AE\Tools\OniSplit -create:level out lab.xml		<pre>
	..\..\..\AE\Tools\OniSplit -create:txmp out env\markers\*.tga		..\..\..\AE\Tools\OniSplit -create:level out lab.xml
	REM use quote signs for folder names that contain spaces		..\..\..\AE\Tools\OniSplit -create:txmp out env\markers\*.tga
	..\..\..\AE\Tools\OniSplit -create post-create-patches post-create-patches\*.xml		REM use quote signs for folder names that contain spaces
	copy /Y post-create-patches\*.oni out		..\..\..\AE\Tools\OniSplit -create post-create-patches post-create-patches\*.xml
	..\..\..\AE\Tools\OniSplit -import:pc out ..\level3_Final.dat		copy /Y post-create-patches\*.oni out
	REM read error messages, ~~close console~~ with any key press		..\..\..\AE\Tools\OniSplit -import:pc out ..\level3_Final.dat
	~~pause~~		pause
	pushd ..\..\..\AE		REM read here notifications, warnings and error messages, continue with any key press
	Oni.exe -noswitch		pushd ..\..\..\AE
			Oni.exe -noswitch
			</pre>

	Known issues of lab demo		'''Extended build.cmd'''
			<pre>
			@echo off
			pushd "%~dp0"
			set "LEVEL_CLEANUP=..\..\Tools\LevelCleanUp\LevelCleanUp.exe"
			if exist "%LEVEL_CLEANUP%" (
			"%LEVEL_CLEANUP%" "."
			) else (
			echo Skipping furniture cleanup: "%LEVEL_CLEANUP%" was not found.
			echo The tool can be installed via AEInstaller.
			)
			..\..\..\AE\Tools\OniSplit.exe -create:level out lab.xml
			..\..\..\AE\Tools\OniSplit.exe -create:txmp out env\markers\*.tga
			REM use quote signs for folder names that contain spaces
			..\..\..\AE\Tools\OniSplit.exe -create post-create-patches post-create-patches\*.xml
			copy /Y post-create-patches\*.oni out
			..\..\..\AE\Tools\OniSplit.exe -import:pc out ..\level3_Final.dat
			REM read error messages, close console with any key press
			pause
			pushd ..\..\..\AE
			Oni.exe -noswitch
			</pre>

			'''Known issues of lab demo'''
	* Motocycle anim (OBAN) is to low		* Motocycle anim (OBAN) is to low
	* second scene block shows no motorcycle		* second scene block shows no motorcycle
	* uses an automated fix for updating TXMPgoo		* uses an automated fix for updating TXMPgoo

	Notes on packaging		'''Notes on packaging'''
	* Hit "build.cmd" to create .oni files. They will be stored in the "out" folder and can be used to make a new [[Making a mod package\|AE package]].		* Hit "build.cmd" to create .oni files. They will be stored in the "out" folder and can be used to make a new [[Making a mod package\|AE package]].
	* Normally, "TXMP_marker_door" and "TXMP_marker_ghost" will be missing in the "out" folder so we added a line to handle that as well.		* Normally, "TXMP_marker_door" and "TXMP_marker_ghost" will be missing in the "out" folder so we added a line to handle that as well.
Line 1,129:		Line 1,159:

	====Furniture.xml====		====Furniture.xml====
	The AKEV core geometry ~~is more or less~~ the ~~overall~~ structure ~~of the level while this~~ furniture file ~~adds~~ standard objects (e.g. crates and desks) to it.		The AKEV core geometry represents the general level structure, including unique elements. This furniture file will add standard objects (e.g. crates and desks) to it.

			Recycled furniture files might contain artifacts.
			* You can either write an own script to delete all code blocks that don't have an OFGA in the shared folder or you install the LevelCleanUp tool via AEI.

	{\| class="wikitable" width="100%"		{\| class="wikitable" width="100%"

Validate External Links/Exceptions

Iritscen — Sun, 19 Apr 2026 22:59:21 GMT

← Older revision		Revision as of 22:59, 19 April 2026
Line 53:		Line 53:
	403,https://www.cracked.com/article_20078_5-weird-directions-human-evolution-could-have-taken.html,Oni2:Slaves_of_War/Neo-Biology		403,https://www.cracked.com/article_20078_5-weird-directions-human-evolution-could-have-taken.html,Oni2:Slaves_of_War/Neo-Biology
	403,https://www.treehugger.com/rare-interspecies-play-observed-between-dolphins-and-whales-4857038,Oni2:Slaves_of_War/Neo-Biology		403,https://www.treehugger.com/rare-interspecies-play-observed-between-dolphins-and-whales-4857038,Oni2:Slaves_of_War/Neo-Biology
			403,https://ocean.si.edu/ocean-life/invertebrates/zombie-worms-crave-bone,Oni2:Slaves_of_War/Neo-Biology
	403,https://www.viator.com/tours/Rio-de-Janeiro/Niteroi-City-Tour-and-Contemporary-Art-Museum-Admission/d712-8753P7,Oni2:Slaves_of_War/Settings		403,https://www.viator.com/tours/Rio-de-Janeiro/Niteroi-City-Tour-and-Contemporary-Art-Museum-Admission/d712-8753P7,Oni2:Slaves_of_War/Settings
	403,https://www.cracked.com/article_17562_5-horrifying-apocalyptic-scenarios-that-have-already-happened.html,Oni2:Slaves_of_War/Settings		403,https://www.cracked.com/article_17562_5-horrifying-apocalyptic-scenarios-that-have-already-happened.html,Oni2:Slaves_of_War/Settings
Line 78:		Line 79:
	403,https://www.politico.com/news/2025/06/02/pentagon-greenland-northern-command-00381223,Restless_Souls/Glossary/Artifacts		403,https://www.politico.com/news/2025/06/02/pentagon-greenland-northern-command-00381223,Restless_Souls/Glossary/Artifacts
	303,https://link.springer.com/article/10.1007/s41748-026-01073-y,Restless_Souls/Glossary/Artifacts		303,https://link.springer.com/article/10.1007/s41748-026-01073-y,Restless_Souls/Glossary/Artifacts
			403,https://www.oeaw.ac.at/news/wie-die-wasserkrise-teheran-unter-druck-setzt,Restless_Souls/Glossary/Artifacts
	302,https://www.golem.de/news/abschreckungspolitik-taiwan-will-tsmc-fabriken-nicht-von-usa-bombardieren-lassen-2305-174057.html,Restless_Souls/Glossary/de		302,https://www.golem.de/news/abschreckungspolitik-taiwan-will-tsmc-fabriken-nicht-von-usa-bombardieren-lassen-2305-174057.html,Restless_Souls/Glossary/de
	000-92,https://www.washingtonpost.com/archive/politics/1997/04/24/russia-china-sign-new-friendship-pact/896539b8-c583-44f2-8a73-095cbad1e784/,Restless_Souls/Glossary/de		000-92,https://www.washingtonpost.com/archive/politics/1997/04/24/russia-china-sign-new-friendship-pact/896539b8-c583-44f2-8a73-095cbad1e784/,Restless_Souls/Glossary/de

Oni (no relation)

Iritscen — Sun, 19 Apr 2026 22:58:52 GMT

link fix

← Older revision		Revision as of 22:58, 19 April 2026
Line 93:		Line 93:
	[https://www.orderofgamers.com/games/at-43/ AT-43] was a sci-fi role-playing board game released in 2006 which told the story of several warring factions. One faction is called [https://www.orderofgamers.com/downloads/AT43ONI.pdf ONI], standing for Okamura Non-aligned Industries. They're a mercenary corporation that uses the O serum to create zombie soldiers and builds weapons based off any technology they can get their hands on, then sells them to the highest bidder in the war between the other factions of the game.		[https://www.orderofgamers.com/games/at-43/ AT-43] was a sci-fi role-playing board game released in 2006 which told the story of several warring factions. One faction is called [https://www.orderofgamers.com/downloads/AT43ONI.pdf ONI], standing for Okamura Non-aligned Industries. They're a mercenary corporation that uses the O serum to create zombie soldiers and builds weapons based off any technology they can get their hands on, then sells them to the highest bidder in the war between the other factions of the game.

	Although the original publisher Rackham has been defunct since 2010, the rights to the company's games were [https://www.~~beastsofwar~~.com/board-games/monolith-announce-rackham-companys-ip/ acquired by] Monolith Edition in 2024, another board game publisher, with the intent of putting the games back in production.		Although the original publisher Rackham has been defunct since 2010, the rights to the company's games were [https://www.ontabletop.com/board-games/monolith-announce-rackham-companys-ip/ acquired by] Monolith Edition in 2024, another board game publisher, with the intent of putting the games back in production.

	{{Quote\|Okamura Kazuo finally met his fate after eight months of work in his new service. He undertook an experiment with a highly-advanced viral strain and put it in the presence of a reagent he had invented.		{{Quote\|Okamura Kazuo finally met his fate after eight months of work in his new service. He undertook an experiment with a highly-advanced viral strain and put it in the presence of a reagent he had invented.

Creating a level

Paradox-01 — Sun, 19 Apr 2026 21:50:19 GMT

← Older revision		Revision as of 21:50, 19 April 2026
(7 intermediate revisions by the same user not shown)
Line 157:		Line 157:
	The level import demo files can be downloaded [http://mods.oni2.net/node/299 HERE].		The level import demo files can be downloaded [http://mods.oni2.net/node/299 HERE].

	~~First, put '''~~OniSplit.exe~~''' into the second '''~~lab~~'''~~ folder ~~alongside~~ the ~~XML files~~.		When you unpacked the folders shared and lab into the GameDataFolder your setup should look like this. With the shared folder in the GDF you can easily create more level projects. Be sure to update the build.cmd for these projects.
			{{Tree list}}
			* Oni
			** AE
			*** Tools
			**** OniSplit.exe
			*** GameDataFolder
			**** level3_Final.dat (created from lab.xml via build.cmd)
			**** level3_Final.raw (created from lab.xml via build.cmd)
			**** shared (global resource folder)
			**** lab (local project folder)
			***** lab.xml
			***** build.cmd
			***** out
			***** post-create-patches (for overwriting the static image lab\env\images\GOO.tga)
			****** TXMPGOO.oni
			****** TXMPGOO.xml (provided as example for combined oni creation and patching via build.cmd)
			****** TXMPGOO_*.tga
			{{Tree list\|end}}

	~~Look at the file '''~~build.cmd~~'''~~. ~~These are the two important lines~~:		Content of build.cmd
			..\..\..\AE\Tools\OniSplit -create:level out lab.xml
			..\..\..\AE\Tools\OniSplit -create:txmp out env\markers\*.tga
			REM use quote signs for folder names that contain spaces
			..\..\..\AE\Tools\OniSplit -create post-create-patches post-create-patches\*.xml
			copy /Y post-create-patches\*.oni out
			..\..\..\AE\Tools\OniSplit -import:pc out ..\level3_Final.dat
			REM read error messages, close console with any key press
			pause
			pushd ..\..\..\AE
			Oni.exe -noswitch

	~~OniSplit.exe -create:level out~~ lab~~.xml~~		Known issues of lab demo
	~~OniSplit.exe -import:pc out level3_Final.dat~~		* Motocycle anim (OBAN) is to low
			* second scene block shows no motorcycle
			* uses an automated fix for updating TXMPgoo

	~~The first line creates the~~ *.oni files ~~from a master~~.~~xml file,~~ in ~~this case '''lab.xml'''. Once finalized,~~ the ~~resulting .oni files~~ can be ~~put into~~ a new [[Making a mod package\|AE package]].		Notes on packaging
			* Hit "build.cmd" to create .oni files. They will be stored in the "out" folder and can be used to make a new [[Making a mod package\|AE package]].
	The ~~second line creates~~ level ~~archives which can be used for fast tests~~. ~~They don't require you to install a package through~~ the ~~AE Installer~~.		* Normally, "TXMP_marker_door" and "TXMP_marker_ghost" will be missing in the "out" folder so we added a line to handle that as well.
			* The script continues to build level3_Final files and starts Oni so you can instantly test the level. That is much faster then using the AEInstaller.
	~~Instead of "-nosep" you can now also use "-pc"~~ for ~~the import.~~ Macs, ~~however, do~~ use "-sep".		* To generate test archives for Macs, use the "-import:sep" argument instead of "-import:pc".

	==Troubleshooting==		==Troubleshooting==
Line 180:		Line 210:

	:[http://mods.oni2.net/system/files/AKEV_texture_checker.txt THIS] script checks which textures are missing by comparing the AKEV.xml with its .oni files folder. Change the two paths so that it works for you: Alt+4, insert code, then F5.		:[http://mods.oni2.net/system/files/AKEV_texture_checker.txt THIS] script checks which textures are missing by comparing the AKEV.xml with its .oni files folder. Change the two paths so that it works for you: Alt+4, insert code, then F5.

	~~"TXMP_marker_door" and "TXMP_marker_ghost" will be missing in the demo's "out" folder.~~

	~~You can add this between the other two lines in build.cmd to prevent a crash.~~
	~~OniSplit.exe -create:txmp out env/markers/*.tga~~

	==Terminology==		==Terminology==
Line 236:		Line 261:
	* A '''level map''' consists of visible geometry: terrain and buildings. This is also named the '''environment''' or for short '''env'''.		* A '''level map''' consists of visible geometry: terrain and buildings. This is also named the '''environment''' or for short '''env'''.
	** Use '''quads''' of approximately 10 up to 20 meters in size to construct env geometry.		** Use '''quads''' of approximately 10 up to 20 meters in size to construct env geometry.
	* ~~Anything other than floors~~ and simple walls ~~will be made of~~ triangles.		** Use quads for floor and simple walls, including pathfinding objects.
			* Create objects with triangles (or triangulate quads during export if this option exists for you).
	** Geometry from CJBO works best with triangles. Quads might show holes in-game.		** Geometry from CJBO works best with triangles. Quads might show holes in-game.
	'''Invisible pathfinding'''		'''Invisible pathfinding'''

Talk:Modifying an existing level

Paradox-01 — Sun, 19 Apr 2026 15:43:43 GMT

Roundtripping

← Older revision		Revision as of 15:43, 19 April 2026
Line 215:		Line 215:
	** Therefore, you can define '''hash parity''' of output files as a '''general goal''', with the '''exception''' that differences can be ignored if they are caused only by '''non-semantic ID changes'''. In other words: you may consider semantic equivalence under normalized comparison as sufficient.		** Therefore, you can define '''hash parity''' of output files as a '''general goal''', with the '''exception''' that differences can be ignored if they are caused only by '''non-semantic ID changes'''. In other words: you may consider semantic equivalence under normalized comparison as sufficient.
	** By the way, DAE files - which are internally XML - contain tags for the authoring tool and version. Therefore, these files may also differ at the byte level.		** By the way, DAE files - which are internally XML - contain tags for the authoring tool and version. Therefore, these files may also differ at the byte level.
			<?xml version="1.0" encoding="utf-8"?>
			<COLLADA xmlns="http://www.collada.org/2005/11/COLLADASchema" version="1.4.1">
			<asset>
			<contributor>
			<authoring_tool>Softimage\|XSI Mod Tool version 7.5.203.0</authoring_tool>
			</contributor>
			[...]
	* After all obvious bugs have been fixed with help of roundtripping, unit testing could be done to catch smaller mismatches and bugs. Eventually, ingame testing would be done.		* After all obvious bugs have been fixed with help of roundtripping, unit testing could be done to catch smaller mismatches and bugs. Eventually, ingame testing would be done.

Creating a level

Paradox-01 — Sun, 19 Apr 2026 15:40:36 GMT

Reformulating: Getting Onisplit from AE is first choice.

← Older revision		Revision as of 15:40, 19 April 2026
Line 153:		Line 153:

	==Setting up a workflow==		==Setting up a workflow==
	If not noted differentely you need OniSplit v0.9.82.0 or a newer version. Onisplit can be downloaded [http://mods.oni2.net/node/38 ~~HERE] (it also comes with the [[AE]~~] ~~and is found in the Tools directory of the installation)~~.		If not noted differentely you need OniSplit v0.9.82.0 or a newer version. Onisplit comes with the [[AE]] and is found in the Tools directory of the installation; but it can also be downloaded from [http://mods.oni2.net/node/38 mod depot].

	The level import demo files can be downloaded [http://mods.oni2.net/node/299 HERE].		The level import demo files can be downloaded [http://mods.oni2.net/node/299 HERE].

Talk:Modifying an existing level

Paradox-01 — Sun, 19 Apr 2026 11:10:10 GMT

← Older revision		Revision as of 11:10, 19 April 2026
(5 intermediate revisions by the same user not shown)
Line 197:		Line 197:
	\| Speed \|\| 5.571 ms \|\| 5.406 ms \|\| 5.748 ms		\| Speed \|\| 5.571 ms \|\| 5.406 ms \|\| 5.748 ms
	\|-		\|-
	\| Peak RAM usage \|\| 1.~~155,~~81 MB \|\| 150,51 MB \|\| 63,64 MB		\| Peak RAM usage \|\| 1155.81 MB \|\| 150.51 MB \|\| 63.64 MB<!--closer to US formatting-->
	\|}		\|}

Line 208:		Line 208:
	* A complete dev env should contain files to test every possible conversion including options.		* A complete dev env should contain files to test every possible conversion including options.
	* Keep test data out of original AE directory. When debugging multiple codebases, you don't want them to crash into one another.		* Keep test data out of original AE directory. When debugging multiple codebases, you don't want them to crash into one another.
	* To set up advanced agents - that might even include (interesting but tricky) self-improvement - look at the web for [~~examples~~ https://david.coffee/vibe-coding-part-1/].		* To set up advanced agents - that might even include (interesting but tricky) self-improvement - look at the web for [https://david.coffee/vibe-coding-part-1/ examples].

	=====Roundtripping=====		=====Roundtripping=====
	* On a general note: Roundtripping data is a very effective method to detect observable differences and ~~actual~~ bugs.		* On a general note: Roundtripping data is a very effective method to detect observable differences and bugs that were introduced by the initial codebase conversion.
	* More specifically: Descriptor IDs, such as in <code><TRAC id="6787"></code>, are ~~not preserved because~~ ONI files use ''local'' ~~IDs and are later repacked during DAT creation~~. ~~Therefore~~, ~~IDs in~~ XML~~/ONI~~ are ~~typically reset to 0~~.		* More specifically: '''Descriptor IDs''', such as in <code><TRAC id="6787"></code>, are '''typically reset to 0 and then incremented by 1''' for each instance. '''ONI files''' are '''modular containers for''' different '''subfile types''', or as we say, '''instances'''. Therefore, ONI files use '''[[XML:TxtC#Example\|local IDs]]'''. Eventually, all [[XML:DOOR#File_structure\|instances]] become repacked later when the larger level archives (DAT) are rebuilt.
	** Therefore, you can define hash parity of output files as a general goal, with the exception that differences can be ignored if they are caused only by non-semantic ID changes. In other words: you may consider semantic equivalence under normalized comparison as sufficient.		** Therefore, you can define '''hash parity''' of output files as a '''general goal''', with the '''exception''' that differences can be ignored if they are caused only by '''non-semantic ID changes'''. In other words: you may consider semantic equivalence under normalized comparison as sufficient.
	** By the way, DAE files - which are internally XML - contain ~~a tag~~ for the authoring tool and version. Therefore, these files may also differ at the byte level.		** By the way, DAE files - which are internally XML - contain tags for the authoring tool and version. Therefore, these files may also differ at the byte level.
			* After all obvious bugs have been fixed with help of roundtripping, unit testing could be done to catch smaller mismatches and bugs. Eventually, ingame testing would be done.

	=====Agent.md example=====		=====Agent.md example=====
Line 324:		Line 325:

	==(Another tool placeholder)==		==(Another tool placeholder)==
			I consider the work on Onisplit as training. But now knowing that ''the community'' has another tool in the making, there is less motivation to work on Onisplit updates in a faster pace as the bigger goal is the recycler. After all, the entire pipeline depends on the main conversion tool.
			game data -> converter -> level recycler -> Blender / Blender addon -> converter -> updated game data

OniX

Iritscen — Sun, 19 Apr 2026 01:55:09 GMT

actually forgot why I chose 192; it didn't come out of a hat

← Older revision		Revision as of 01:55, 19 April 2026
Line 24:		Line 24:
	\|}		\|}

	'''OniX''' is a fan-made rebuild of the [[Oni]] game application, yielding new possibilities for Oni in terms of modding, new engine features, and maintenance for modern operating systems. The initial v1.0 release is intended to replicate "vanilla" Oni as closely as possible while fixing compatibility issues with current operating systems and modern hardware (including HDPI<ref>High DPI, typically defined as a minimum of 220-240 dpi.<br>For an HDPI display, a backing scale above 1x is commonly used (where "1x" means a 1:1 ratio of physical pixel to logical point); this means that controls, text, and everything else on-screen is drawn with more pixels in order to prevent the screen contents from becoming too tiny.<br>The Retina displays on Macs with built-in screens use a 2x (4:1 pixels-per-point) scaling factor. A display in Microsoft Windows which is set to use scaling above 100% raises the effective DPI by using a fractional backing scale, e.g. 125% = 1.25x.<br>In Windows, OniX queries the monitor's effective DPI at its current scaling, and treats any effective DPI ≥ 192 as a 2x backing scale. Setting OniX to a resolution of "1280x960" on such a display will create a 640x480-point window which is drawn with a 2x scaling factor, containing 1280x960 pixels of content.</ref> and HRR<ref>High Refresh Rate, that is, anything above 60 Hz. OniX corrects timing issues and input issues which Oni.exe experienced at high refresh rates.</ref> displays) and upgrading to a new game data versioning system that will make future improvements easier to roll out. A legacy build is offered which will run in anything from Windows 98 to Windows 8. It does this by not supporting certain features of modern Windows which don't impact older computers anyway, e.g. HDPI support.		'''OniX''' is a fan-made rebuild of the [[Oni]] game application, yielding new possibilities for Oni in terms of modding, new engine features, and maintenance for modern operating systems. The initial v1.0 release is intended to replicate "vanilla" Oni as closely as possible while fixing compatibility issues with current operating systems and modern hardware (including HDPI<ref>High DPI, typically defined as a minimum of 220-240 dpi.<br>For an HDPI display, a backing scale above 1x is commonly used (where "1x" means a 1:1 ratio of physical pixel to logical point); this means that controls, text, and everything else on-screen is drawn with more pixels in order to prevent the screen contents from becoming too tiny.<br>The Retina displays on Macs with built-in screens use a 2x (4:1 pixels-per-point) scaling factor. A display in Microsoft Windows which is set to use scaling above 100% raises the effective DPI by using a fractional backing scale, e.g. 125% = 1.25x.<br>In Windows, OniX queries the monitor's effective DPI at its current scaling, and treats any effective DPI ≥ 192 as a 2x backing scale (because 96 dpi is the default in Windows). Setting OniX to a resolution of "1280x960" on such a display will create a 640x480-point window which is drawn with a 2x scaling factor, containing 1280x960 pixels of content.</ref> and HRR<ref>High Refresh Rate, that is, anything above 60 Hz. OniX corrects timing issues and input issues which Oni.exe experienced at high refresh rates.</ref> displays) and upgrading to a new game data versioning system that will make future improvements easier to roll out. A legacy build is offered which will run in anything from Windows 98 to Windows 8. It does this by not supporting certain features of modern Windows which don't impact older computers anyway, e.g. HDPI support.

	==Limitations==		==Limitations==

Talk:Modifying an existing level

Paradox-01 — Sat, 18 Apr 2026 21:12:29 GMT

← Older revision		Revision as of 21:12, 18 April 2026
(4 intermediate revisions by the same user not shown)
Line 144:		Line 144:

	====Scaling====		====Scaling====
	~~Round-tripping~~ the old helix through Blender caused an upscaling.		Roundtripping the old helix through Blender caused an upscaling.

	Old code:		Old code:
Line 208:		Line 208:
	* A complete dev env should contain files to test every possible conversion including options.		* A complete dev env should contain files to test every possible conversion including options.
	* Keep test data out of original AE directory. When debugging multiple codebases, you don't want them to crash into one another.		* Keep test data out of original AE directory. When debugging multiple codebases, you don't want them to crash into one another.
			* To set up advanced agents - that might even include (interesting but tricky) self-improvement - look at the web for [examples https://david.coffee/vibe-coding-part-1/].

	=====Roundtripping=====		=====Roundtripping=====
	~~Descriptors~~ IDs ~~like~~ in <code><TRAC id="6787"></code> are not preserved (because ~~irrelevant)~~ and ~~will be resetted~~ to 0.		* On a general note: Roundtripping data is a very effective method to detect observable differences and actual bugs.
			* More specifically: Descriptor IDs, such as in <code><TRAC id="6787"></code>, are not preserved because ONI files use ''local'' IDs and are later repacked during DAT creation. Therefore, IDs in XML/ONI are typically reset to 0.
			** Therefore, you can define hash parity of output files as a general goal, with the exception that differences can be ignored if they are caused only by non-semantic ID changes. In other words: you may consider semantic equivalence under normalized comparison as sufficient.
			** By the way, DAE files - which are internally XML - contain a tag for the authoring tool and version. Therefore, these files may also differ at the byte level.

	=====Agent.md example=====		=====Agent.md example=====
Line 218:		Line 222:
	Example of an Agent.md; for "..." use your own start path.		Example of an Agent.md; for "..." use your own start path.

	The display name is not determined by the filename but by the internal name. Either add manually or tell the IDE chatbot to add your agent directory to the '''project file'''. After that agents can be picked. For roundtripping-and-autoimproving new C# via old C# agent 1 is picked. For roundtripping-and-autoimproving VB via new C# agent 2 is picked.		The display name is not determined by the filename but by the internal name. Either add manually or tell the IDE chatbot to add your agent directory to the '''project file'''. After that agents can be picked. For roundtripping and autoimproving new C# via old C# agent 1 is picked. For roundtripping and autoimproving VB via new C# agent 2 is picked.

	This way, agents also can have a global directory.		This way, agents also can have a global directory.
Line 227:		Line 231:
	</pre>		</pre>

	The bigger idea is to write '''universal information into agent md''' so the actual '''~~session instructions~~ can be shortened'''.		The bigger idea is to write '''universal information into agent md''' so the actual '''prompts can be shortened'''.

	Agent md		Agent md
Line 245:		Line 249:

	Read test data from ...\Oni\AE\GameDataFolder if needed, but write outputs to github-ignoreable subfolders of the individual's local OniSplit codebase to avoid conflicts with the source code and to keep test outputs organized and separate from source files.		Read test data from ...\Oni\AE\GameDataFolder if needed, but write outputs to github-ignoreable subfolders of the individual's local OniSplit codebase to avoid conflicts with the source code and to keep test outputs organized and separate from source files.
	Use .test-output for outputs and comparisons to reach hash-based conclusions about parity between c# and vb builds.		Use .test-output for outputs and comparisons to reach hash-based conclusions about parity between C# and VB builds.

	If you compare over 100 files at once, do it sequentially in steps of 100 so the consoles do not overflow or hang. If using powershell or other terminals, don't lose connection and report ~~everytime~~ a batch finished, so you can continue with your remaining work after all batches finished.		If you compare over 100 files at once, do it sequentially in steps of 100 so the consoles do not overflow or hang. If using powershell or other terminals, don't lose connection and report every time a batch finished, so you can continue with your remaining work after all batches finished.

	If roundtripping is requested, get specified files (or naming pattern) from active user prompt, export oni files from dat if necessary, then extract oni files to xml and create oni again. Analyze diff in xml and hash-diffs of old and new oni files. Patch vb codebase to make roundtripping work and reach oni-hash-parity: Ignore-exception: Descriptors IDs like in TRAC id="6787" are not preserved because irrelevant and will be ~~resetted~~ to 0. Log example of probably unimportant mismatches though. And show values of one mismatch example in console output: What do they represent.		If roundtripping is requested, get specified files (or naming pattern) from active user prompt, export oni files from dat if necessary, then extract oni files to xml and create oni again. Analyze diff in xml and hash-diffs of old and new oni files. Patch VB codebase to make roundtripping work and reach oni-hash-parity: Ignore-exception: Descriptors IDs like in TRAC id="6787" are not preserved because irrelevant and will be reset to 0. Log example of probably unimportant mismatches though. And show values of one mismatch example in console output: What do they represent.

	When conversions with this vb-based application fail, test same command with the c#-based Onisplit.exe to check if the issue is vb-specific or shared.		When conversions with this VB-based application fail, test same command with the C#-based Onisplit.exe to check if the issue is VB-specific or shared.
	If shared, then it's not a parity issue and should be fixed in both builds together. Skip (but document) shared issues for now and focus on vb-only issues.		If shared, then it's not a parity issue and should be fixed in both builds together. Skip (but document) shared issues for now and focus on VB-only issues.
	If vb-specific, then it's a parity issue and should be fixed in the vb codebase to match the c# behavior.		If vb-specific, then it's a parity issue and should be fixed in the VB codebase to match the c# behavior.
	</pre>		</pre>

	=====Prompt example=====		=====Prompt example=====
	test roundtripping of TxtC*.oni files		test roundtripping of TxtC*.oni files

			Prompt engineering for agentic coding is also known as vibecoding.
			* You basically write pseudocode, which the agent then translates into real code and additional means to make everything work. The pseudocode should strike the right balance between formulating your app’s features and how these should be implemented, without going into every detail.
			* Besides considering your information and the rules defined in the md files, the agent will also make its own assumptions. These might be incorrect at some point or go ''off track''. Therefore, one prompt usually never achieves what you want. Further details - including broad or more specific bug-fix instructions - will need to be written by you at a later time anyway.
			* For more complex apps, think of a structure (components/modules, data flow, responsibilities) that the agent should build.

	====Notes on C# (.NET Framework 4) (Onisplit 0.9.99.0)====		====Notes on C# (.NET Framework 4) (Onisplit 0.9.99.0)====

← Older revision		Revision as of 22:15, 21 April 2026
Line 166:		Line 166:
	;Flags - data usage		;Flags - data usage
	:0x'''01''' 00 00 00 - unnamed		:0x'''01''' 00 00 00 - unnamed
	:0x'''02''' 00 00 00 - ~~empty~~		:0x'''02''' 00 00 00 - placeholder
	:0x'''04''' 00 00 00 - never used; intended to mark instance as pointing to duplicate data rather than its own data		:0x'''04''' 00 00 00 - never used; intended to mark instance as pointing to duplicate data rather than its own data
	:0x'''08''' 00 00 00 - instance's data is being used by duplicate instances as a source		:0x'''08''' 00 00 00 - instance's data is being used by duplicate instances as a source
Line 185:		Line 185:
	:0x00 00 '''00''' 00 - versioning timestamp – month		:0x00 00 '''00''' 00 - versioning timestamp – month
	:0x00 00 00 '''00''' - versioning timestamp – year-->		:0x00 00 00 '''00''' - versioning timestamp – year-->
	The flags "unnamed" and "~~empty~~" require special explanation.		The flags "unnamed" and "placeholder" require special explanation.

	===Unnamed and ~~empty~~ resources===		===Unnamed and placeholder resources===
	You'll notice that the level file header lists fewer names (7,124) than instances (9,347). That's because there are 3 types of instance:		You'll notice that the level file header lists fewer names (7,124) than instances (9,347). That's because there are 3 types of instance:
	*Unnamed and not ~~empty~~ - they are only referenced by other instances in the same file, generally as child data (e.g., 3D geometry elements like ABNA are "contained" by AKEV, a level's environment).		*Unnamed and not placeholder - they are only referenced by other instances in the same file via instance ID; these are generally what can be considered child data of a named instance (e.g., 3D geometry elements like ABNA are "contained" by AKEV, a level's environment).
	*:In vanilla Oni .dats there are some rare occurrences of unnamed non-~~empty~~ ''orphan'' instances (e.g., [[OBD:File types/Naming#TRCM\|TRCM]]). These are a form of garbage and are discarded by OniSplit when unpacking a level.		*:In vanilla Oni .dats there are some rare occurrences of unnamed non-placeholder ''orphan'' instances (e.g., [[OBD:File types/Naming#TRCM\|TRCM]]). These are a form of garbage and are discarded by OniSplit when unpacking a level.
	*Named and not ~~empty~~ - they can be referenced by other instances in any file and the engine can use their name or template tag to find them.		*Named and not placeholder - they can be referenced by other instances in any file and the engine can use their name or template tag to find them.
	*Named and ~~empty~~ - "~~empty~~" instances are used in level-specific instance files (i.e. not in level0_Final.dat) to associate an instance ID with a name. For every ~~empty~~ resource, there's another one with a matching name in level0_Final.dat that has data in it. The ~~empty~~ resource in the instance file is ~~(usually)~~ looked up by ID, then the engine searches all the loaded files for a non-~~empty~~ instance with the same name, causing it to find the actual file in the global data in level0_Final.dat.		*Named and placeholder - "placeholder" instances are used in level-specific instance files (i.e. not in level0_Final.dat) to associate an instance ID with a name. For every placeholder resource, there's another one with a matching name in level0_Final.dat that has data in it. The placeholder resource in the instance file is looked up by ID or name and then the engine searches all the loaded files for a non-placeholder instance with the same name, causing it to find the actual file in the global data in level0_Final.dat.

	===Peeking ahead at instance name===		===Peeking ahead at instance name===