The way it's currently set up unfortunately that's not something we can control right now. All the data is currently being held in one big table and identified by a column specifying version and each of the three php pages (renewal, pre-re and classic) pulling data and sorting it based on version. There's even a common pool identifier which like 70% of items are under and that makes them show up in all three pages, making any changes to their description require duplication of the item in a lot of cases. It's possible that I can get it to exclude all items that fall under the Renewal version type from searches/dropdowns but I'll probably need some time to test it so make sure I dont break anything/everything.
It's really elaborate and -_-ty, but it's mostly above my head and I'm trying not to break stuff. I already spoke to Jaye and a lot of the Renewal items they've been adding wont be actually openable, but they still show up in searches and the drop downs just end up like you said "Item wasnt found in the database".
I've made a start on adding some of the items we've been missing and have a (quite large) list of more, but I've been hesitant to add things that dont exist in fear of creating itemid duplicates with renewal (not sure if everything is unique across both servers or not). It's very rough going adding them one at a time and possibly asking Jaye if we can get her tool to add things for Classic would make it waaaaaaaaay more realistic. The problem is there's quite a few items with different descriptions/uses between Classic/pre-re/renewal for example here's the Rideword hat:
They're different in all three versions, the Renewal version has its own description and is fine. But the Classic DB is pulling from the common pool that contains "everything" and from memory doesnt even have its own specific version for item descriptions (whereas it does for spawns/drops etc), you'd have to add it to the php and then you need to start to ignore a bunch of things from the common pool or just completely duplicate all the entries and specify them to be Classic only. It's somewhat hard to explain but its quite a mess.
As for the drops it's not an easy one to fix, if you want rough estimates you can set the server rates under Main -> Settings. But any of the custom changes will not be added right now for a few reasons. Mostly, the GMs are not giving out specific data, they're using "Rare" and "Common" and "Very very very rare" which are vague as heck. I've put a lot of thought into how to display those and these are the options I've been looking at:
Change everything (use the data the GMs have provided and update the entire database using their descriptors/drop ranges)
- Ranges, just convert their descriptions and have every item just list their percentage ranges eg Jellopy 50-100%
- GM Descriptions eg Jellopy Common (maybe include the range afterwards or a legend else on the page)
Change only what's different from our existing data (so that we maintain more accurate data for anything that hasnt been changed yet)
- Use any of the two options above
- Just put down ?? for anything that's different
The ranges the GMs have given us are pretty huge (and really dumb) and there's so many random modifiers on the server it's hard to know what to tell people is accurate. Ideally we'd get data that has already had base rates (and the card double drop) factored in allowing people to do their own math for VIP/Gum/anything else. But I really have no idea about too much of it.
There's also the fact that doing any of those options is an ENORMOUS departure from what we've been used to, the game is so old and datamined that we have data for almost everything even down to monster skills, when and how they use them etc. Going from those very clear and specific drop rates to ranges or vague descriptors is a significant step back and I dont really want to make such a big change honestly. I was going to modify a few monsters to show some examples when we finally got better data from the GMs (the data they gave us last didnt contain itemIDs so it was somewhat hard to link the drops with the DB itself, I do think I've found a solution to that, the data is just really out of date right now) to show people how weird it could look.
So that ended up being a lot of words, there's a lot of random weird/annoying stuff with the DB. It's something I've been working on a little bit. I managed to get the spawns working, but the drops and items are another thing entirely. If anyone is interested in looking into it I recommend they send Blue and/or Xellie a PM and ask for access to the Database section of the irowiki forums, I've got a post there of my discoveries and changes.
Edit: So I had a look and it was worse than I thought, however I think I've figured it out. I changed the http://db.irowiki.or...ssic/item-info/ page and it should no longer show Renewal items in the drop down boxes. I'm going to have a look at the search results page after i have some lunch. If you spot anything that doesnt belong please let me know. There will probably be some items that are incorrectly versioned from before the current push to update the Renewal db and they can be fixed.
Edited by Themes, 15 May 2015 - 02:46 PM.
