Spawn Commands
Posted: Sun Dec 16, 2007 9:09 am
Most of you are probably unaware of this, but I made a change to the emu that will be in version 0.5 affecting commands. Instead of using a underscore to differentiate between separate commands, I implemented John Adams idea of allowing commands to have subcommands like '/spawn add' (add being the subcommand). This makes commands easier to use, but more importantly it gives us the advantage of being able to specify minimum status requirements for each subcommand. If adding your own subcommands remember that all subcommands must have a parent command.
Anyways getting back to the point of this post. Below are a list of the spawn commands that I am implementing in accordance with #3 on my priority list. If you see one that I missed or you feel should be added/changed, let me know ASAP before I am finished with them.
Legend: parameters enclosed in [ ] are mandatory, those enclosed in ( ) are optional
The commands that modify the spawn's information immediately save the new information to the database if the given spawn was previously added to the database.
I didn't feel a need to add a /spawn delete command because once spawns are in the NPC or Object table they don't table up much space and if you use the /spawn remove command to get rid of all of them in your zones they won't be loaded. By not deleting them from your NPC or Objects table you can always re-add them to your zone. Note that names with spaces in them can be set by enclosing the name in quotes (" or '). If you don't, the parser will think the rest of the name is a separate parameter.
Anyways getting back to the point of this post. Below are a list of the spawn commands that I am implementing in accordance with #3 on my priority list. If you see one that I missed or you feel should be added/changed, let me know ASAP before I am finished with them.
Legend: parameters enclosed in [ ] are mandatory, those enclosed in ( ) are optional
Code: Select all
/spawn add [spawn group id] [spawn group name] (percentage)
Saves the Targeted spawn to DB using the given spawn group id. You can specify [i]new[/i] for [spawn group id] to generate a new spawn group id for this spawn. Put quotes around [spawn group name] if it is more than one word. Percentage defaults to 100 if not givenCode: Select all
/spawn create [spawn type] [race type] [class type] [level] [name] (difficulty) (size)
Unlike the original /spawn command which required an NPC or Object ID, this creates a new spawn that can be added to your database. Valid types are Object or NPCCode: Select all
/spawn details
This will list details about the targeted spawnCode: Select all
/spawn equipment [slot] [appearance id] (red) (green) (blue) (highlight red) (highlight green) (highlight blue)
Set the visual textures for a NPC. Slot is 0 to 24
Code: Select all
/spawn list [spawn type] [name]
Name can be a partial portion of the NPC/Object's name.Code: Select all
/spawn set [option] [value]
Sets the option to the selected value for the Targeted spawn. Spawn must be targeted for this to work. Options for this command havent been finalized yet but will include things like name, level, class, race, size, etc. Just about any option that I can think of that affects the display of the mob I will include.Code: Select all
/spawn remove
Removes the Targeted spawn from the zone. Note that this does not delete them from the NPC or Object tables.Code: Select all
/spawn target [spawn type] [id]
This will set the given spawn as targetable. Used to change a spawn if it was set to untargetable.Code: Select all
/spawn [spawn type] [id] (x) (y) (z) (heading) (location)
I modified the spawn command to get rid of the parameters that were obsolete when the /spawn create command was added.I didn't feel a need to add a /spawn delete command because once spawns are in the NPC or Object table they don't table up much space and if you use the /spawn remove command to get rid of all of them in your zones they won't be loaded. By not deleting them from your NPC or Objects table you can always re-add them to your zone. Note that names with spaces in them can be set by enclosing the name in quotes (" or '). If you don't, the parser will think the rest of the name is a separate parameter.