Error Database - Revision history

174.165.58.215 at 22:42, 13 October 2026

2026-10-13T22:42:50Z

← Older revision		Revision as of 18:42, 13 October 2026
Line 55:		Line 55:
	\| 140 \|\| 49097 \|\| 784 \|\| 753 \|\| 80 \|\| 0		\| 140 \|\| 49097 \|\| 784 \|\| 753 \|\| 80 \|\| 0
	\|}		\|}

			==== Function #3988 ====
			Message: Collection was modified; enumeration operation may not execute.
			Reported: Oct 13, 2026

			Resolution: Fixed #3988 enumeration error (in 3.0). The trigger seems to be damaged NPR ships that leave their fleet and cannot find a new home.

Wiki-admin at 13:41, 13 October 2026

2026-10-13T13:41:52Z

← Older revision		Revision as of 09:41, 13 October 2026
Line 18:		Line 18:

	Resolution: "aha, i found what this one was. Something to do with how I attempted to fix things earlier. I had deleted the Martians record of Earth from FCT_AlienPopulation, and because Earth was in view of their sensors it was throwing an error."		Resolution: "aha, i found what this one was. Something to do with how I attempted to fix things earlier. I had deleted the Martians record of Earth from FCT_AlienPopulation, and because Earth was in view of their sensors it was throwing an error."

			==== Function #1908 ====
			Reported: Oct 12, 2026

			"1908 is a function that updates tactical intelligence on the weapons of alien contacts. I have never seen one in that function before. Are you running any mods or have you made any changes directly to the database." -- Steve

			Speculation: "Okay, so ive been tinkering around, and I cant be sure, but uh, I suspect the bug is firing from the Aether salvaging ships. I cant be sure, but thats my working theory, because once I interupted their salvaging, the errors stopped throwing" -- reporting user

			Resolution: Pending

	==== Function #3821 ====		==== Function #3821 ====

Wiki-admin at 14:04, 12 October 2026

2026-10-12T14:04:33Z

← Older revision		Revision as of 10:04, 12 October 2026
Line 1:		Line 1:
	~~{{toclimit\|limit=4}}~~

	Aurora has a robust error system used by Steve to help debug when things aren't working correctly. At times, things can go wrong either due to a bug in the game or through the machinations of players (e.g. DB editing, etc.). While it's not known how many error conditions live in Aurora, over the years some of them crop up and Steve is happy to explain them. We try to keep track of them here.		Aurora has a robust error system used by Steve to help debug when things aren't working correctly. At times, things can go wrong either due to a bug in the game or through the machinations of players (e.g. DB editing, etc.). While it's not known how many error conditions live in Aurora, over the years some of them crop up and Steve is happy to explain them. We try to keep track of them here.

Wiki-admin at 14:03, 12 October 2026

2026-10-12T14:03:53Z

← Older revision		Revision as of 10:03, 12 October 2026
Line 1:		Line 1:
			{{toclimit\|limit=4}}

	Aurora has a robust error system used by Steve to help debug when things aren't working correctly. At times, things can go wrong either due to a bug in the game or through the machinations of players (e.g. DB editing, etc.). While it's not known how many error conditions live in Aurora, over the years some of them crop up and Steve is happy to explain them. We try to keep track of them here.		Aurora has a robust error system used by Steve to help debug when things aren't working correctly. At times, things can go wrong either due to a bug in the game or through the machinations of players (e.g. DB editing, etc.). While it's not known how many error conditions live in Aurora, over the years some of them crop up and Steve is happy to explain them. We try to keep track of them here.

Wiki-admin at 13:58, 12 October 2026

2026-10-12T13:58:46Z

← Older revision		Revision as of 09:58, 12 October 2026
Line 2:		Line 2:

	Where possible an error should have its #, and associated version if you know it, Steve's explanation for what the problem is, and the known solution, if any. Please note, that occasionally the solution to the error is to edit the game database, which can really truly break things -- so back up your database before pursuing some of these fixes.		Where possible an error should have its #, and associated version if you know it, Steve's explanation for what the problem is, and the known solution, if any. Please note, that occasionally the solution to the error is to edit the game database, which can really truly break things -- so back up your database before pursuing some of these fixes.

	~~{{toclimit\|limit=4}}~~

	__TOC__		__TOC__

Wiki-admin at 13:58, 12 October 2026

2026-10-12T13:58:35Z

