Deprecated Darkstar fourms

I recently updated everything via svn. I then rebuilt Login, Map and search which updated with 0 errors. Login & Search open fine, but when I try to open the map server it gets to loading zones then crashes. I've messed around with it a bit, but I can't figure out the cause anyone else have this issue?

reran all the sql files?

I did all, but the account/char ones. think thats the problem?

hmm... probably not, if it's crashing on zones. what kind of crash is it? not responding? good idea would be to launch it from visual studio (f5) so that when it crashes you can see why

I changed to a different revision and it works now as far as booting, but when my connect server goes to pass it off to map connect crashed and i'm dc/ed. I'm trying to learn cause I would love to contribute to this one day. XI was my favorite MMO for years, but I feel abyssea ruined it. anyways ty for the help kj hopefully I can fix the connect/map problem i'm getting.

I'm having a similar issue, updated the server using DSPupdater and it mentioned 3 .sql databases that were not updated due to timeouts or something of the sort. Unfortunately the only one I can remember was the triggers.sql, the other 2 I want to say were mob pools or groups, I'm really not sure. Now when loading the map server it gets to zones and then says there is a DB error- Unknown column 'pet_mobid' in 'field list'. I've manually updated all but the char sql's but I'm still getting this error and am not seeing this column anywhere.

Edit - Tried to update again to an earlier revision but I was met with a whole slew of new errors. Now my settings.lua is apparently an altered and conflicting file, yet it hasn't been touched, but is causing me to be unable to update server any further.

DSPUpdater hasn't been maintained in a while and is not officially supported. We have to assume it no longer works.

It appears to be working after allowing it to create a new settings.lua and updating to r3480, it has to be not liking something to do with adding pet names to the mysql database but I'm still just not seeing where there should or should not be the table that was causing the issue. If DSP isn't the preferred method of updating currently, what is?

megazraff wrote:If DSP isn't the preferred method of updating currently, what is?

rebuilding and rerunning the sql files manually - usually through navicat