Technical Difficulties - Revision history

IcyLeoDragon: /* Eluna and the Moth Surfacing crash */ added effects of different difficulties

2025-07-12T20:11:17Z

Eluna and the Moth Surfacing crash: added effects of different difficulties

← Older revision		Revision as of 20:11, 12 July 2025
Line 134:		Line 134:
	The console version of this game (possibly only the Nintendo Switch Version) has many crash, graphics, and other bugs. Five specific bugs will make a campaign unplayable:		The console version of this game (possibly only the Nintendo Switch Version) has many crash, graphics, and other bugs. Five specific bugs will make a campaign unplayable:
	===[[Calamity]] crash===		===[[Calamity]] crash===
	When drawing a calamity after a battle, the game consistently crashes. If the battle plays out differently, sometimes it will not crash, and a different starting event or enemy force may also affect it, but if the glitch progresses far enough, no battle will not crash. As end-of-chapter or end-of-campaign battles do not generate a calamity, they are safe from this glitch. At ~100 calamities, however, even overland calamities will cause a crash, so the [[achievement]] “Overwhelming Monstrosity” is impossible. Seems to be more likely with more calamities, so maybe try an overland/comic strategy that results in less calamities.		When drawing a calamity after a battle, the game consistently crashes. If the battle plays out differently, sometimes it will not crash, and a different starting event or enemy force may also affect it, but if the glitch progresses far enough, no battle will not crash. As end-of-chapter or end-of-campaign battles do not generate a calamity, they are safe from this glitch. At ~100 calamities, however, even overland calamities will cause a crash, so the [[achievement]] “Overwhelming Monstrosity” is impossible. Seems to be more likely with more calamities, so maybe try an overland/comic strategy that results in less calamities. Storyteller overland [[difficulty]] decreases calamities to the point where this glitch is irrelevant, and it is unknown whether Tragic Hero+ overland difficulties are possible, although a Tragic Hero 3-chapter should be.
	=== Save failure glitch ===		=== Save failure glitch ===
	This glitch starts unpredictably, seemingly unrelated to events or enemies. When you try to save, it will claim you saved without actually creating a save file. This has the same effect for autosaves and overwrites, effectively deleting a file. Successfully saving is somewhat likely at the beginning, but it becomes less and less common the more the glitch progresses. However, making many attempts to save in succession does not seem to work, although sometimes it will work after up to four. In the case where about four attempts have failed, overwriting or deleting a file seems to give you another chance for four saves. Eventually, another glitch appears where it claims you have maximum save files when you don’t, in which case you are forced to overwrite or delete a file, but you are able to successfully save. However, several saves later, saves resume failing even when it claims you have maximum. This glitch spreads to other save files, and if you delete all infected saves and even all saves, the glitch persists. In a different campaign, the glitch stays dormant for half to a full chapter before starting with the same initial symptoms as in the first campaign. Somehow, this glitch persists even when data is cleared for an account, although it doesn’t spread between accounts. There is no known way to avoid this glitch.		This glitch starts unpredictably, seemingly unrelated to events or enemies. When you try to save, it will claim you saved without actually creating a save file. This has the same effect for autosaves and overwrites, effectively deleting a file. Successfully saving is somewhat likely at the beginning, but it becomes less and less common the more the glitch progresses. However, making many attempts to save in succession does not seem to work, although sometimes it will work after up to four. In the case where about four attempts have failed, overwriting or deleting a file seems to give you another chance for four saves. Eventually, another glitch appears where it claims you have maximum save files when you don’t, in which case you are forced to overwrite or delete a file, but you are able to successfully save. However, several saves later, saves resume failing even when it claims you have maximum. This glitch spreads to other save files, and if you delete all infected saves and even all saves, the glitch persists. In a different campaign, the glitch stays dormant for half to a full chapter before starting with the same initial symptoms as in the first campaign. Somehow, this glitch persists even when data is cleared for an account, although it doesn’t spread between accounts. There is no known way to avoid this glitch.

	===Eluna and the Moth [[Surfacing]] crash===		===[[Eluna and the Moth]] [[Surfacing]] crash===
	A glitch involving the final battle of Eluna and the Moth. [[Mastery]] cannot be seen in its entirety, although it can be skipped fairly consistently. However, after that, when the final character exits the tower, the “Surfacing” comic never appears, although a marker saying that it will appear shows up just before the game crashes. It is unknown whether Eluna and the Moth is completable ~~at all~~ on ~~Console~~ edition.		A glitch involving the final battle of Eluna and the Moth. [[Mastery]] cannot be seen in its entirety, although it can be skipped fairly consistently. However, after that, on difficulties beyond Storyteller, when the final character exits the tower, the “Surfacing” comic never appears, although a marker saying that it will appear shows up just before the game crashes. On Storyteller difficulty, the comic sometimes appears, in which case the second panel crashes the game. However, the event can still be skipped and then read from the third (or maybe fourth) panel onward, and there are no further problems once the event finishes. It is unknown whether Eluna and the Moth is completable on higher difficulties in console edition.
	===[[Black Castle Ruins]] crash===		===[[Black Castle Ruins]] crash===
	The [[Generic Campaign]] final capstone Black Castle Ruins will consistently crash on certain turns sometime before the enemies are done taking their turns. This glitch is very likely to happen before Turn 4, and it is unknown what causes a specific turn to create a lock, although enemy attacks and especially reactions by the heroes are known to worsen things. This makes Black Castle Ruins effectively impossible on Console edition, although very fast and strong hunters may be able to reach and defeat the boss in time. It is unknown whether victory events would play correctly without crashing. Since the final capstone is generated at the beginning of the campaign, this stops the campaign from being completed entirely. This glitch was encountered in two campaigns, but only with the [[Drauven]] boss [[Dravonne]], and it is unknown whether other factions would create the same effect, although it is likely that they would.		The [[Generic Campaign]] final capstone Black Castle Ruins will consistently crash on certain turns sometime before the enemies are done taking their turns. This glitch is very likely to happen before Turn 4, and it is unknown what causes a specific turn to create a lock, although enemy attacks and especially reactions by the heroes are known to worsen things. This makes Black Castle Ruins effectively impossible on Console edition, although very fast and strong hunters may be able to reach and defeat the boss in time. It is unknown whether victory events would play correctly without crashing. Since the final capstone is generated at the beginning of the campaign, this stops the campaign from being completed entirely. This glitch was encountered in two campaigns, but only with the [[Drauven]] boss [[Dravonne]], and it is unknown whether other factions would create the same effect, although it is likely that they would. Storyteller difficulty likely solves this problem, and Tragic Hero probably consistently crashes on Turn 1.

	=== Carved in Stone glitch ===		=== Carved in Stone glitch ===
	Saving in a Carved in Stone campaign can corrupt the save, erasing the data for the campaign. This bug was specifically mentioned to be fixed in the patch notes.		Saving in a Carved in Stone campaign can corrupt the save, erasing the data for the campaign. This bug was specifically mentioned to be fixed in the patch notes.

