PlayerSupport - Revision history

Loki at 19:21, 27 June 2023

2023-06-27T19:21:52Z

← Older revision		Revision as of 19:21, 27 June 2023
Line 49:		Line 49:

	In order to delete the duplicate items, run the script /resources/progs/users/zac/dedupallroomitems.js. The default is 100 copies of a single item before it deletes them, but you can specify the threshold in arguments.		In order to delete the duplicate items, run the script /resources/progs/users/zac/dedupallroomitems.js. The default is 100 copies of a single item before it deletes them, but you can specify the threshold in arguments.

			==Changing a Player's Name==
			If you find yourself needing to change a player's name to a new name:
			*Verify that name isn't in use first (check all player names on all connected ports).
			*MODIFY USER (playername)
			*Enter new name
			All bank accounts, player account information, and owned property will change to the new name. Any zappermasks (such as on a spell_boomerang or certain bind-on-pickup equipment) will not be changed to the new name, and must be handled on a case-by-case basis.
			*I don't know what will happen to heritage information, such as children mobs.

			An alternative would be to provide the player with a TITLE of the new name, instead. This creates its own issues, such as TELL not working on the title name.

Loki: /* Player stuck in a deleted room */

2022-02-11T12:25:00Z

Player stuck in a deleted room

← Older revision		Revision as of 12:25, 11 February 2022
Line 11:		Line 11:
	**[[DESTROY(Builder)\|DESTROY]] the character.		**[[DESTROY(Builder)\|DESTROY]] the character.
	**[[IMPORT(Builder)\|IMPORT]] the character from the verified copy of the player.		**[[IMPORT(Builder)\|IMPORT]] the character from the verified copy of the player.
	***If using an account system, you will need to reattach the player to the account using [[MODIFY(Builder)\|MODIFY]] ~~PLAYER~~ (or Grinder).		***If using an account system, you will need to reattach the player to the account using [[MODIFY(Builder)\|MODIFY]] USER (or Grinder).
	***If not using an account system, you will need to reset the player's password.		***If not using an account system, you will need to reset the player's password.

Loki: /* Player stuck in a deleted room */

2022-02-11T12:24:08Z

Player stuck in a deleted room

← Older revision		Revision as of 12:24, 11 February 2022
Line 7:		Line 7:
	==Player stuck in a deleted room==		==Player stuck in a deleted room==
	*If a character was located in a room deleted by a builder, they will be unable to log in. In order to recover the player:		*If a character was located in a room deleted by a builder, they will be unable to log in. In order to recover the player:
	**Use the [[EXPORT]] command to create a copy of the player.		**Use the [[EXPORT(Builder)\|EXPORT]] command to create a copy of the player.
	***Save the file and review it to ensure you have a good character backup before proceeding.		***Save the file and review it to ensure you have a good character backup before proceeding.
	**[[DESTROY]] the character.		**[[DESTROY(Builder)\|DESTROY]] the character.
	**[[IMPORT]] the character from the verified copy of the player.		**[[IMPORT(Builder)\|IMPORT]] the character from the verified copy of the player.
	***If using an account system, you will need to reattach the player to the account using [[MODIFY]] PLAYER (or Grinder).		***If using an account system, you will need to reattach the player to the account using [[MODIFY(Builder)\|MODIFY]] PLAYER (or Grinder).
	***If not using an account system, you will need to reset the player's password.		***If not using an account system, you will need to reset the player's password.

Loki at 12:22, 11 February 2022

2022-02-11T12:22:47Z

← Older revision		Revision as of 12:22, 11 February 2022
Line 4:		Line 4:
	==Log in issues==		==Log in issues==
	*If a character cannot log in, and their ACCOUNT screen shows that their character is a level 0 STDMOB, then we have a doppleganger bug. To solve, ask the player to remain offline until you can correct it. Search the world with a WHERE (PlayerName) command. If the player name appears, GOTO each instance of the player name, verify that it is not a MOB that just shares the player's name, and DESTROY (MobName) if the mob is an erroneous doppleganger of the player. Once all dopplegangers are destroyed, do an UNLOAD (player name), and select YES for the save prompt. The player should be able to log in correctly.		*If a character cannot log in, and their ACCOUNT screen shows that their character is a level 0 STDMOB, then we have a doppleganger bug. To solve, ask the player to remain offline until you can correct it. Search the world with a WHERE (PlayerName) command. If the player name appears, GOTO each instance of the player name, verify that it is not a MOB that just shares the player's name, and DESTROY (MobName) if the mob is an erroneous doppleganger of the player. Once all dopplegangers are destroyed, do an UNLOAD (player name), and select YES for the save prompt. The player should be able to log in correctly.

			==Player stuck in a deleted room==
			*If a character was located in a room deleted by a builder, they will be unable to log in. In order to recover the player:
			**Use the [[EXPORT]] command to create a copy of the player.
			***Save the file and review it to ensure you have a good character backup before proceeding.
			**[[DESTROY]] the character.
			**[[IMPORT]] the character from the verified copy of the player.
			***If using an account system, you will need to reattach the player to the account using [[MODIFY]] PLAYER (or Grinder).
			***If not using an account system, you will need to reset the player's password.

	==Player seeing weird room information==		==Player seeing weird room information==

Loki at 18:09, 28 October 2020

2020-10-28T18:09:12Z

