Leaderboard

Hi Codeman, 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. 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. Any ideas based on these screenshots?

As outlined in #20103, we're currently making a concerted push for blizzlike instance spawn behavior. As part of this, every instance in the 3.3.5 client needs to have all of its spawns mapped to the corresponding instance boss that causes that group to no longer spawn once defeated. Luckily, we have a tool to help with this. Extract the attached archive into your Interface/AddOns directory, then log onto a 3.3.5 core running commit fcd6fe0 (or newer). Move yourself into the instance you want to map, then invoke /spawngroup to bring up the mapper panel. Use the green plus icon to create one spawn group for each boss in the instance. If there are groups with complex conditions, like "only spawns if any of X, Y and Z are alive", create a separate group for each of them. Scroll down (shift+mouse wheel to scroll faster) and name each of the newly created groups (right-click the respective header). Names should be representative, but have only descriptive value (no need to match the boss name exactly, for example). Start assigning groups to entries and spawns in the "Unassigned" category. Pay attention to detail - not all creatures of the same entry are necessarily assigned to a specific boss. Click on an entry to expand it into a list of its spawn points. Each spawn point can be individually assigned to a group. Click on a spawn point to teleport to it. You can combine this with having the world map open to quickly map disjoint spawn points. Once you are done, click on "Export SQL" to generate a complete instance spawn group script for the instance, then post it here. Because mistakes happen, I'd like at least two, preferably three, copies of each data set, from different people. To find out which instances still need data, take a look at this issue on the tracker - contributions may be posted either there or in this thread. (PS: Feel free to take breaks. The mapper stores any mappings you've already made and will reload them when you bring the panel up again, including across sessions [assuming you log out normally - don't force kill the client.]) (PPS: Invoke /spawngroup while outside an instance at your own peril - it's probably gonna freeze your client for a bit. Lots of spawns there.)

The wow client for the latest MacOS (Sierra 10.12+) is really buggy, due to the internal certificate and the binary had to be modified so Mac would accept it. For this very reason Mac doesn't handle running old software well, and for obvious reasons Blizz is not going to issue an updated client to run Wrath . Your best bet would be to load Wine and install the windows version of enUS. I do however have an official 3.3.5a Mac client, but you have to jump through alot of hoops to get it to work. If you are running a desktop mac, then you might be lucky not to have video problems with it. However, I run the Mac client on my Macbook Pro 15" and the video display wont go higher than 1024x768. PM me if you really want the Mac version, but just remember you have been warned!

Really it is kind of nice that legion moved over to db2 because now the ID's that were being used in item_template can now be used because the way and format data is handled now. item_sparse is just another new way to handle ID's in a different way instead of in MySQL database it is handled in client database instead so ID's can start at one and be handled differently.

If I made something for Legion I wouldn't port anything over unless I had the same framework but I would make something new for an item creator and I don't know why you guys are having an issue with stats they work just fine for me I have tons of intellect and stamina on my items for testing. Are you guys sure you are using the right fields for item creating, maybe I should just make a simple application for item creating so there is no confusion.

In the legion you add items now in the hotfixes database which is item, item_sparse same if it was in the world database but it is in the hotfixes database now.

This isn't the Holiday Inn the last time I checked lol

Yeah scripts are broken right now that is why you are getting compile error linking

Have you tried switching the data over to that field because I think I might know why it is not working for you could you take screen shots and send them to me because I would really like to figure out why this is not working for you. Be careful using navicat because it is not something trinitycore wants users using when it comes to statements and running queries because the way it handles that data sometimes and formats.