i also noticed someone has been removing links to items and drop percentages in the classic database on iro wiki. even tho it was flawed before...
combine that with some spawns being bugged or changed in classic (such as a mobster with no re-spawn cool-down,<New! double angeling deviling on juno field map, 20+ alice spawn in kiel factory 1, lmao), and ya.... if you dont play all the time you just dont know......
The problem with iROwiki and its DB is that the Renewal/Classic and OldDB stuff are all incredibly intertwined, when I was doing some work on it I tried to untangle things but as the Renewal people were updating items/making changes it was affecting us too, in some situations I was able to create new classic only entries for a handful of items like EMH/slotted mids. After they moved the forums to their new software I lost my access to the DB area and my request to get it back went unanswered, so I no longer really care enough to manage it.
The main issue with the spawns which I also did is that for Juno they just decided to leave some things in like the permanent Juno spotlight, which causes the double spawned minis. Every request I made to Oda for an updated list of spawns or drops went unanswered and I gave up requesting, having lost access now I really just dont care enough. Beyond that there was never any record of what spawns got changed when/where after Heim stopped doing his HUGE updates like 4 years ago or however long.
Ideally, because of how customised Classic is the GMs would look at creating a way for us to look at these things with a database of their own for drops/spawns and use the existing Classic wiki (not database) for quest/event information, if they need any help deciphering the raw data I'm happy to help, I spent way too long re-arranging and formatting the data to get it from what they had provided into the data that iROwiki uses which is closer to what gets stored in the AEGIS databases than what we were provided.