IcyLeoDragon: /* Save failure glitch */ added info and renamed section

2025-05-28T22:04:39Z

Save failure glitch: added info and renamed section

← Older revision		Revision as of 22:04, 28 May 2025
Line 135:		Line 135:
	===[[Calamity]] crash===		===[[Calamity]] crash===
	When drawing a calamity after a battle, the game consistently crashes. If the battle plays out differently, sometimes it will not crash, and a different starting event or enemy force may also affect it, but if the glitch progresses far enough, no battle will not crash. As end-of-chapter or end-of-campaign battles do not generate a calamity, they are safe from this glitch. At ~100 calamities, however, even overland calamities will cause a crash, so the [[achievement]] “Overwhelming Monstrosity” is impossible. Seems to be more likely with more calamities, so maybe try an overland/comic strategy that results in less calamities.		When drawing a calamity after a battle, the game consistently crashes. If the battle plays out differently, sometimes it will not crash, and a different starting event or enemy force may also affect it, but if the glitch progresses far enough, no battle will not crash. As end-of-chapter or end-of-campaign battles do not generate a calamity, they are safe from this glitch. At ~100 calamities, however, even overland calamities will cause a crash, so the [[achievement]] “Overwhelming Monstrosity” is impossible. Seems to be more likely with more calamities, so maybe try an overland/comic strategy that results in less calamities.
	=== ~~[[Eluna and the Moth]] save~~ failure glitch ===		=== Save failure glitch ===
	This glitch starts unpredictably, seemingly unrelated to events or enemies. When you try to save, it will claim you saved without actually creating a save file. This has the same effect for autosaves and overwrites, effectively deleting a file. Successfully saving is somewhat likely at the beginning, but it becomes less and less common the more the glitch progresses. However, making many attempts to save in succession does not seem to work, although sometimes it will work after up to four. In the case where about four attempts have failed, overwriting or deleting a file seems to give you another chance for four saves. Eventually, another glitch appears where it claims you have maximum save files when you don’t, in which case you are forced to overwrite or delete a file, but you ~~have a high chance to be~~ able to successfully save. This glitch spreads to other save files, and if you delete all infected saves and even all saves, the glitch persists. In a different campaign, the glitch stays dormant for half to a full chapter before starting with the same initial symptoms as in the first campaign. Somehow, this glitch persists even when data is cleared for an account, although it doesn’t spread between accounts. There is no known way to avoid this glitch.		This glitch starts unpredictably, seemingly unrelated to events or enemies. When you try to save, it will claim you saved without actually creating a save file. This has the same effect for autosaves and overwrites, effectively deleting a file. Successfully saving is somewhat likely at the beginning, but it becomes less and less common the more the glitch progresses. However, making many attempts to save in succession does not seem to work, although sometimes it will work after up to four. In the case where about four attempts have failed, overwriting or deleting a file seems to give you another chance for four saves. Eventually, another glitch appears where it claims you have maximum save files when you don’t, in which case you are forced to overwrite or delete a file, but you are able to successfully save. However, several saves later, saves resume failing even when it claims you have maximum. This glitch spreads to other save files, and if you delete all infected saves and even all saves, the glitch persists. In a different campaign, the glitch stays dormant for half to a full chapter before starting with the same initial symptoms as in the first campaign. Somehow, this glitch persists even when data is cleared for an account, although it doesn’t spread between accounts. There is no known way to avoid this glitch.

	===Eluna and the Moth [[Surfacing]] crash===		===Eluna and the Moth [[Surfacing]] crash===
	A glitch involving the final battle of Eluna and the Moth. [[Mastery]] cannot be seen in its entirety, although it can be skipped fairly consistently. However, after that, when the final character exits the tower, the “Surfacing” comic never appears, although a marker saying that it will appear shows up just before the game crashes. It is unknown whether Eluna and the Moth is completable at all on Console edition.		A glitch involving the final battle of Eluna and the Moth. [[Mastery]] cannot be seen in its entirety, although it can be skipped fairly consistently. However, after that, when the final character exits the tower, the “Surfacing” comic never appears, although a marker saying that it will appear shows up just before the game crashes. It is unknown whether Eluna and the Moth is completable at all on Console edition.

