Quote:
|
Originally Posted by sotonin
lol.
you dont understand what #npcspawn create does obviously.
it creates a DUPLICATE of whatever npc you use it on to start.
So if you use it on a orc pawn it doesnt make that orc pawn spawn there, if you use it often it will clutter up your DB with a crapload of npctypes
#npcspawn create is for taking a #spawn'ed creature (which might i add they suck by default youd have to manually edit runspeed walkspeed etc in db before they can even move. Wish there was a more detailed #spawn command at our disposal.
#npcspawn add takes an existing npctype that was summoned with #npctypespawn and adds a new spawn record for it.
#npcspawn update is supposed to take a mob that already has a spawn point in place and UPDATE it with the new moved location. This command does NOT work though. =\
|
Yea it does make a mess, but so far that is the only way I see to do it. Despite what many say, there is not alot of rock solid info on working these emu's. Half the stickies and tutorials are for older versions of the emu and don't work anymore. That is the main problem I had setting up my database. There is like 3 stickies out there all telling you to use different databases. None of them tell you that you need to do the AC fix either, which was a major problem for me.
Hybrid Mode
