Jump to content
  • 0

[Zero] A Few Small Questions


warmech

Question

After reviewing the server logs for my Zero instance, I've come across a few more seemingly non-issues that I wanted to inquire about.

First:

2013-06-28 19:50:34 Loading Equipment templates...
2013-06-28 19:50:34 ERROR:creature_equip_template table is empty!

2013-06-28 19:50:34 >> Loaded 0 equipment template

After researching the current Zero database issues page on git, I've been unable to find anything mentioning this issue but, at https://github.com/mangos-zero/database-old/issues/36, I've come across an old posting mentioning this. The extent of the discussion there seems to point at items not existing in the version of the game being run, hence an empty table. Not sure how much that applies in my circumstance, but any input would be appreciated.

Second:

2013-06-28 19:50:38 Loading CreatureLinking Data...
2013-06-28 19:50:38 
2013-06-28 19:50:38 >> Loaded creature linking for 55 creature-entries
2013-06-28 19:50:38 >> Table creature_linking is empty.

Again, I kind of presume this is empty by default, but can't be sure. :-[

Third:

2013-06-28 19:50:46 Loading Vendors...
2013-06-28 19:50:46 
2013-06-28 19:50:46 >> Loaded `npc_vendor_template`, table is empty!
2013-06-28 19:50:46 
2013-06-28 19:50:46 >> Loaded 12576 vendor items
2013-06-28 19:50:46 Loading Trainers...
2013-06-28 19:50:46 
2013-06-28 19:50:46 >> Loaded `npc_trainer_template`, table is empty!

Another two empty tables that have names which construe importance, but I can't be sure.

Fourth:

2013-06-28 19:50:48 Loading Localization strings...
2013-06-28 19:50:48 
2013-06-28 19:50:48 >> Loaded 0 creature locale strings. DB table `locales_creature` is empty.
2013-06-28 19:50:48 
2013-06-28 19:50:48 >> Loaded 0 gameobject locale strings. DB table `locales_gameobject` is empty.
2013-06-28 19:50:48 
2013-06-28 19:50:48 >> Loaded 0 Item locale strings. DB table `locales_item` is empty.
2013-06-28 19:50:48 
2013-06-28 19:50:48 >> Loaded 0 Quest locale strings. DB table `locales_quest` is empty.
2013-06-28 19:50:48 
2013-06-28 19:50:48 >> Loaded 0 Quest locale strings. DB table `locales_npc_text` is empty.
2013-06-28 19:50:48 
2013-06-28 19:50:48 >> Loaded 0 PageText locale strings. DB table `locales_page_text` is empty.
2013-06-28 19:50:48 
2013-06-28 19:50:48 >> Loaded 0 gossip_menu_option locale strings. DB table `locales_gossip_menu_option` is empty.
2013-06-28 19:50:48 
2013-06-28 19:50:48 >> Loaded 0 points_of_interest locale strings. DB table `locales_points_of_interest` is empty.
2013-06-28 19:50:48 >>> Localization strings loaded

I'm guessing that these pertain to game localizations and language availability and are empty due to no other localizations being loaded.

Fifth:

2013-06-28 19:50:50 <SD2 ERROR>: Missing `sd2_db_version` information.
2013-06-28 19:50:50 Loading ScriptDev2 Revision [z2676] (*) * * (Win32)

The "sd2_db_version" field in the MySQL table for scriptdev2 is, in fact, empty here. I followed all the steps properly to install the database, but still get this error. Not important, I suppose but, again, any insight is welcome. :)

Sixth (and finally):

2013-06-28 19:50:50 <SD2 ERROR>: No script found for ScriptName 'npc_sergeant_bly'.
2013-06-28 19:50:50 <SD2 ERROR>: No script found for ScriptName 'npc_weegli_blastfuse'.

All my googling has led to nowhere on this one, unfortunately. I'm running the most recent version of all builds, so I'm not sure why these should be missing unless they were nerfed characters in Vanilla, but can be interacted with in TBC or later.

Sorry for the text dump here; none of these are probably anywhere near catastrophic. I just want to make sure I've got everything done the right way - no half measures. Thanks again for any input anyone has to offer on these. You guys keep a great community! :)

Link to comment
Share on other sites

6 answers to this question

Recommended Posts

Fifth:

2013-06-28 19:50:50 <SD2 ERROR>: Missing `sd2_db_version` information.
2013-06-28 19:50:50 Loading ScriptDev2 Revision [z2676] (*) * * (Win32)