IcyLeoDragon: Fixed errors in glitch description

2025-05-28T22:00:22Z

Fixed errors in glitch description

← Older revision		Revision as of 22:00, 28 May 2025
Line 134:		Line 134:
	The console version of this game (possibly only the Nintendo Switch Version) has many crash, graphics, and other bugs. Five specific bugs will make a campaign unplayable:		The console version of this game (possibly only the Nintendo Switch Version) has many crash, graphics, and other bugs. Five specific bugs will make a campaign unplayable:
	===[[Calamity]] crash===		===[[Calamity]] crash===
	When drawing a calamity after a battle, the game consistently crashes. If the battle plays out differently, sometimes it will not crash, and a different starting event or enemy force may also affect it, but if the glitch progresses far enough, no battle will not crash. As end-of-chapter or end-of-campaign battles do not generate a calamity, they are safe from this glitch. Seems to be more likely with more calamities, so maybe try an overland/comic strategy that results in less calamities.		When drawing a calamity after a battle, the game consistently crashes. If the battle plays out differently, sometimes it will not crash, and a different starting event or enemy force may also affect it, but if the glitch progresses far enough, no battle will not crash. As end-of-chapter or end-of-campaign battles do not generate a calamity, they are safe from this glitch. At ~100 calamities, however, even overland calamities will cause a crash, so the [[achievement]] “Overwhelming Monstrosity” is impossible. Seems to be more likely with more calamities, so maybe try an overland/comic strategy that results in less calamities.
	=== [[Eluna and the Moth]] save failure glitch ===		=== [[Eluna and the Moth]] save failure glitch ===
	This glitch ~~seems~~ to ~~start sometime in chapter 5 of Eluna and the Moth. It is unknown what causes it, but it does not happen every time~~. When you try to save, it will claim you saved without actually creating a save file. This has the same effect for autosaves and overwrites, effectively deleting a file. Successfully saving is somewhat likely at the beginning, but it becomes less and less common the more the glitch progresses. However, making many attempts to save in succession does not seem to work, although sometimes it will work after up to four. In the case where about four attempts have failed, overwriting or deleting a file seems to give you another chance for four saves. Eventually, another glitch appears where it claims you have maximum save files when you don’t, in which case you are forced to overwrite or delete a file, but you have a high chance to be able to successfully save. This glitch spreads to other save files, and if you delete all infected saves and even all saves, the glitch persists. In a different campaign, the glitch stays dormant for half to a full chapter before starting with the same initial symptoms as in ~~Eluna and~~ the ~~Moth~~. Somehow, this glitch persists even when data is cleared for an account, although it doesn’t spread between accounts. ~~The only~~ known way to avoid this glitch ~~is to avoid Eluna and the Moth entirely, or play it only on accounts with small legacies to avoid extreme progress loss~~.		This glitch starts unpredictably, seemingly unrelated to events or enemies. When you try to save, it will claim you saved without actually creating a save file. This has the same effect for autosaves and overwrites, effectively deleting a file. Successfully saving is somewhat likely at the beginning, but it becomes less and less common the more the glitch progresses. However, making many attempts to save in succession does not seem to work, although sometimes it will work after up to four. In the case where about four attempts have failed, overwriting or deleting a file seems to give you another chance for four saves. Eventually, another glitch appears where it claims you have maximum save files when you don’t, in which case you are forced to overwrite or delete a file, but you have a high chance to be able to successfully save. This glitch spreads to other save files, and if you delete all infected saves and even all saves, the glitch persists. In a different campaign, the glitch stays dormant for half to a full chapter before starting with the same initial symptoms as in the first campaign. Somehow, this glitch persists even when data is cleared for an account, although it doesn’t spread between accounts. There is no known way to avoid this glitch.
	===Eluna and the Moth [[Surfacing]] crash===		===Eluna and the Moth [[Surfacing]] crash===
	A ~~completely unrelated~~ glitch ~~with chapter 5~~ of Eluna and the Moth. [[Mastery]] cannot be seen in its entirety, although it can be skipped fairly consistently. However, after that, when the final character exits the tower, the “Surfacing” comic never appears, although a marker saying that it will appear shows up just before the game crashes. It is unknown whether Eluna and the Moth is completable at all on Console edition.		A glitch involving the final battle of Eluna and the Moth. [[Mastery]] cannot be seen in its entirety, although it can be skipped fairly consistently. However, after that, when the final character exits the tower, the “Surfacing” comic never appears, although a marker saying that it will appear shows up just before the game crashes. It is unknown whether Eluna and the Moth is completable at all on Console edition.
	===[[Black Castle Ruins]] crash===		===[[Black Castle Ruins]] crash===
	The [[Generic Campaign]] final capstone Black Castle Ruins will consistently crash on certain turns sometime before the enemies are done taking their turns. This glitch is very likely to happen before Turn 4, and it is unknown what causes a specific turn to create a lock, although enemy attacks and especially reactions by the heroes are known to worsen things. This makes Black Castle Ruins effectively impossible on Console edition, although very fast and strong hunters may be able to reach and defeat the boss in time. It is unknown whether victory events would play correctly without crashing. Since the final capstone is generated at the beginning of the campaign, this stops the campaign from being completed entirely. This glitch was encountered in two campaigns, but only with the [[Drauven]] boss [[Dravonne]], and it is unknown whether other factions would create the same effect, although it is likely that they would.		The [[Generic Campaign]] final capstone Black Castle Ruins will consistently crash on certain turns sometime before the enemies are done taking their turns. This glitch is very likely to happen before Turn 4, and it is unknown what causes a specific turn to create a lock, although enemy attacks and especially reactions by the heroes are known to worsen things. This makes Black Castle Ruins effectively impossible on Console edition, although very fast and strong hunters may be able to reach and defeat the boss in time. It is unknown whether victory events would play correctly without crashing. Since the final capstone is generated at the beginning of the campaign, this stops the campaign from being completed entirely. This glitch was encountered in two campaigns, but only with the [[Drauven]] boss [[Dravonne]], and it is unknown whether other factions would create the same effect, although it is likely that they would.

	== ~~[[The Enduring War]]~~ Carved in Stone glitch ==		=== Carved in Stone glitch ===
	~~If the Enduring War campaign is played~~ in Carved in Stone ~~mode~~, ~~it is possible~~ for the ~~file~~ to ~~completely deleted after a crash, and not always one creating a new autosave. It is unknown what causes this, but it seems like both components individually don’t have any problems~~.		Saving in a Carved in Stone campaign can corrupt the save, erasing the data for the campaign. This bug was specifically mentioned to be fixed in the patch notes.

