Rev 666

[WillowyLady]

Got a little bit of bother using Rev 666, to start with it compiled with one error.

On cranking up server got a boat load of errors.


[Error] DBLoadItems query 'select source,`itemclass`,`name`,`lore`,`idfile`,`id`,`we ight`,`norent`,`nodrop`,`size`,`slots`,`price`,`ic on`,`UNK012`,`UN
K013`,`benefitflag`,`tradeskills`,`cr`,`dr`,`pr`,` mr`,`fr`, Blah Blah etc..

So, tried to source in using NAVICAT - Execute Batch File "utils/items-0.6.0-DR2-0.6.1-DR1-convert.sql"

[Err] 1054 - Unknown column 'unknown021' in 'items'
[Err] alter table items change unknown021 UNK012 int NOT NULL DEFAULT '0';
[Msg] Finished - Unsuccessfully

Any ideas what I may be doing wrong or perhaps missed.

Many thanks.

[cavedude]

Did you really think revision 666 would be problem free? :P Make sure you sourced the item changes in Rev 665.

[WillowyLady]

Did you really think revision 666 would be problem free? :P Make sure you sourced the item changes in Rev 665.

Not with a number like that!:shock:

Just compiled 667 now, so will play with that and go back and see if I missed anything obvious!

[Zeice]

Still getting one build failed in Rev 667 under windows compile
errors here

4>.\client_packet.cpp(2020) : error C2664: 'void Client::Message_StringID(int32,int32,int32)' : cannot convert parameter 2 from 'const char [18]' to 'int32'


4>.\client_mods.cpp(44) : error C2662: 'Client::GetClientVersion' : cannot convert 'this' pointer from 'const Client' to 'Client &'

[WillowyLady]

It's seems to have gone a wee bittie further downhill now, I have hit can't find perl58.dll issues with rev 669 and DB 25.

Using Perl v 5.10.0.1004, its been well behaved for a while:)

I'll sleep on it. Not like I need to grind for 5 years to get a poxy aa~

Things always look better in the morning *grins*

[Dodie]

I can't find this /utils/items-0.6.0-DR2-0.6.1-DR1-convert.sql


i says No files in this directory. You may select another directory from the tree on the left.

when i look up Rev 665

[Dodie]

I found it, but i 300 errors when i source it.


Unknown column and duplicate column errors

[cavedude]

You don't want to source that file! It's ancient and that error should be removed from the EQEmu source. More than likely, you just missed the item update in 665. Either source that in, or use the PEQ database which is already up to date.

[WillowyLady]

Using ver 678, no problems now:0

Issue was caused by sourcing in items-0.6.0-DR2-0.6.1-DR1-convert.sql

There was an error message right after this lot

[Error] DBLoadItems query 'select source,`itemclass`,`name`,`lore`,`idfile`,`id`,`we ight`,`norent`,`nodrop`,`size`,`slots`,`price`,`ic on`,`UNK012`,`UN
K013`,`benefitflag`,`tradeskills`,`cr`,`dr`,`pr`,` mr`,`fr`, Blah Blah etc..

which mentioned to source in items-0.6.0-DR2-0.6.1-DR1-convert.sql

Sourcing that bugger in was the cause of my problem.

All appears to be OK now>)

[cavedude]

I changed the error in the latest revision of the code. Hopefully, that will stop confusing people.

[Dodie]

You don't want to source that file! It's ancient and that error should be removed from the EQEmu source. More than likely, you just missed the item update in 665. Either source that in, or use the PEQ database which is already up to date.



Sorry for being stupid, but could u direct me to the item update in 665? been ages and im new to svn, or if anyone else could... thanks

[cavedude]

EQEmuServer/utils/sql/svn/665_heroic_resists.sql is the file you're looking for.

[Dodie]

It said duplicated entry column or something when i sourced it so i got error again....lol something is wrong

[trevius]

If you got duplicate messages when running that SQL, then the fields should already be there. You should check your items table to make sure you see the new fields for heroic resists such as heroic_pr, heroic_dr etc for all resist types. If those are in your table, then have you tried starting your server to see what happens or what error messages you get?

[Dodie]

If you got duplicate messages when running that SQL, then the fields should already be there. You should check your items table to make sure you see the new fields for heroic resists such as heroic_pr, heroic_dr etc for all resist types. If those are in your table, then have you tried starting your server to see what happens or what error messages you get?

Yes i see them all there.


these are my errors

[06.16. - 23:04:27] Starting Log: logs/eqemu_error_world_2248.log
[06.16. - 23:04:27] DBLoadItems query 'select source,`itemclass`,`name`,`lore`,`idfile`,`id`,`we ight`,`norent`,`nodrop`,`size`,`slots`,`price`,`ic on`,`UNK012`,`UNK013`,`benefitflag`,`tradeskills`, `cr`,`dr`,`pr`,`mr`,`fr`,`astr`,`asta`,`aagi`,`ade x`,`acha`,`aint`,`awis`,`hp`,`mana`,`ac`,`deity`,` skillmodvalue`,`UNK033`,`skillmodtype`,`banedmgrac e`,`banedmgamt`,`banedmgbody`,`magic`,`casttime_`, `reqlevel`,`bardtype`,`bardvalue`,`light`,`delay`, `reclevel`,`recskill`,`elemdmgtype`,`elemdmgamt`,` range`,`damage`,`color`,`classes`,`races`,`UNK054` ,`maxcharges`,`itemtype`,`material`,`sellrate`,`UN K059`,`casttime`,`UNK061`,`procrate`,`combateffect s`,`shielding`,`stunresist`,`strikethrough`,`extra dmgskill`,`extradmgamt`,`spellshield`,`avoidance`, `accuracy`,`charmfileid`,`factionmod1`,`factionmod 2`,`factionmod3`,`factionmod4`,`factionamt1`,`fact ionamt2`,`factionamt3`,`factionamt4`,`charmfile`,` augtype`,`augslot1type`,`augslot1visible`,`augslot 2type`,`augslot2visible`,`augslot3type`,`augslot3v isible`,`augslot4type`,`augslot4visible`,`augslot5 type`,`augslot5visible`,`ldontheme`,`ldonprice`,`l donsold`,`bagtype`,`bagslots`,`bagsize`,`bagwr`,`b ook`,`booktype`,`filename`,`banedmgraceamt`,`augre strict`,`loregroup`,`pendingloreflag`,`artifactfla g`,`summonedflag`,`favor`,`fvnodrop`,`endur`,`dots hielding`,`attack`,`regen`,`manaregen`,`endurancer egen`,`haste`,`damageshield`,`recastdelay`,`recast type`,`guildfavor`,`augdistiller`,`UNK123`,`UNK124 `,`attuneable`,`nopet`,`UNK127`,`pointtype`,`potio nbelt`,`potionbeltslots`,`stacksize`,`notransfer`, `stackable`,`UNK134`,`clickeffect`,`clicktype`,`cl icklevel`,`clicklevel2`,`proceffect`,`proctype`,`p roclevel`,`proclevel2`,`worneffect`,`worntype`,`wo rnlevel`,`wornlevel2`,`focuseffect`,`focustype`,`f ocuslevel`,`focuslevel2`,`scrolleffect`,`scrolltyp e`,`scrolllevel`,`scrolllevel2`,`svcorruption`,`pu rity`,`backstabdmg`,`dsmitigation`,`heroic_str`,`h eroic_int`,`heroic_wis`,`heroic_agi`,`heroic_dex`, `heroic_sta`,`heroic_cha`,`heroic_mr`,`heroic_fr`, `heroic_cr`,`heroic_dr`,`heroic_pr`,`heroic_svcorr up`,`healamt`,`spelldmg`,updated from items order by id', #1054: Unknown column 'augslot1visible' in 'field list'
[06.16. - 23:04:27] If you got boat loads of errors, make sure you sourced: utils/items-0.6.0-DR2-0.6.1-DR1-convert.sql
06.16. - 23:04:27] [WORLD__INIT_ERR] Error: Could not load item data. But ignoring



[06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Aggro:SlowAggroMod'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Aggro:SlowAggroMod
[06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Aggro:IncapacitateAggroMod'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Aggro:IncapacitateAggroMod
[06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Aggro:MovementImpairAggroMod'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Aggro:MovementIm



[06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Combat:HitPerLevelDiff'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Combat:HitPerLevelDiff



06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Combat:MeleeHitChanceMod'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Combat:MeleeHitChanceMod
[06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Combat:PriestHitChanceMod'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Combat:PriestHitChanceMod
[06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Combat:CasterHitChanceMod'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Combat:CasterHitChanceMod
[06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Combat:HeavyAvoidChanceMod'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Combat:HeavyAvoidChanceMod
[06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Combat:ModerateAvoidChanceMod'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Combat:ModerateAvoidChanceMod
[06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Combat:LightAvoidChanceMod'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Combat:LightAvoidChanceMod
[06.16. - 23:04:27] [RULES__ERROR] Unable to find rule 'Combat:UnarmoredAvoidChanceMod'
[06.16. - 23:04:27] [RULES__ERROR] Unable to interpret rule record for Combat:UnarmoredAvoidChanceMod

[trevius]

Many rules have been removed, so you can remove them from your rule_values table if you wish. But, those rule errors don't matter. What does matter is this error:

#1054: Unknown column 'augslot1visible' in 'field list'

It looks like you missed an SQL update from way back when the aug unknown was changed to the new augslot1visible field name.

See if this SQL helps:
/utils/sql/svn/292_augslots.sql

[Dodie]

I tried that one and it sais ERROR Check that column/key exists



and unknown column ' bla bla ' in items

[trevius]

If you sourced in items-0.6.0-DR2-0.6.1-DR1-convert.sql while trying to fix your other issues, that is probably the cause of your current problems. You need to revert back to before you sourced that in if possible.

[Dodie]

Ah, I probably did that. Hmm, I don't really have anything done on the DB, could I just reinstall in some quick way?



Thanks for assisting.

[trevius]

You should just need to download the latest PEQ DB update from their SVN and source it all in again to overwrite everything else you have in there now. Then, you will probably still need to run any SQL updates that came since the last PEQ DB version if it doesn't currently include the Heroic Resists and maybe some other stuff.

[Dodie]

Ok, i will try that.


Thanks

[cavedude]

No, I update the binaries with the DB so it is up to date. In the future, I also do not recommend manually updating the DB. Just wait for me to update it for you. Crossing the SVN update and the PEQ updates can sometimes create incompatibilities.

[WillowyLady]

Sounds a good idea CD!

May I thank you guys for the effort you put in to guiding techophobes like me.

You really put so called "professionals" to deep shame!

*sprinkles angel dust* ack, was bloody caltrops again~

;)

[Dodie]

Ok ill just wait then!

[trevius]

Dodie, you don't have to wait, because the newest binaries are from R669 which means that since the PEQ DB matches that, you will be able to run as soon as you update to the latest PEQ DB release and resource everything.

Also, I wanted to mention that I am in the process of also adding 3 new tables for handling SoF AAs, so now that you guys are finally getting everything added for the items stuff and running again, you will be doing it all again soon for SoF AAs :P Seriously though, the new AA tables shouldn't be nearly as much trouble as the item table stuff though, so don't worry too much about it.

I think the addition of the items table changes as well as the upcoming SoF AA tables will mostly finalize the new table updates that will be required to finish off SoF. At least until new features available in SoF are coded in at all. Once the SoF AA tables go in, we should just need to code in the new item stats and then fill in the SoF AA tables to what they should be and SoF will be pretty-much caught up with Titanium. There will still be a couple minor issues here and there, but IMO, the AA issue is the biggest difference between the clients.

[Dodie]

Ahh, I just resourced everything and it works :D



Thanks for help.