Thanks for wanting to look into this. Here’s the Olemba Cone gameobject entry in the gameobject_template with data8 column filled with questid. I’m not using Navicat anymore. Switched over to Mysql Workbench. First screenshot gameobject_template entry. second screenshot is that of the gameobject_template_addon table for the Olemba Cone.
[ATTACH]2205._xfImport[/ATTACH]
[ATTACH]2207._xfImport[/ATTACH]
[ATTACH]2206._xfImport[/ATTACH]
Gameobject_template_addon is selected on gameobject 182541.
Third screenshot is of gameobject_loot_template
Using the entry in data1 of the gameobject_template table of Olemba cone (screenshot 1) i.e. entry 19372.
Entry 19372 points to Item 25745. This is an Olemba Seed item. However the problem is that I can’t click on the gameobject.
Can you send me your SQL query for the item for both tables I am going to edit the item myself and see where it is not allowing you to be clickable. As soon as you get me the SQL query I am going to write a script that will allow this to be clickable when you are on the quest only.
okay cool thanks I will do that as soon as I compile another updated server, I try to compile a server every week if not sooner depending on the changes made. It gets crazy since I use all the servers, 3.3.5a, 4.3.4 and 7.2.5
Well i have tested it now and every thing works good for me.
You can open the gameobject if you have taked the quest only (I tested it with the horde quest id=9993, alliance is the same 9992), if you havent taken the quest you cant open it.
Here you have the values for it (i didnt change any values, so its trinity original values):
Gameobject_template:
data0=57
data1=19372
data3=1
The rest of data files=0,nothing relevant there
Gameobject_template_addon:
flags=4
The rest=0
Gameobject_loot_template;
entry=19372
questrequired=1
The rest same than you.
I hope this is clear for you so you can fix it. Good luck.
Thanks for testing and helping out. I’ve applied those settings and restarted the trinitycore worldserver. However the Olemba cones are not clickable. I didn’t clear the cache in the client. I’ll try this tonight. If that fails then I’m thinking of rebuilding a new database. I’ve taken the database of dduarte v720 as a basis and then ran the updates. Is that also what you guys have done?
Well i was going to tell you about clearing your cache too. If it doesnt work:
You can truncate the world database, import the world sql file downloaded of trinity and then you run the worldserver.exe so updates get added automatly.And everything should to work good.
Just wondering why you used a different database of trinity instead of trinity one…
I thought so, I’ll do the cache clearing first. If that fails, then I’ll do the truncate and import the original world sql file. The updates that are relevant are only those in the 7.x folder right?
To clarify, I used the Dduarte database. That one is also available by Trinity TDB 720.00 which holds all data until 19-04-2017. I ran updates ontop of that one.
If I start over I can truncate the world database but… what do I do next?
Just turn on run updates when starting the worldserver?
Sorry I have been gone for a while now been really busy with stuff but I did test that out and it didn’t work until I started the database over again and cleared my cache so you might want to think about doing that, I have done a lot of testing lately and so far that is the best solution, I am still trying to work around one thing though so I will post back thanks
Truncate the world database, add the sql file tdb full 720 and turn on run updates automatly in the worldserver.config. Then run the worldserver.exe and everything should to be ok. Dont forget to delete the cache client folder before of starting the wowpatched…exe
Using configuration file E:/Games/WowPrivateServer/Legion/Official Legion 7.2.5/worldserver.conf.
Using SSL version: OpenSSL 1.0.2k 26 Jan 2017 (library: OpenSSL 1.0.1u 22 Sep 2016)
Using Boost version: 1.59.0
Updating Auth database…
>> Auth database is up-to-date! Containing 11 new and 97 archived updates.
Updating Character database…
>> Character database is up-to-date! Containing 5 new and 67 archived updates.
Updating World database…
>> Applying update “2017_04_19_01_world.sql” ‘B1EFAB0’…
mysql: Could not create or access the registry key needed for the MySQL application
to log to the Windows EventLog. Run the application with sufficient
privileges once to create the key, add the key manually, or turn off
logging for that application.
Applying of file ‘F:/Development/TrinityCore/TrinityCore/sql/updates/world/master/2017_04_19_01_world.sql’ to database ‘world’ failed! If you are a user, please pull the latest revision from the repository. Also make sure you have not applied any of the databases with your sql client. You cannot use auto-update system and import sql files from TrinityCore repository with your sql client. If you are a developer, please fix your sql query.
Could not update the World database, see log for details.
Hmm ok, I was able to circumvent the above by applying all the world sql updates from the master branch and then also did that for the hotfix database.
Using configuration file E:/Games/WowPrivateServer/Legion/Official Legion 7.2.5/worldserver.conf.
Using SSL version: OpenSSL 1.0.2k 26 Jan 2017 (library: OpenSSL 1.0.1u 22 Sep 2016)
Using Boost version: 1.59.0
Automatic database updates are disabled for all databases!
Could not prepare statements of the World database, see log for details.
But what log do I access for details…Anyone got experience with this?
Ok, so reinstall mysql then. It’s probably not only the database that got corrupted?
I think I’ll rebuild the project also, since I see that the log has a date of 15-05-2017, but I just pulled and built a new worldserver.exe. Something’s messed up. I’ll start over I think.
1.) complete new git check out, rebuilt VS project with cmake.
2.) compiled new bnetserver, worldserver
3.) extracted all maps, vmaps ,mmaps and dbc/db2
4.) created new instance and hosted on mysql server 5.7
5.) created all databases auth, characters, hotfixes and world
6.) filled it with DDuarte’s TDB 7.2.0.
7.) ran all updates in the updates folder
8.) downloaded and installed Wow Client 7.2.5
9.) created new account and character
10.) tested the quest 9992 Olemba Seeds
11.) The gameobjects are highlighted and drop the items!
So case closed, thanks for helping out and giving pointers to solve this issue. As for me I’m very happy with the new 7.2.5 release.
I’ve discovered that the riding/flying trainers do not work also the profession trainers are not responding to gossips. Is that still expected not to work? I’ve googled the trinitycore issue history and there is mention of that that’s been solved. However my trainer table is empty