IcyLeoDragon: /* The Enduring War Carved in Stone glitch */ sorry, fixed typo

2025-04-04T20:08:07Z

The Enduring War Carved in Stone glitch: sorry, fixed typo

← Older revision		Revision as of 20:08, 4 April 2025
Line 143:		Line 143:

	== [[The Enduring War]] Carved in Stone glitch ==		== [[The Enduring War]] Carved in Stone glitch ==
	If the Enduring War campaign is played as in Carved in Stone mode, it is possible for the file to completely deleted after a crash, and not always one creating a new autosave. It is unknown what causes this, but it seems like both components individually don’t have any problems.		If the Enduring War campaign is played in Carved in Stone mode, it is possible for the file to completely deleted after a crash, and not always one creating a new autosave. It is unknown what causes this, but it seems like both components individually don’t have any problems.

IcyLeoDragon: /* Console version */ forgot one

2025-04-04T20:07:34Z

Console version: forgot one

← Older revision		Revision as of 20:07, 4 April 2025
Line 132:		Line 132:
	# You can also find the graphics.json file in your players folder, and set shadowBufferSize to 0.25, or 0.125		# You can also find the graphics.json file in your players folder, and set shadowBufferSize to 0.25, or 0.125
	==Console version==		==Console version==
	The console version of this game (possibly only the Nintendo Switch Version) has many crash, graphics, and other bugs. ~~Four~~ specific bugs will make a campaign unplayable:		The console version of this game (possibly only the Nintendo Switch Version) has many crash, graphics, and other bugs. Five specific bugs will make a campaign unplayable:
	===[[Calamity]] crash===		===[[Calamity]] crash===
	When drawing a calamity after a battle, the game consistently crashes. If the battle plays out differently, sometimes it will not crash, and a different starting event or enemy force may also affect it, but if the glitch progresses far enough, no battle will not crash. As end-of-chapter or end-of-campaign battles do not generate a calamity, they are safe from this glitch. Seems to be more likely with more calamities, so maybe try an overland/comic strategy that results in less calamities.		When drawing a calamity after a battle, the game consistently crashes. If the battle plays out differently, sometimes it will not crash, and a different starting event or enemy force may also affect it, but if the glitch progresses far enough, no battle will not crash. As end-of-chapter or end-of-campaign battles do not generate a calamity, they are safe from this glitch. Seems to be more likely with more calamities, so maybe try an overland/comic strategy that results in less calamities.
