Buffs dropping at zone

[nannite]

Hello all,
I have a linux eqemu server up and running. I pull the source from git master about 3 weeks ago and just updated the database from here; http://peqtgc.com/releases

We started playing on it a couple of days ago and quickly noticed that all our buffs drop when we zone. We also don't get full health with each ding, but we get full mana.

I've been searching around but haven't found anything yet.

Do I need to pull from a different source branch or do another pull?

Did I use the correct database version?

Anyone have any idea that would cause something like that?

[demonstar55]

You need to source this file https://github.com/EQEmu/Server/blob...uff_update.sql

[nannite]

Thanks for the reply but when I try that it get this:

ERROR 1054 (42S22): Unknown column 'death_save_chance' in 'character_buffs'
ERROR 1054 (42S22): Unknown column 'DeathSaveSuccessChance' in 'merc_buffs'
ERROR 1146 (42S02): Table 'eq.botbuffs' doesn't exist
ERROR 1054 (42S22): Unknown column 'death_save_aa_chance' in 'character_buffs'
ERROR 1054 (42S22): Unknown column 'CasterAARank' in 'merc_buffs'
ERROR 1146 (42S02): Table 'eq.botbuffs' doesn't exist
ERROR 1060 (42S21): Duplicate column name 'caston_y'
ERROR 1060 (42S21): Duplicate column name 'caston_y'
ERROR 1146 (42S02): Table 'eq.botbuffs' doesn't exist
ERROR 1060 (42S21): Duplicate column name 'caston_z'
ERROR 1060 (42S21): Duplicate column name 'caston_z'
ERROR 1146 (42S02): Table 'eq.botbuffs' doesn't exist
ERROR 1060 (42S21): Duplicate column name 'ExtraDIChance'
ERROR 1060 (42S21): Duplicate column name 'ExtraDIChance'
ERROR 1146 (42S02): Table 'eq.botbuffs' doesn't exist
ERROR 1054 (42S22): Unknown column 'not_reflectable' in 'spells_new'

maybe there is another update that is missing?

[sorvani]

Yeah that query needs to be fixed to not attempt things on tables that don't exist such as bots, but that is not your problem. You have the changes in already per your errors there.

Likely your source is prior to the changes. You need to update the source and the DB.

[nannite]

Ahh ok, I'll pull down the latest source and rebuild then.

[nannite]

That did the trick! TYVM

[nannite]

ok well that fixed the zoning buff problem, but now I can't attack mobs and when I try to cast on them I get "Your spell would not have taken hold on your target". Buffs all work though.

[nannite]

Ok updated the source as of today and got todays database release, sourced the drop_system.sql and peqbeta_2014-03-02-02:01.sql but I still have the same issue, I can't attack any mobs with either autoattack or spells.

[demonstar55]

Im assuming you're in a revamped zone that has combat disabled in the database because they're not fully implemented yet

[nannite]

Actually I'm not sure, is North Ro a revamped zone?

[nannite]

Well looks like it is, as well as Common lands. Befallen seems to be working fine, so that must be the issue.

Thanks again!

[sorvani]

Originally Posted by nannite

Ok updated the source as of today and got todays database release, sourced the drop_system.sql and peqbeta_2014-03-02-02:01.sql but I still have the same issue, I can't attack any mobs with either autoattack or spells.

If you have a database dated after the SQL, you do not need the SQL.

Glad you figured it out.

[jcarmony]

I am having same problem, all buffs drop whenever I zone. Using windows emu , and PEQDB peqbeta_2014-06-16-02:01.tar.gz .. I got the latest source released (06/13/2014) and rebuilt it, fresh clean install and still no luck. Also the updates (source/utils/sql/git/required) are up to date (last one being 2014_05_04_SlowMitigationFix.sql) .. So I would assume the peqdb 6-16-14 would be fully updated.

Everything else seems to be working fine. Any help is highly appreciated.

[provocating]

Someone correct me here but I think even if you source in PEQ at a particular date, that does not guarantee you do not need to back date some of the SQL updates. I seem to have run into this before.

[demonstar55]

The issue described here is because they missed an SQL that affects a player table, which the PEQ update doe not over, since it would cause character deletion, so you need to run the right SQL from the updates.