Hey Royallers , Every time I come back to the game I notice that Nexon has taken down whatever wiki I was using last time. I'm a software engineer by day, so I figured I'd just build one with a twist. Meet Scrolled It's an offline, trademark-free, copyright-free "Mushroom Game" wiki that you assemble yourself. Point it at your local game data files, wait a minute or so, and it builds a fully searchable wiki for your exact version of the game: items, equips, weapons, mobs, NPCs, maps, and quests, all cross-linked. Your files, your machine The trick is that your files never leave your computer. Parsing, searching, and browsing all of it happens locally and works offline once loaded. Nothing copyrighted ever sits on a server, so there's nothing for anyone to take down. And because the wiki lives on your machine once it's built, it keeps working even if the site goes away tomorrow. The code is also open-sourced under a permissive license, so you can download it, modify it, and host your own. What's in it Command palette with a tiny query language. Type mobs level:50-70 boss:true and it takes you straight to the filtered list. Works the same for items, equips, quests, and the rest. Map viewer. Toggleable layers for NPCs, mob spawns, and portals. Hover any icon for a stat preview, click through to its detail page. Collections. Bookmark folders ("Funded HP wash route", "Zak prequest checklist", whatever) you can export/import as a small JSON file to share with a friend or a guild. Backup and Share. After creating your wiki, export a backup that contains the whole indexed wiki and all of your personalized data. Send this to your other devices or share it with friends. Quest Chains. Find and follow chains of quests, understand all of the requirements to unlocking all content. Quality of life. Light/dark mode with customisable colours, full keyboard navigation, and it runs fine on a laptop in airplane mode after the first load. Try it App: https://scrolled.dev/ Source: https://github.com/RedbackThomson/Scrolled Feedback wanted You're the first group to see it, so I'd love feedback of any papercuts, missing fields you expected to find, mob/item lookups that look wrong or weird, anything at all. Code and issues live on GitHub. I'm also happy to chat over Discord DMs (redbackthomson) or right here on this thread. Heads up Scrolled is in Early alpha. The data model can still change between versions and break your saved library backup. Re-parse if that happens; nothing in your game files is at risk. Cheers, Redback Spoiler: More Screenshots
just started using it and seems like a good tool so far. layout is clean and easy to use it seems that in the files theres a lot of data that isnt actually active in the game. would be good if there was a way to filter out all the unnecessary stuff that doesnt actually apply to royals also it would be nice if the database was more "complete". eg if you search white scroll the tool doesnt show that its obtainable from nlc gach. likewise if you search gach, you cant see a list of drops. i dont know how easy or difficult this would be to achieve from a technical standpoint, but if were going to treat this as an all in one royals db then i would think that kind of information is what people would look for in completeness. edit: splitting accessories into their separate categories would be nice too
again, forgive the technical ignorance but how can something thats in the game not be in the game files? when gachapon gives an item out it has to rely on a loot table thats stored somewhere. if not the game files then where?
Essentially how this works is that the game client will send a network packet to the server saying "User <username> is attempting to use the Gachapon in Henesys". Then the server will check you have a Gachapon ticket, picks a random Gachapon reward for the Henesys machine from its list of rewards, and then sends back a network packet saying "Remove the Gachapon ticket from their inventory" and another saying "Add the reward to their inventory". So the client never knows what rewards are available, it just knows to communicate with the server when the user interacts with Gachapon. This is true for a lot of different interactions in MapleStory - like PQ stage requirements, boss mechanics, some quest requirements. Since each of these is defined by the server we can't infer the information from the game files and we also can't predict what the result will be because the server may update at any time, independently of the game files, and change its behaviour.
I actually think this is a really good idea. I'd like to figure out an easy way to do that. "Unnecessary" may refer to things that simply are not available in this version of the game, but are still in the game files - like the korean quest chains and some of the equips that have no drop chance from any mob. I don't think users would want to go through and manually find all of these though, so maybe we need an automated solution. I'm struggling to think of what criteria some automated system would use to determine what is useful/relevant to MapleRoyals That's a great idea too!
That's very difficult to do with server-side information not being available. For example, there's some gach only scrolls. How would those be handled? Or multiple VL bodies/bosses like that in general, how do we know which need to be kept and which don't? I believe the old royals.wiki tried to do this (might have been manual removal by the author tho) and accidentally removed some things that did exist in the game.
Yeah unless we can come up with a decent solution for doing this safely, I would prefer to not remove any information. It would be a terrible experience if things were just missing for no explainable reason.
Great callout. Looks like this may be getting skipped when parsing the game files - I'll have to dig into it. There are quite a few items in the game files that are non-standard and therefore need some special handling. My gut says that this is one of these.
Just debugged it and working on a fix. Thankfully it's simpler than that. The name of the item was just stored in a non-standard location for a ring and without a name I choose to skip the item. I'm building a more robust system for mapping items to their corresponding names.
Awesome. Just updated the website and now the ring is showing (and the associated quest to obtain it). Very impressive that you found this missing item because there were only 2 items affected by that bug.