User:Bluescreenofdeath/Known Bugs - Revision history

Bluescreenofdeath: most of them got fixed, yay!

2019-01-22T08:59:34Z

most of them got fixed, yay!

Bluescreenofdeath: update the list a bit

2016-06-22T08:07:22Z

update the list a bit

Elronnd: Savescumming

2016-02-09T00:24:46Z

Savescumming

Bluescreenofdeath at 11:12, 10 February 2015

2015-02-10T11:12:31Z

Bluescreenofdeath: The group spawn hang bug was fixed, so I removed it from the list.

2015-02-10T07:28:17Z

The group spawn hang bug was fixed, so I removed it from the list.

Bluescreenofdeath: The "punished player crashes on plane of water" bug should no longer happen outside of wizard mode.

2014-08-20T07:19:13Z

The "punished player crashes on plane of water" bug should no longer happen outside of wizard mode.

Bluescreenofdeath at 05:48, 15 August 2014

2014-08-15T05:48:05Z

Bluescreenofdeath: Removing the "dip gems into acid" crash bug since I fixed it in version v62.

2014-08-13T05:44:50Z

Removing the "dip gems into acid" crash bug since I fixed it in version v62.

124.171.109.164: grammer

2014-08-09T07:28:09Z

grammer

124.171.109.164: Found a bug.

2014-08-09T07:26:13Z

Found a bug.