← Older revision		Revision as of 09:58, 12 October 2026
Line 2:		Line 2:

	Where possible an error should have its #, and associated version if you know it, Steve's explanation for what the problem is, and the known solution, if any. Please note, that occasionally the solution to the error is to edit the game database, which can really truly break things -- so back up your database before pursuing some of these fixes.		Where possible an error should have its #, and associated version if you know it, Steve's explanation for what the problem is, and the known solution, if any. Please note, that occasionally the solution to the error is to edit the game database, which can really truly break things -- so back up your database before pursuing some of these fixes.

			{{toclimit\|limit=4}}

	__TOC__		__TOC__

Wiki-admin at 13:57, 12 October 2026

2026-10-12T13:57:58Z

← Older revision		Revision as of 09:57, 12 October 2026
Line 3:		Line 3:
	Where possible an error should have its #, and associated version if you know it, Steve's explanation for what the problem is, and the known solution, if any. Please note, that occasionally the solution to the error is to edit the game database, which can really truly break things -- so back up your database before pursuing some of these fixes.		Where possible an error should have its #, and associated version if you know it, Steve's explanation for what the problem is, and the known solution, if any. Please note, that occasionally the solution to the error is to edit the game database, which can really truly break things -- so back up your database before pursuing some of these fixes.

	~~__FORCETOC__~~		__TOC__

	==== Function #111 ====		==== Function #111 ====

Wiki-admin at 13:55, 12 October 2026

2026-10-12T13:55:00Z

← Older revision		Revision as of 09:55, 12 October 2026
Line 17:		Line 17:
	"#454 is a function for the AI to assign target priorities to population-based targets (inc shipyards, ground forces, STO, etc.)" -- Steve		"#454 is a function for the AI to assign target priorities to population-based targets (inc shipyards, ground forces, STO, etc.)" -- Steve

	Resolution: ~~unknown~~		Resolution: "aha, i found what this one was. Something to do with how I attempted to fix things earlier. I had deleted the Martians record of Earth from FCT_AlienPopulation, and because Earth was in view of their sensors it was throwing an error."

	==== Function #3821 ====		==== Function #3821 ====

Wiki-admin at 13:35, 12 October 2026

2026-10-12T13:35:30Z

← Older revision		Revision as of 09:35, 12 October 2026
Line 18:		Line 18:

	Resolution: unknown		Resolution: unknown

			==== Function #3821 ====
			Reported: ~circa 2.6

			"Function 3821 is related to interrogation of prisoners." -- [https://aurora4x.com/t/consistant-function-3821/1162/2?u=falryx Steve]

			Speculation: This error appears to occur when an officer who is a POW is auto-assigned by Aurora to a new command.

			Resolution #1: Find the officer whose name is colored magenta in the officers window whose history shows them being taken prisoner and then being assigned a command. Retire the officer. This removes them from play.

			Resolution #2: Retain the officer in play by finding the officer in FCT_Commanders and changing Prisoner from 1 to 0.

	==== Function #3822 ====		==== Function #3822 ====
Line 23:		Line 34:

	"#3822 is PopulatePOWToListView, so it something to do with POWs." -- Steve		"#3822 is PopulatePOWToListView, so it something to do with POWs." -- Steve

			Speculation: This error seems to occur when the game is attempting to display or manage POWs but is prevented from doing so for some reason (e.g. the POWs are members of the same race/species that controls the population).

	Resolution: On Oct 12, 2026 a resolution to a game was to delete the single row in FCT_Prisoners. It was an NPR planet captured by the player and had POWs from the player Race on the planet. They did not show in the Empire or planet POW screen (it triggered this error). The only way to clear the error was to delete the row (effectively 'removing' the POWs from play).		Resolution: On Oct 12, 2026 a resolution to a game was to delete the single row in FCT_Prisoners. It was an NPR planet captured by the player and had POWs from the player Race on the planet. They did not show in the Empire or planet POW screen (it triggered this error). The only way to clear the error was to delete the row (effectively 'removing' the POWs from play).

Wiki-admin at 13:30, 12 October 2026

2026-10-12T13:30:10Z

@@ Line 5: / Line 5: @@
 __FORCETOC__
-==== Error #111 ====
+==== Function #111 ====
 Reported Oct 10, 2026
@@ Line 11: / Line 11: @@
 Resolution: The player had created a multi-NPR Sol start and given each of the NPRs on Earth a diplomatic station. When they deleted/destroyed the stations the error stopped happening.