← Older revision		Revision as of 18:09, 28 October 2020
Line 35:		Line 35:
	*Second, check the area to make sure it's parent (and parent's parent, etc) area exists.		*Second, check the area to make sure it's parent (and parent's parent, etc) area exists.
	**If you rename a parent area, the old parent area name will remain as a parent area to the children, in addition to the new parent area's name.		**If you rename a parent area, the old parent area name will remain as a parent area to the children, in addition to the new parent area's name.

			==Item Duplications in Player-owned property==
			For some reason, there appears to be an imperious curse that randomly occurs, causing items in player rooms to duplicate.

			In order to delete the duplicate items, run the script /resources/progs/users/zac/dedupallroomitems.js. The default is 100 copies of a single item before it deletes them, but you can specify the threshold in arguments.

Loki at 15:29, 16 April 2020

2020-04-16T15:29:22Z

← Older revision		Revision as of 15:29, 16 April 2020
Line 30:		Line 30:
	==Breeding Issues==		==Breeding Issues==
	*If a baby refuses to grow up, even with multiple [[Chant_SpeedAging\|Speed Agings]], then, using the command line, delete the child's prop_safepet and age properties. Finish out your edit. Reedit the mob and add in prop_safepet and age(123456).		*If a baby refuses to grow up, even with multiple [[Chant_SpeedAging\|Speed Agings]], then, using the command line, delete the child's prop_safepet and age properties. Finish out your edit. Reedit the mob and add in prop_safepet and age(123456).

			==Can't Enter an Area==
			*First, check to see if there are any Prop_ReqEntry, Prop_ReqLevel or other property on the area, exit, and room the players is trying to use.
			*Second, check the area to make sure it's parent (and parent's parent, etc) area exists.
			**If you rename a parent area, the old parent area name will remain as a parent area to the children, in addition to the new parent area's name.

Loki at 15:28, 16 April 2020

2020-04-16T15:28:28Z

← Older revision		Revision as of 15:28, 16 April 2020
Line 30:		Line 30:
	==Breeding Issues==		==Breeding Issues==
	*If a baby refuses to grow up, even with multiple [[Chant_SpeedAging\|Speed Agings]], then, using the command line, delete the child's prop_safepet and age properties. Finish out your edit. Reedit the mob and add in prop_safepet and age(123456).		*If a baby refuses to grow up, even with multiple [[Chant_SpeedAging\|Speed Agings]], then, using the command line, delete the child's prop_safepet and age properties. Finish out your edit. Reedit the mob and add in prop_safepet and age(123456).

	~~==Can't Enter an Area==~~
	*First, check to see if there are any Prop_ReqEntry, Prop_ReqLevel or other property on the area, exit, and room the players is trying to use.
	*Second, check the area to make sure it's parent (and parent's parent, etc) area exists.
	**If you rename a parent area, the old parent area name will remain as a parent area to the children, in addition to the new parent area's name.

Loki at 15:26, 16 April 2020

2020-04-16T15:26:50Z

← Older revision		Revision as of 15:26, 16 April 2020
Line 30:		Line 30:
	==Breeding Issues==		==Breeding Issues==
	*If a baby refuses to grow up, even with multiple [[Chant_SpeedAging\|Speed Agings]], then, using the command line, delete the child's prop_safepet and age properties. Finish out your edit. Reedit the mob and add in prop_safepet and age(123456).		*If a baby refuses to grow up, even with multiple [[Chant_SpeedAging\|Speed Agings]], then, using the command line, delete the child's prop_safepet and age properties. Finish out your edit. Reedit the mob and add in prop_safepet and age(123456).

			==Can't Enter an Area==
			*First, check to see if there are any Prop_ReqEntry, Prop_ReqLevel or other property on the area, exit, and room the players is trying to use.
			*Second, check the area to make sure it's parent (and parent's parent, etc) area exists.
			**If you rename a parent area, the old parent area name will remain as a parent area to the children, in addition to the new parent area's name.

Loki: /* Clanship isn't available for use */

2020-03-03T15:46:48Z

Clanship isn't available for use

← Older revision		Revision as of 15:46, 3 March 2020
Line 18:		Line 18:
	*Attempt to determine who originally purchased the clanship. I normally ask the player, or go through the officer roster. Once you know (or start guessing at) the purchaser, do an AS (PlayerName) SCORE to get that player to load into the game, thereby loading their ship into the game.		*Attempt to determine who originally purchased the clanship. I normally ask the player, or go through the officer roster. Once you know (or start guessing at) the purchaser, do an AS (PlayerName) SCORE to get that player to load into the game, thereby loading their ship into the game.
	*Recommend that players log out while still on their clanship to prevent this from happening. A player on their clanship will cause it to load regardless of who the original purchaser was.		*Recommend that players log out while still on their clanship to prevent this from happening. A player on their clanship will cause it to load regardless of who the original purchaser was.
			*This issue should be resolved by version 5.9.9.1.

	==Sluggishness==		==Sluggishness==

Loki: /* Sluggishness */

2019-08-13T02:08:10Z

Sluggishness

← Older revision		Revision as of 02:08, 13 August 2019
Line 21:		Line 21:
	==Sluggishness==		==Sluggishness==
	This may be a stuck thread issues. If it is do the following:		This may be a stuck thread issues. If it is do the following:
	*LIST ~~THREAD~~ ACTIVE		*LIST THREADS ACTIVE
	*wait a few seconds		*wait a few seconds
	*LIST ~~THREAD~~ ACTIVE		*LIST THREADS ACTIVE
	*Figure out which one is hopelessly hung between the two lists, or issue another LIST THREAD ACTIVE		*Figure out which one is hopelessly hung between the two lists, or issue another LIST THREAD ACTIVE
	*DESTROY THREAD [threadname]		*DESTROY THREAD [threadname]