Line 141:		Line 141:
	===[[Black Castle Ruins]] crash===		===[[Black Castle Ruins]] crash===
	The [[Generic Campaign]] final capstone Black Castle Ruins will consistently crash on certain turns sometime before the enemies are done taking their turns. This glitch is very likely to happen before Turn 4, and it is unknown what causes a specific turn to create a lock, although enemy attacks and especially reactions by the heroes are known to worsen things. This makes Black Castle Ruins effectively impossible on Console edition, although very fast and strong hunters may be able to reach and defeat the boss in time. It is unknown whether victory events would play correctly without crashing. Since the final capstone is generated at the beginning of the campaign, this stops the campaign from being completed entirely. This glitch was encountered in two campaigns, but only with the [[Drauven]] boss [[Dravonne]], and it is unknown whether other factions would create the same effect, although it is likely that they would.		The [[Generic Campaign]] final capstone Black Castle Ruins will consistently crash on certain turns sometime before the enemies are done taking their turns. This glitch is very likely to happen before Turn 4, and it is unknown what causes a specific turn to create a lock, although enemy attacks and especially reactions by the heroes are known to worsen things. This makes Black Castle Ruins effectively impossible on Console edition, although very fast and strong hunters may be able to reach and defeat the boss in time. It is unknown whether victory events would play correctly without crashing. Since the final capstone is generated at the beginning of the campaign, this stops the campaign from being completed entirely. This glitch was encountered in two campaigns, but only with the [[Drauven]] boss [[Dravonne]], and it is unknown whether other factions would create the same effect, although it is likely that they would.

			== [[The Enduring War]] Carved in Stone glitch ==
			If the Enduring War campaign is played as in Carved in Stone mode, it is possible for the file to completely deleted after a crash, and not always one creating a new autosave. It is unknown what causes this, but it seems like both components individually don’t have any problems.

IcyLeoDragon: I don’t know where this should go, because I can’t use discord or submit a log. If this should be moved to a subpage or something or be deleted, that is fine, as long as, if it is deleted, the info is submitted at least as noticeably as with a bug report in the main game.

2025-04-04T19:58:07Z

I don’t know where this should go, because I can’t use discord or submit a log. If this should be moved to a subpage or something or be deleted, that is fine, as long as, if it is deleted, the info is submitted at least as noticeably as with a bug report in the main game.

