The for sake of organization and sanity we need the following:
TASK: CLONE OBJ TO
USE: clone obj 23015 to 47301
PURPOSE: Clones obj 23015 a red headband to the new vnum.
- This will take on all strings, stats, flags, values, and scripts.
- This will make perzing equipment as quick as a few keystrokes
- Can also speed up the obj making process for new zones.
IMM HOUSECLEANING UTILITY: We need to get all perzes as close to a concise inventory listing as possible. Taking existing perzes that may exist in various zones where there were free vnums and move them to a new place. Once "moved" we can then delete (free up) the old placement. E.g., now that obj 47301 is exactly the same as obj 23015, we can clear 23015.
The Big Picture
I would like to see this for mobiles and triggers as well.
For triggers, the purpose would be to make available basic stock scripts for new builders to grab form that include explanations for how it works line-by-line. We could go as far as we'd like in terms of this teachable tool.
For mobiles, it just helps a person speed up the process of building mobiles. We could setup stock mobiles of levels 10, 20, 30, and so on. All of which can be clones from specific IMM zones where we keep these stock placements. Limit what can be cloned from where based on IMM level.
Let's say that the following Zones are IMM zones for these purposes:
473, 599, 980
If you're an IMM of 54 or lower, then you can only clone from the above zones.
This has been rolling around my brain for about a week now, and with a recent revelation of zone dependencies in odd ways, I can't help but feel like we need to try and organize things better.