The "sd2_db_version" field in the MySQL table for scriptdev2 is, in fact, empty here. I followed all the steps properly to install the database, but still get this error. Not important, I suppose but, again, any insight is welcome. :)

Sixth (and finally):

2013-06-28 19:50:50 <SD2 ERROR>: No script found for ScriptName 'npc_sergeant_bly'.
2013-06-28 19:50:50 <SD2 ERROR>: No script found for ScriptName 'npc_weegli_blastfuse'.

All my googling has led to nowhere on this one, unfortunately. I'm running the most recent version of all builds, so I'm not sure why these should be missing unless they were nerfed characters in Vanilla, but can be interacted with in TBC or later.

The table "sd2_db_version" should contain ScriptDev2 (for MaNGOS classic z2383+)

Make sure you run "git pull" on the folder scripts and server before doing the below.

scirpts folder should be located - server\src\bindings\scripts

server being the root folder.

In server\src\bindings

You have CMakeLists.txt

Edit it these lines are like:

# add_subdirectory(universal)
add_subdirectory(scripts)

Go to the root and load the core in your compiler and rebuild

Once build complete go to server\src\bindings\scripts

Load the SLN again for your compiler and rebuild scripts

All files are compiled now.

Database wise you need to run from server\src\bindings\scripts\sql

mangos_scriptname_clear.sql

mangos_scriptname_full.sql

scriptdev2_create_structure_mysql.sql

scriptdev2_script_full.sql

On our live realms we have our scriptdev tables in our main mangos database.

When re-compiling the core you will need to run from server\sql\updates

z2424_sxxxx_xxxxx_01_realm_db_version.sql

This is due to the latest change Antz made to the core / realmd

Those other errors I would not worry about, Our database is worked on daily at the moment by developers here so I'm sure they would know about those anyway but thanks for reporting them and if there is a problem with the other errors I'm sure a developer will be along later this morning to say :)

Link to comment
Share on other sites

Personally I switch on the log colours which makes things much clearer.

Basically anything in Red is potentially a problem. On my system as least only one entry shows as red.

2013-06-28 19:50:34 Loading Equipment templates...
2013-06-28 19:50:34 ERROR:creature_equip_template table is empty!

2013-06-28 19:50:34 >> Loaded 0 equipment template

And that is not really an error.

if you want to eliminate that message for now, open creature_equip_template and enter 1,1,1,1 in each of the fields

Link to comment
Share on other sites

Personally I switch on the log colours which makes things much clearer.

Done, and boy does that make things clearer!

2013-06-28 19:50:34 Loading Equipment templates...
2013-06-28 19:50:34 ERROR:creature_equip_template table is empty!

2013-06-28 19:50:34 >> Loaded 0 equipment template

And that is not really an error.

if you want to eliminate that message for now, open creature_equip_template and enter 1,1,1,1 in each of the fields

Not a concern for me, since you cleared that up; thanks a bunch!

The table "sd2_db_version" should contain ScriptDev2 (for MaNGOS classic z2383+)

Make sure you run "git pull" on the folder scripts and server before doing the below.

scirpts folder should be located - server\src\bindings\scripts

server being the root folder.

In server\src\bindings

You have CMakeLists.txt

Edit it these lines are like:

# add_subdirectory(universal)
add_subdirectory(scripts)

Go to the root and load the core in your compiler and rebuild

Once build complete go to server\src\bindings\scripts

Load the SLN again for your compiler and rebuild scripts

All files are compiled now.

Database wise you need to run from server\src\bindings\scripts\sql

mangos_scriptname_clear.sql

mangos_scriptname_full.sql

scriptdev2_create_structure_mysql.sql

scriptdev2_script_full.sql

On our live realms we have our scriptdev tables in our main mangos database.

When re-compiling the core you will need to run from server\sql\updates

z2424_sxxxx_xxxxx_01_realm_db_version.sql

This is due to the latest change Antz made to the core / realmd

Didn't even know "$git pull" was a thing; followed all of your instructions and everything looks to be on target! ;D

Those other errors I would not worry about, Our database is worked on daily at the moment by developers here so I'm sure they would know about those anyway but thanks for reporting them and if there is a problem with the other errors I'm sure a developer will be along later this morning to say :)

Thanks again for the awesome support! I can't commend you guys enough for your level of dedication to this. Thanks to y'all, everything is running fine and I've been having a blast. :) Keep up the excellent work, good sirs and ladies!

PS - If I do encounter an issue that doesn't look like it's been addressed, is there a proper error reporting protocol to use for submitting a bug? I'd hate to make clutter if there's a right way to go about doing things.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use