← Older revision		Revision as of 19:58, 4 April 2025
Line 131:		Line 131:
	# Turn off Ability Particles (do this last, not recommended)		# Turn off Ability Particles (do this last, not recommended)
	# You can also find the graphics.json file in your players folder, and set shadowBufferSize to 0.25, or 0.125		# You can also find the graphics.json file in your players folder, and set shadowBufferSize to 0.25, or 0.125
			==Console version==
			The console version of this game (possibly only the Nintendo Switch Version) has many crash, graphics, and other bugs. Four specific bugs will make a campaign unplayable:
			===[[Calamity]] crash===
			When drawing a calamity after a battle, the game consistently crashes. If the battle plays out differently, sometimes it will not crash, and a different starting event or enemy force may also affect it, but if the glitch progresses far enough, no battle will not crash. As end-of-chapter or end-of-campaign battles do not generate a calamity, they are safe from this glitch. Seems to be more likely with more calamities, so maybe try an overland/comic strategy that results in less calamities.
			=== [[Eluna and the Moth]] save failure glitch ===
			This glitch seems to start sometime in chapter 5 of Eluna and the Moth. It is unknown what causes it, but it does not happen every time. When you try to save, it will claim you saved without actually creating a save file. This has the same effect for autosaves and overwrites, effectively deleting a file. Successfully saving is somewhat likely at the beginning, but it becomes less and less common the more the glitch progresses. However, making many attempts to save in succession does not seem to work, although sometimes it will work after up to four. In the case where about four attempts have failed, overwriting or deleting a file seems to give you another chance for four saves. Eventually, another glitch appears where it claims you have maximum save files when you don’t, in which case you are forced to overwrite or delete a file, but you have a high chance to be able to successfully save. This glitch spreads to other save files, and if you delete all infected saves and even all saves, the glitch persists. In a different campaign, the glitch stays dormant for half to a full chapter before starting with the same initial symptoms as in Eluna and the Moth. Somehow, this glitch persists even when data is cleared for an account, although it doesn’t spread between accounts. The only known way to avoid this glitch is to avoid Eluna and the Moth entirely, or play it only on accounts with small legacies to avoid extreme progress loss.
			===Eluna and the Moth [[Surfacing]] crash===
			A completely unrelated glitch with chapter 5 of Eluna and the Moth. [[Mastery]] cannot be seen in its entirety, although it can be skipped fairly consistently. However, after that, when the final character exits the tower, the “Surfacing” comic never appears, although a marker saying that it will appear shows up just before the game crashes. It is unknown whether Eluna and the Moth is completable at all on Console edition.
			===[[Black Castle Ruins]] crash===
			The [[Generic Campaign]] final capstone Black Castle Ruins will consistently crash on certain turns sometime before the enemies are done taking their turns. This glitch is very likely to happen before Turn 4, and it is unknown what causes a specific turn to create a lock, although enemy attacks and especially reactions by the heroes are known to worsen things. This makes Black Castle Ruins effectively impossible on Console edition, although very fast and strong hunters may be able to reach and defeat the boss in time. It is unknown whether victory events would play correctly without crashing. Since the final capstone is generated at the beginning of the campaign, this stops the campaign from being completed entirely. This glitch was encountered in two campaigns, but only with the [[Drauven]] boss [[Dravonne]], and it is unknown whether other factions would create the same effect, although it is likely that they would.

Pbelanger: /* Multiplayer Stuck at "Logging In" */ Added a bit, plus mentioned connecting via IP

2024-07-10T15:00:31Z

Multiplayer Stuck at "Logging In": Added a bit, plus mentioned connecting via IP

← Older revision		Revision as of 15:00, 10 July 2024
Line 38:		Line 38:
	(There isn't much more to say beyond this; try the things listed in the message, let us know if you still can't figure it out.)		(There isn't much more to say beyond this; try the things listed in the message, let us know if you still can't figure it out.)
	===Multiplayer Stuck at "Logging In"===		===Multiplayer Stuck at "Logging In"===
	Be sure neither player is using a VPN, ~~and check~~ that Wildermyth isn't being blocked by your firewalls/antivirus.
			* Be sure neither player is using a VPN
			* If you're using Steam, make sure players are set to "Online" on Steam Friends
			* Check that Wildermyth isn't being blocked by your firewalls/antivirus

			If none of those fix the issue, you may want to try connecting via '''IP address and [https://www.noip.com/support/knowledgebase/general-port-forwarding-guide port forwarding]''' instead of the standard connecting via Steam/Epic.
	===Game Won't Start, External Monitor Message===		===Game Won't Start, External Monitor Message===
	Sometimes you may see this message when trying to start Wildermyth:		Sometimes you may see this message when trying to start Wildermyth:

Pbelanger: /* If You Got an Error Message... */ Period

2024-06-07T16:58:55Z

If You Got an Error Message...: Period

