Thanks for the suggestions! Here's some responses:
manawe wrote:1) I would recommend
adding rendered maps instead of png - its reasonably simple.
In 2nd year at uni I did a small wiki myself in order to learn angular for my summer job - here is a short video:
https://www.youtube.com/watch?v=o2OfkTTqAaY
This could allow you to add filter options to the map - highlight objects on maps, hide ground, add background mask and opacity, etc etc, sort of like Gabrael maps, or link to mob map links which could center on map.
Yup, this is on my list of things to do. Don't know if you've seen my
Interactive World Map but my idea is to turn that into rendered maps you can quickly move around on, zoom in and out on, and look at stuff on. Then I want to have MODB link to it (like click from a vendor page to go to the interactive map that vendor is on and see where they're at. Mobs & other stuff too. Just need time to work on it. (all of this is done in my "spare time" after working an average of 60hrs a week, lol)
And BTW, that YouTube link says the video is unavailable. LMK if you have a working link, would love to see it.
manawe wrote:2) Improve navigation of wiki (NOT SURE if can be done easily in react! Quick googling showed this:
https://reacttraining.com/react-router/ ... mple/basic)
Every time you load up a new page from navigation it is re-rendered. It could be better to
use History API to update the URL without reloading the page or partial view.
Quick example (couldnt find anything I did which is more cpu intensive to highlight the difference, I used static routing in my rpg wiki too xD):
https://youtu.be/YTSqkzyed3I
Actually, the entire page isn't re-rendered when you click stuff/search. It only changes the parts of the DOM that need updated. EG, the nav on the left almost never changes (the numbers change when you search, but otherwise it's pretty static.) That said, I'm actually rebuilding the app in the latest version of React (the original app is very old, and a lot has changed.) I'm also breaking the data out (right now everything is in one giant JS file (almost 3MB.) I've already built an API for it, and am working on the app itself now. It'll probably be a month or two before I release this version, lots to do, and I want to continue working on the current version too.
Edit: I just noticed on mobile that clicking some links will scroll the page to the top, giving the feeling that it is refreshing. This is because I'm using the Hash API - This will change in the next version of MODB. For now, it has to stay though.
manawe wrote:3) Add page showing arrow information (like spells)
Good idea! I've actually got it on my list to make arrow images work (they work completely differently than the rest of the game's images) and just haven't gotten around to doing it. Maybe I'll make that arrow page as you suggest and do the images at the same time.
manawe wrote:4) Allow to adjust dps/xps for spells/arrows based on the selected cool down reduction.
Actually, I'm working on adding "Item Sets" to the "Load Character" system so you can create 3 sets of gear: Melee, Magic & Archery. Then if you create a Magic set the spells page will automatically calculate your CD reduction and add "Your DPS" and "Your XPS" columns to the list. The same idea would apply to your Archery set and the (soon to exist) Arrows page.
I also want to use the Item Sets to integrate a Combat Analysis (one that would work for Archer too!)
manawe wrote:5) List vendors with just their names and images of items - condensed view which does not require clicking on vendor names which takes you to separate screen. Add item filter to vendors.
Nice idea. I'll have to look into it. Shouldn't be too hard.
