Sorting out Nuked PCs

[GoogleCodeExporter]

Provide a trigger for games to use to reset the SOURCE on jobs. If the
source list contains 1 PC dbref and that PC is nuked, then the SOURCE
should point to the +jobs owner. If the SOURCE is >1 PC, then just remove
the nuked PC.

Original issue reported on code.google.com by grey...@gmail.com on 2 Oct 2006 at 8:01

[GoogleCodeExporter]

We need a universal TRIG_CLEAN trigger - it will wipe a DB# out of the system 
(from 
SOURCE to headers, etc), and can be triggered by the game's autonuke code.

Original comment by Fleety...@gmail.com on 24 Oct 2007 at 1:22

[GoogleCodeExporter]

Grey's previous issue (same issue, really, moving old comments and closing 
previous 
issue):

1. Create a TPS or RP job using the default Summary
2. Add a PC to one of the player/staff lists
3. The player is idlenuked.
4. You can no longer remove that player/dbref from the list, since the
object is no longer a player type.

Something will need to be done to manage the dbrefs or allow staff to clean
out non-player dbrefs from the list. 

Original comment by Fleety...@gmail.com on 24 Oct 2007 at 1:26

• Changed title: Sorting out Nuked PCs
• Added labels: Priority-High
• Removed labels: Priority-Low

[GoogleCodeExporter]

Reported by grey419, Oct 02, 2006 
Provide a trigger for games to use with their nuker. This would clear nuked
PCs from any tags lists.

This is a bug, as the possibility exists for a PC to be nuked, then a new
PC created with the same dbref to now have access through the tags to that job.

Original comment by Fleety...@gmail.com on 24 Oct 2007 at 1:27

[GoogleCodeExporter]

Original comment by grey...@gmail.com on 29 Oct 2007 at 4:24

• Added labels: Milestone-Release5.2

[GoogleCodeExporter]

Fixed in r54

Original comment by widdis@gmail.com on 11 Dec 2009 at 7:31

• Changed state: Fixed