← Older revision		Revision as of 08:59, 22 January 2019
Line 1:		Line 1:
	This page lists known bugs of [[Slash'EM Extended]] that aren't fixed yet. Any information that may help fixing them is appreciated; this is especially true for serious bugs that crash the game or (even worse) break savegame files.		This page lists known bugs of [[Slash'EM Extended]] that aren't fixed yet. Any information that may help fixing them is appreciated; this is especially true for serious bugs that crash the game or (even worse) break savegame files.

−	* Sometimes if a monster dies or certain other things happen, the game gives a "dmonsfree: 1 removed doesn't match 2 pending" disorder message. The game still runs afterwards but sometimes monsters come back to life after saving and restoring; the exact cause is still unknown. Might be related to vampiric players?
−	* Certain events can trigger a "cant find o_id <number>" message, sometimes followed by a game crash that may leave an unrecoverable savegame file. As long as I can't find a way to fix this serious bug, all players are advised to regularly back up their savegames so they don't lose all progress if the bug strikes; being able to track down and fix this bug would be great... It might or might not be related to any of the following: monsters spawning with cockatrice corpses, monsters with special corpse generation being killed while dropping items on death, or monsters being killed while they are in a pit.
−	* Certain other events can trigger an "obj_is_local" panic which may also cause savegame files to be unrecoverable. Looking at the source of old SLASH'EM versions and certain other variants suggests it has to do with light sources but I currently can't reproduce it...
−	* Rarely, the game segfaults on changing dungeon levels, leaving files that may or may not be recoverable into a playable savegame file. No clue why this is happening, as it doesn't seem to be easily reproducible.
	* The game may sometimes appear to hang when monsters are spawning. Often the remedy for this is to give it a while (a minute or two); if it still didn't unfreeze by then, killing the window might be the only option, which should cause the game to save, but this has a small chance of bugging the savegame file so be careful!		* The game may sometimes appear to hang when monsters are spawning. Often the remedy for this is to give it a while (a minute or two); if it still didn't unfreeze by then, killing the window might be the only option, which should cause the game to save, but this has a small chance of bugging the savegame file so be careful!
−	* (didn't happen in a long while, unknown if still there) Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.
−	* Dying with a lit lightsaber can cause a "program in disorder" message if a later character then encounters the bones file.
−	* If the player is using the Missingno race and turns off the "missing_safety" option, the game will frequently crash, sometimes leaving unrecoverable saves. This is actually done by design, but in order to actually play a full game with that race, keep missing_safety on!
−	* Entering certain dungeon levels can print a "rnd(1) attempted - program in disorder" message. Other causes for this bug exist too. The exact cause of this is not known but it doesn't seem to adversely affect anything.

@@ Line 1: / Line 1: @@
 This page lists known bugs of [[Slash'EM Extended]] that aren't fixed yet. Any information that may help fixing them is appreciated; this is especially true for serious bugs that crash the game or (even worse) break savegame files.
-* Sometimes if a monster dies or certain other things happen, the game gives a "dmonsfree: 1 removed doesn't match 2 pending" disorder message. The game still runs afterwards but sometimes monsters come back to life after saving and restoring; the exact cause is still unknown.
+* Sometimes if a monster dies or certain other things happen, the game gives a "dmonsfree: 1 removed doesn't match 2 pending" disorder message. The game still runs afterwards but sometimes monsters come back to life after saving and restoring; the exact cause is still unknown. Might be related to vampiric players?
 * Certain events can trigger a "cant find o_id <number>" message, sometimes followed by a game crash that may leave an unrecoverable savegame file. As long as I can't find a way to fix this serious bug, all players are advised to regularly back up their savegames so they don't lose all progress if the bug strikes; being able to track down and fix this bug would be great... It might or might not be related to any of the following: monsters spawning with cockatrice corpses, monsters with special corpse generation being killed while dropping items on death, or monsters being killed while they are in a pit.
 * Certain other events can trigger an "obj_is_local" panic which may also cause savegame files to be unrecoverable. Looking at the source of old SLASH'EM versions and certain other variants suggests it has to do with light sources but I currently can't reproduce it...
-* Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.
+* Rarely, the game segfaults on changing dungeon levels, leaving files that may or may not be recoverable into a playable savegame file. No clue why this is happening, as it doesn't seem to be easily reproducible.
 * Dying with a lit lightsaber can cause a "program in disorder" message if a later character then encounters the bones file.
-* If the player is using the Missingno race, the game will frequently crash, sometimes leaving unrecoverable saves. This is actually done by design, but in order to actually play a full game with that race, [[savescumming]] may be necessary
+* If the player is using the Missingno race and turns off the "missing_safety" option, the game will frequently crash, sometimes leaving unrecoverable saves. This is actually done by design, but in order to actually play a full game with that race, keep missing_safety on!

@@ Line 6: / Line 6: @@
 * Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.
 * Dying with a lit lightsaber can cause a "program in disorder" message if a later character then encounters the bones file.
-* If the player is using the Missingno race, the game will frequently crash, sometimes leaving unrecoverable saves. This is actually done by design, but in order to actually play a full game with that race, saving often and backing up the savegame files is necessary.
+* If the player is using the Missingno race, the game will frequently crash, sometimes leaving unrecoverable saves. This is actually done by design, but in order to actually play a full game with that race, [[savescumming]] may be necessary

@@ Line 2: / Line 2: @@
 * Sometimes if a monster dies or certain other things happen, the game gives a "dmonsfree: 1 removed doesn't match 2 pending" disorder message. The game still runs afterwards but sometimes monsters come back to life after saving and restoring; the exact cause is still unknown.
-* Certain events can trigger a "cant find o_id <number>" message, sometimes followed by a game crash that may leave an unrecoverable savegame file. As long as I can't find a way to fix this serious bug, all players are advised to regularly back up their savegames so they don't lose all progress if the bug strikes; being able to track down and fix this bug would be great...
+* Certain events can trigger a "cant find o_id <number>" message, sometimes followed by a game crash that may leave an unrecoverable savegame file. As long as I can't find a way to fix this serious bug, all players are advised to regularly back up their savegames so they don't lose all progress if the bug strikes; being able to track down and fix this bug would be great... It might or might not be related to any of the following: monsters spawning with cockatrice corpses, monsters with special corpse generation being killed while dropping items on death, or monsters being killed while they are in a pit.
 * Certain other events can trigger an "obj_is_local" panic which may also cause savegame files to be unrecoverable. Looking at the source of old SLASH'EM versions and certain other variants suggests it has to do with light sources but I currently can't reproduce it...
 * Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.
 * Dying with a lit lightsaber can cause a "program in disorder" message if a later character then encounters the bones file.
 * If the player is using the Missingno race, the game will frequently crash, sometimes leaving unrecoverable saves. This is actually done by design, but in order to actually play a full game with that race, saving often and backing up the savegame files is necessary.

@@ Line 1: / Line 1: @@
 This page lists known bugs of [[Slash'EM Extended]] that aren't fixed yet. Any information that may help fixing them is appreciated; this is especially true for serious bugs that crash the game or (even worse) break savegame files.
 * Sometimes if a monster dies or certain other things happen, the game gives a "dmonsfree: 1 removed doesn't match 2 pending" disorder message. The game still runs afterwards but sometimes monsters come back to life after saving and restoring; the exact cause is still unknown.
 * Certain events can trigger a "cant find o_id <number>" message, sometimes followed by a game crash that may leave an unrecoverable savegame file. As long as I can't find a way to fix this serious bug, all players are advised to regularly back up their savegames so they don't lose all progress if the bug strikes; being able to track down and fix this bug would be great...
@@ Line 7: / Line 6: @@
 * Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.
 * Dying with a lit lightsaber can cause a "program in disorder" message if a later character then encounters the bones file.

← Older revision		Revision as of 05:48, 15 August 2014
Line 7:		Line 7:
	* Certain other events can trigger an "obj_is_local" panic which may also cause savegame files to be unrecoverable. Looking at the source of old SLASH'EM versions and certain other variants suggests it has to do with light sources but I currently can't reproduce it...		* Certain other events can trigger an "obj_is_local" panic which may also cause savegame files to be unrecoverable. Looking at the source of old SLASH'EM versions and certain other variants suggests it has to do with light sources but I currently can't reproduce it...
	* Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.		* Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.
		+	* Dying with a lit lightsaber can cause a "program in disorder" message if a later character then encounters the bones file.

← Older revision		Revision as of 05:44, 13 August 2014
Line 7:		Line 7:
	* Certain other events can trigger an "obj_is_local" panic which may also cause savegame files to be unrecoverable. Looking at the source of old SLASH'EM versions and certain other variants suggests it has to do with light sources but I currently can't reproduce it...		* Certain other events can trigger an "obj_is_local" panic which may also cause savegame files to be unrecoverable. Looking at the source of old SLASH'EM versions and certain other variants suggests it has to do with light sources but I currently can't reproduce it...
	* Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.		* Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.
−
−	* Creating a potion via #dip-ping gems into acid can crash the game when the potion gets used/identified. The cause is that in objects.c, many more descriptions of potions are defined than there are actual potions, but dipping gems in acid creates potions BASED on their description. E.g. dipping a Topaz into acid makes a "Murky" potion, which may only exists as a description. Any attempt to utilize these pseudo potions will always result in a crash.
−	~~: Possible fixes, based on ease;~~
−	~~# Reduce the number of potion descriptions in objects.c to match the number of actual potions, while retaining all the ones needed for the acid dipping (listed from line 2009 in potion.c).~~
−	~~# Alter acid + gem dipping (2009, potion.c) to give set potion effects rather than set potion descriptions, e.g.~~
−	~~;instead of;~~
−	~~<syntaxhighlight lang="C">~~
−	~~case RUBY:~~
−	~~potion_descr = "ruby";~~
−	~~break;~~
−	~~case GARNET:~~
−	~~potion_descr = "pink";~~
−	~~break;~~
−	~~case JASPER:~~
−	~~potion_descr = "purple-red";~~
−	~~break;~~
−	~~</syntaxhighlight>~~
−	~~;use~~
−	~~<syntaxhighlight lang="C">~~
−	~~case RUBY:~~
−	~~return POT_GAIN_ABILITY;~~
−	~~break;~~
−	~~case GARNET:~~
−	~~return POT_RESTORE_ABILITY;~~
−	~~break;~~
−	~~case JASPER:~~
−	~~return POT_HEALING;~~
−	~~break;~~
−	~~</syntaxhighlight>~~
−	# add some kind of check to the acid dipping to make sure they are real potions, and to substitute with a default if the potion isn't fully defined, eg if "purple-red" potion doesn't exist, return POT_GAIN_ENERGY
−	: Frankly option 1 is boring, option 2 is the sensible but goes against the original purpose, and option 3 is probably a bit difficult for me. If you want, I can write up the full conversion for option 2. Just leave a note and I'll check back within 24 hours. --[[Special:Contributions/124.171.109.164\|124.171.109.164]] 07:26, 9 August 2014 (UTC)

@@ Line 8: / Line 8: @@
 * Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.
-* Creating a potion via #dip-ping gems into acid will can crash the game when the potion gets used/identified. The cause is that in objects.c, many more decriptions of potions are defined than there are actual potions, but dipping gems in acid creates potions BASED on their Description. E.g. dipping a Topaz into acid makes a "Murky" potion, which may possibly only exists as a description. Any attempt to utilize this pseudo potion will always result in a crash.
+* Creating a potion via #dip-ping gems into acid can crash the game when the potion gets used/identified. The cause is that in objects.c, many more descriptions of potions are defined than there are actual potions, but dipping gems in acid creates potions BASED on their description. E.g. dipping a Topaz into acid makes a "Murky" potion, which may only exists as a description. Any attempt to utilize these pseudo potions will always result in a crash.
 : Possible fixes, based on ease;
 # Reduce the number of potion descriptions in objects.c to match the number of actual potions, while retaining all the ones needed for the acid dipping (listed from line 2009 in potion.c).

← Older revision		Revision as of 07:26, 9 August 2014
Line 7:		Line 7:
	* Certain other events can trigger an "obj_is_local" panic which may also cause savegame files to be unrecoverable. Looking at the source of old SLASH'EM versions and certain other variants suggests it has to do with light sources but I currently can't reproduce it...		* Certain other events can trigger an "obj_is_local" panic which may also cause savegame files to be unrecoverable. Looking at the source of old SLASH'EM versions and certain other variants suggests it has to do with light sources but I currently can't reproduce it...
	* Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.		* Some systems seem to have a bug with level-drain attacks that can cause them to instantly kill the character. Again, I can't reproduce it, and the level drain code doesn't seem to have any bugs, but until someone finds out what is causing this, players who are experiencing this bug may want to use items with high magic cancellation and drain resistance.
		+
		+	* Creating a potion via #dip-ping gems into acid will can crash the game when the potion gets used/identified. The cause is that in objects.c, many more decriptions of potions are defined than there are actual potions, but dipping gems in acid creates potions BASED on their Description. E.g. dipping a Topaz into acid makes a "Murky" potion, which may possibly only exists as a description. Any attempt to utilize this pseudo potion will always result in a crash.
		+	: Possible fixes, based on ease;
		+	# Reduce the number of potion descriptions in objects.c to match the number of actual potions, while retaining all the ones needed for the acid dipping (listed from line 2009 in potion.c).
		+	# Alter acid + gem dipping (2009, potion.c) to give set potion effects rather than set potion descriptions, e.g.
		+	;instead of;
		+	<syntaxhighlight lang="C">
		+	case RUBY:
		+	potion_descr = "ruby";
		+	break;
		+	case GARNET:
		+	potion_descr = "pink";
		+	break;
		+	case JASPER:
		+	potion_descr = "purple-red";
		+	break;
		+	</syntaxhighlight>
		+	;use
		+	<syntaxhighlight lang="C">
		+	case RUBY:
		+	return POT_GAIN_ABILITY;
		+	break;
		+	case GARNET:
		+	return POT_RESTORE_ABILITY;
		+	break;
		+	case JASPER:
		+	return POT_HEALING;
		+	break;
		+	</syntaxhighlight>
		+	# add some kind of check to the acid dipping to make sure they are real potions, and to substitute with a default if the potion isn't fully defined, eg if "purple-red" potion doesn't exist, return POT_GAIN_ENERGY
		+	: Frankly option 1 is boring, option 2 is the sensible but goes against the original purpose, and option 3 is probably a bit difficult for me. If you want, I can write up the full conversion for option 2. Just leave a note and I'll check back within 24 hours. --[[Special:Contributions/124.171.109.164\|124.171.109.164]] 07:26, 9 August 2014 (UTC)