[3.3.5a] .Waypoint and other similar commands never save correctly

[Ghosthopper]

Anyone know why my waypoints never seem to save correctly? Or the scale of my NPC's never stay either?
I'm getting the syntax correct (I believe) with

.waypoint gen 50 50
or I add a 1 just to be safe
.waypoint gen 50 50 1
.waypoint add 1 1
or .waypoint add 1
.waypoint add
but to none prevail

I do tons of work making custom patting instances and than every time the server restarts they are just sitting there chill'n. I'm like bro D:

.mod scale 20 1
Also doesn't work for NPC's and if I change the scale in the database it makes ALL of them huge...well what if I only want ONE huge cow

.npc emote state ID 1

doesn't work either.


SO....anyone know a work around for this?


The strangest part is SOMETIMES the waypoints save O_o


AlterWoW repack 3.3.5a
Navicat is where I update my tables.

ALSO on an unrelated note does anyone know how I would go about swapping repacks without losing all my hard work on custom towns, classes, spells, quests etc?

[Facerolling]

A Repack is effectively the Core compiled for you along with probably a community edition of MySQL. The MySQL server is where your spawns, characters, quests etc. are stored. You can "change repack" or compile your own server and continue to use the MySQL server provided with it.

tl;dr - To change Core and keep custom stuff, use the MySQL server still but change the logon and world servers to your new core ones.

[Ghosthopper]

I'm trying to swap in more custom stuff that I didn't make. I.E New 'fun server' rather than Blizlike. So It's going to add TONS of new object spawns and NPC's
That's still the same thing o_O?

[Confucius]

waypoints probably arent saving because you're not shutting down the server correctly, as with scales when you do that it changes scale for all the npcs with that spawn id iirc. And I think your command for emote is wrong I can't remember it though as I haven't done emu in quiet some time.

As to the repack thing, repacks come in two parts, the core and the database, all your spawns and npc and everything is stored in the database, account names, npc ids ect everything. The core is just what allows you to connect to the world and play in it. It gets all the spawns and stuff from the database. So as long as you use the same database, you can change repacks or compile whatever emu you want and your stuff will stay, but you have to also make sure the core is compatible with your database.

[Ghosthopper]

.server shutdown
If this is wrong than god help me O_O



As for the Core update, I'm not looking to swap cores. I'm looking to ....okay well yes swap cores I suppose. I'm trying to swap from AlterWoW (blizlike) to Norwegian Elite fun server 6. The thing is just updating the core I assume will not actually change anything in my DB and thus will not properly add all the fun Norwegian stuff...and that's the goal is to comine them without losing all my custom gameobjects, nps, etc.

[Confucius]

Well when I did emu I shut down using the console shutdown command, also do .save all before shutting down, I think there was a command to save waypoints as well, I also edited my reply above

[Ghosthopper]

I'll try the console shut down.

.save all is macroed to my shut down.


.waypoint save 1
or .waypoint save Is always used as well. I did a bit of research on google and found a different thread on another forum that said ArcEmu is just broken with waypoints with some cores when using custom gameobjects or NPCs....makes sense I suppose.

[Confucius]

Mmm that could be it, last time I used emu I used custom cores so it worked fine. Arcemu public is pretty buggy sometimes.

A solution could be to use Lua scripts for each npc so they could walk around and even do actions ect.

[Ghosthopper]

Gah I'm lazy and unintelligent. Thanks for the tip with the console shut down ~ will def try that. As for the second thing with custom DB like Norwegian any idea if I can use that core and have all of my custom stuff WITH all of their custom stuff? Or is it one or the other

[stoneharry]

lololol

Sorry but there's no need to do .save all

All the command does is take all online players and save there current status to the database. It automatically does this on every shutdown.

ArcEmu has had buggy waypoints that don't save for quite a while now, sometimes they save, sometimes they don't. I think it's an issue with WhyDB rather than ArcEmu however since when I clean my entire waypoints table it generally works fine.

Scale has never saved. Change it in the database.

[Confucius]

lololol

Sorry but there's no need to do .save all

All the command does is take all online players and save there current status to the database. It automatically does this on every shutdown.

ArcEmu has had buggy waypoints that don't save for quite a while now, sometimes they save, sometimes they don't. I think it's an issue with WhyDB rather than ArcEmu however since when I clean my entire waypoints table it generally works fine.

Scale has never saved. Change it in the database.

D:< I used to have to do .save all a long time ago in antrix and stuff D: meany stone is too good at this stuff

[Ghosthopper]

lololol

Sorry but there's no need to do .save all

All the command does is take all online players and save there current status to the database. It automatically does this on every shutdown.

ArcEmu has had buggy waypoints that don't save for quite a while now, sometimes they save, sometimes they don't. I think it's an issue with WhyDB rather than ArcEmu however since when I clean my entire waypoints table it generally works fine.

Scale has never saved. Change it in the database.

That settles that. It's just bugged. lol

Alright moving on. Any idea about getting a bunch of Norwegian Elite stuff and not losing everything? (assuming the table set up and cores are compatible)

[stoneharry]

Execute both databases into seperate databases, go into the norwegian one, find the data you want, export to SQL, go to your database, execute into there.

Only real way if they didn't provide the SQL updates to default tbh.