← Older revision		Revision as of 16:58, 7 June 2024
Line 64:		Line 64:
	Legacy backup file could not be loaded. This may be fine, but just in case, a copy of the broken backup file has been stored as "legacy_backup_(numbers)".		Legacy backup file could not be loaded. This may be fine, but just in case, a copy of the broken backup file has been stored as "legacy_backup_(numbers)".
	Usually not a big deal, since the backup gets replaced on load anyway, but we store a separate copy of the broken backup just in case.		Usually not a big deal, since the backup gets replaced on load anyway, but we store a separate copy of the broken backup just in case.
	No legacy or legacy backup file found for this account If you know you should have heroes in your legacy, STOP! Check your game files for the legacy file (players/yourName/legacy.json.zip). If it doesn't exist, and you're using Steam, this may be a Steam Cloud issue. If you're using Steam Cloud for this game, check https://store.steampowered.com/account/remotestorageapp?appid=763890 and look for the players/yourName/legacy.json.zip file there. If it exists, download it and put a copy of it into your player folder! If it doesn't exist, and you recently played Wildermyth on a different computer, first turn off Steam Cloud for Wildermyth, then open up the game files on your other computer and copy the legacy.json.zip file from there.		No legacy or legacy backup file found for this account. If you know you should have heroes in your legacy, STOP! Check your game files for the legacy file (players/yourName/legacy.json.zip). If it doesn't exist, and you're using Steam, this may be a Steam Cloud issue. If you're using Steam Cloud for this game, check https://store.steampowered.com/account/remotestorageapp?appid=763890 and look for the players/yourName/legacy.json.zip file there. If it exists, download it and put a copy of it into your player folder! If it doesn't exist, and you recently played Wildermyth on a different computer, first turn off Steam Cloud for Wildermyth, then open up the game files on your other computer and copy the legacy.json.zip file from there.
	This message is shown if your player account has save files, but no legacy or legacy backup file. As far as we can tell, this happens due to Steam Cloud deleting those files for some reason. (But the issue is uncommon, and we don't have any way to reproduce it to know for sure) Do all the steps listed in the error message to see if you can find a place where your legacy file still exists. The section below ("If You Didn't Get an Error Message...") also lists some similar steps, and what to do if your legacy ''is'' gone for good.		This message is shown if your player account has save files, but no legacy or legacy backup file. As far as we can tell, this happens due to Steam Cloud deleting those files for some reason. (But the issue is uncommon, and we don't have any way to reproduce it to know for sure) Do all the steps listed in the error message to see if you can find a place where your legacy file still exists. The section below ("If You Didn't Get an Error Message...") also lists some similar steps, and what to do if your legacy ''is'' gone for good.

Pbelanger: Added another legacy file error

2024-06-07T16:58:04Z

Added another legacy file error

← Older revision		Revision as of 16:58, 7 June 2024
Line 64:		Line 64:
	Legacy backup file could not be loaded. This may be fine, but just in case, a copy of the broken backup file has been stored as "legacy_backup_(numbers)".		Legacy backup file could not be loaded. This may be fine, but just in case, a copy of the broken backup file has been stored as "legacy_backup_(numbers)".
	Usually not a big deal, since the backup gets replaced on load anyway, but we store a separate copy of the broken backup just in case.		Usually not a big deal, since the backup gets replaced on load anyway, but we store a separate copy of the broken backup just in case.
			No legacy or legacy backup file found for this account If you know you should have heroes in your legacy, STOP! Check your game files for the legacy file (players/yourName/legacy.json.zip). If it doesn't exist, and you're using Steam, this may be a Steam Cloud issue. If you're using Steam Cloud for this game, check https://store.steampowered.com/account/remotestorageapp?appid=763890 and look for the players/yourName/legacy.json.zip file there. If it exists, download it and put a copy of it into your player folder! If it doesn't exist, and you recently played Wildermyth on a different computer, first turn off Steam Cloud for Wildermyth, then open up the game files on your other computer and copy the legacy.json.zip file from there.
			This message is shown if your player account has save files, but no legacy or legacy backup file. As far as we can tell, this happens due to Steam Cloud deleting those files for some reason. (But the issue is uncommon, and we don't have any way to reproduce it to know for sure) Do all the steps listed in the error message to see if you can find a place where your legacy file still exists. The section below ("If You Didn't Get an Error Message...") also lists some similar steps, and what to do if your legacy ''is'' gone for good.

	=== If You Didn't Get an Error Message... ===		=== If You Didn't Get an Error Message... ===

Pbelanger: Added sections for Player Account Load Failure and Legacy Heroes Missing

2024-06-06T03:56:59Z

Added sections for Player Account Load Failure and Legacy Heroes Missing

← Older revision		Revision as of 03:56, 6 June 2024
Line 43:		Line 43:
	Ran into an exception preventing Wildermyth from running. This specific exception (Checks.java:100) sometimes happens if you're using a laptop with an external monitor hooked up to it. Some players have been able to fix the issue by unplugging the external monitor, removing their monitors in Windows Device Manager and letting Windows reinstall them, or uninstalling their monitor adapter and downloading a new one.		Ran into an exception preventing Wildermyth from running. This specific exception (Checks.java:100) sometimes happens if you're using a laptop with an external monitor hooked up to it. Some players have been able to fix the issue by unplugging the external monitor, removing their monitors in Windows Device Manager and letting Windows reinstall them, or uninstalling their monitor adapter and downloading a new one.
	Note that while this has generally happened for players with laptops using external displays, it has also happened to players using desktops or laptops without external displays. Regardless, your first step should be to try removing your monitors via Windows Device Manager. Here's an associated Reddit post with a bit more conversation on the matter: https://www.reddit.com/r/wildermyth/comments/oqix8f/crash_on_launch/		Note that while this has generally happened for players with laptops using external displays, it has also happened to players using desktops or laptops without external displays. Regardless, your first step should be to try removing your monitors via Windows Device Manager. Here's an associated Reddit post with a bit more conversation on the matter: https://www.reddit.com/r/wildermyth/comments/oqix8f/crash_on_launch/

			== Player Account Load Failure ==
			If you get this error message:
			There was a problem loading your player account located in the following folder: [filepath] Your save files (players/yourName/story) and legacy (players/yourName/legacy.json.zip) are probably still fine, but you may need to create a new account and move them into it.
			...it's usually a pretty easy fix! Generally speaking, it's a corrupt account.json file, which doesn't hold much important data. Just create a new in-game account, then in the game files (on Steam, right-click the game > Manage > Browse local files), move your save files ("story" folder) and legacy file from the old account to the new one. You can also try moving over the other options files as well.

			== Legacy Heroes Missing ==
			If you've opened up your legacy and see no heroes, there are several things that could be going on, most of which involve issues with the '''legacy.json.zip''' file in your players/[yourPlayerName] folder. Wildermyth keeps a '''legacy_backup.json.zip''' file as well, which is stored every time the main legacy file is successfully loaded.

			=== If You Got an Error Message... ===
			There are several error messages that can appear if your legacy failed to load properly. In all cases, if the legacy file fails to load, the failed legacy is stored as legacy_backupLoadFail_[time].json.zip, so it can be investigated if needed.
			Unable to load your legacy file; most recent backup has been loaded. A copy of the broken legacy file has been stored.
			This means something was wrong with your legacy file (corrupted, manually edited, bad data?) but that legacy_backup.json.zip was able to be properly loaded.
			Unable to load your legacy file, and no backup was found. A copy of the broken legacy file has been stored
			This means something was wrong with your legacy file, but there was no backup file to load. The legacy starts empty instead.
			Unable to load your legacy file, and also unable to load the most recent backup. A copy of the broken legacy file has been stored.
			This means something was wrong with your legacy file AND the legacy_backup file.
			Legacy backup file had a different id from Legacy file. This usually means there's an issue. A copy of the backup file has been stored as "legacy_backup_(numbers)". If it seems like you're missing legacy heroes or unlocks, try replacing legacy.json.zip with the created backup.
			This can happen if for some reason the legacy file has been deleted or replaced with a different legacy file.
			Legacy backup file could not be loaded. This may be fine, but just in case, a copy of the broken backup file has been stored as "legacy_backup_(numbers)".
			Usually not a big deal, since the backup gets replaced on load anyway, but we store a separate copy of the broken backup just in case.

			=== If You Didn't Get an Error Message... ===
			The first things to check:

			* Each in-game account has its own legacy. Make sure you're not accidentally using a different account than you meant to.
			* Check in the game files players/[yourPlayerName] for legacy.json.zip and legacy_backup.json.zip. Make a copy of these just in case. If there's a legacy_backup_[numbers] or legacy_backupLoadFail_[numbers] file as well, that's a good file to investigate.

			If there are no legacy heroes and no error messages, unfortunately, this usually means the legacy and legacy backup files have been deleted. The most common cause of this (as far as we can tell) is Steam Cloud deleting them for some reason.

			* If you played on another computer where your legacy was okay, you can turn off Steam Cloud before going on that other computer, then open the game files on the other computer and copy the legacy file from there.
			* If your legacy is gone for good, as long as you still have save files from previous campaigns, you can still get your heroes back by loading the last saves of those campaigns, completing them, and then putting those heroes into your legacy.
			** Note that the legacy file also contains unlocks and achievements, so you'll have to redo those. (For "Completing the tutorial" to unlock all the standard campaigns, keep in mind that you only have to do the first three missions of Ulstryx, which should only take a couple minutes) Keep in mind that if there are other things that you can't easily get back to the way they were in your legacy, you can always enable [[Testing\|devMode]] to cheat to try and get things back to how they were. We won't judge; losing progress sucks.

	==Game Crashes==		==Game Crashes==