PlayerSupport

CoffeeMUD
Administrator                                                  Builder                                                              Player

=CoffeeMUD Builder Information=
Basics	Praetor     Player Support     Commands     Zapper Masks	Advanced	Races     Classes     Abilities     Socials     Scripting
Building	Behaviors     Properties     Areas     Rooms     Exits     Items     Mobs	Systems	Achievements     Crafting     Help Info     Ships     Planes of Existence     Quests     Triumphs

This page is intended for the discussion of HOW to assist players with common 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.

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 USER (or Grinder).
    • If not using an account system, you will need to reset the player's password.

Player seeing weird room information

• Check if the player is under the affects of hallucination, or some other illusions.
• Check if the player is under the affects of Scrying, or some other divination.
• Check if the room the player is in is under the affects of a mirage, or alternate room view.
• Check if the player is affected by the doppleganger bug. Do a WHERE (playername). If there is more than one mob with the player's name (including the player), then GOTO each instance of the player name and verify that it is not a MOB that just shares the player's name. If the mob appears to be an erroneous doppleganger of the player, then inform the player that you need them to logout for a couple of minutes while you correct the issue. Once the player is logged out (or you get tired waiting for a response), use UNLOAD USER (PlayerName) and Save (Y) the player. Then DESTROY (MobName) any mob that appears to be an erroneous doppleganger. Once all dopplegangers are destroyed, the player may log back in. Special NOTE: Do NOT destroy the doppleganger while the player is still online, as this will delete the player!

Player can't find home/clan property/ship

This is especially common for players returning after a long hiatus. The LIST REALESTATE (PlayerName/ClanName) is ideal for this. For players who frequently have an issue with this, recommend they learn the Find Home and Find Ship skills.

Clanship isn't available for use

This issue is particularly troubling if CLANHOMESET, CLANDONATESET, or CLANMORGUESET was used on the clanship.

• 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.
• This issue should be resolved by version 5.9.9.1.

Sluggishness

This may be a stuck thread issues. If it is do the following:

• LIST THREADS ACTIVE
• wait a few seconds
• LIST THREADS ACTIVE
• Figure out which one is hopelessly hung between the two lists, or issue another LIST THREAD ACTIVE
• DESTROY THREAD [threadname]

Breeding Issues

• If a baby refuses to grow up, even with multiple 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.

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.

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.