versx / WhMgr-UI

6 stars 15 forks source link

Various Improvement suggestions #39

Open nileplumb opened 3 years ago

nileplumb commented 3 years ago
versx commented 3 years ago

Also, half of this should have been for WhMgr vs WhMgr-UI, since WhMgr-UI just manipulates the database so WhMgr can read the changes.

versx commented 3 years ago
versx commented 3 years ago

@nileplumb

nileplumb commented 3 years ago

well I was thinking it would act like a filter of sorts, so it would check which pokemon you've selected then only display the icons (or text if icon missing) for the available forms of the selected pokemon. because at the moment all possible forms are listed including some confusing duplicates

eg upcoming Slowpoke people might erroneously select a 'normal' Slowpoke or 'Galar Standard', when in fact this would be normal castform and darmanitan

I'd argue against a drop down box perhaps a collapsible section, default All forms selected (including future releases not yet in master file eg a pikachu subscription should alert for any weird form costumes they release in future )

QUESTS I believe it should show every possible combination, at the moment many people are chasing Galarian Zigzagoon and Ponyta quests, let's assume a player wanted to set up their alerts now for a future event they can't, nor can they if they try to set up when the database is quest empty (eg with so many events now I often delay quest scans until 10am on new event days, the database would be empty and players can't chose any new subscriptions)

ADMIN PRESETS SUBSCRIPTION BUTTONS are separate json files not an option?

eg { "min_iv": 0, "max_iv": 100, "min_level": 0, "max_level": 35, "gender": "all", "size": "all",

"Exeggutor": {
    "form": Alola, (or specific Id number eg 78)
    "min_iv": 0,
    "max_iv": 100,
    "min_level": 0,
    "max_level": 35,
    "size": "All",
    "gender": "All"
},
"Dratini": "True",
"Dragonair": "True",
"Dragonite": "True",
"Kingdra": "True",
"Altaria": "True",
"Bagon": "True",
"Shelgon": "True",
"Salamence": "True",
"Latias": "True",
"Latios": "True",
"Rayquaza": "True",
"Gible": "True",
"Gabite": "True",
"Garchomp": "True",
"Dialga": "True",
"Palkia": "True",
"Giratina": "True"

}

nileplumb commented 3 years ago

another good option that'd be very user friendly would be for a logged in admin to chose the pokemon themselves then have an option to save as a new preset for others choosing a button name etc

versx commented 3 years ago

well I was thinking it would act like a filter of sorts, so it would check which pokemon you've selected then only display the icons (or text if icon missing) for the available forms of the selected pokemon. because at the moment all possible forms are listed including some confusing duplicates

eg upcoming Slowpoke people might erroneously select a 'normal' Slowpoke or 'Galar Standard', when in fact this would be normal castform and darmanitan

I'd argue against a drop down box perhaps a collapsible section, default All forms selected (including future releases not yet in master file eg a pikachu subscription should alert for any weird form costumes they release in future )

QUESTS I believe it should show every possible combination, at the moment many people are chasing Galarian Zigzagoon and Ponyta quests, let's assume a player wanted to set up their alerts now for a future event they can't, nor can they if they try to set up when the database is quest empty (eg with so many events now I often delay quest scans until 10am on new event days, the database would be empty and players can't chose any new subscriptions)

ADMIN PRESETS SUBSCRIPTION BUTTONS are separate json files not an option?

eg { "min_iv": 0, "max_iv": 100, "min_level": 0, "max_level": 35, "gender": "all", "size": "all",

"Exeggutor": {
  "form": Alola, (or specific Id number eg 78)
  "min_iv": 0,
  "max_iv": 100,
  "min_level": 0,
  "max_level": 35,
  "size": "All",
  "gender": "All"
},
"Dratini": "True",
"Dragonair": "True",
"Dragonite": "True",
"Kingdra": "True",
"Altaria": "True",
"Bagon": "True",
"Shelgon": "True",
"Salamence": "True",
"Latias": "True",
"Latios": "True",
"Rayquaza": "True",
"Gible": "True",
"Gabite": "True",
"Garchomp": "True",
"Dialga": "True",
"Palkia": "True",
"Giratina": "True"

}

Forms: I like the idea of only showing the available form buttons/selections relating to the Pokemon selected.

Quests: Thanks

Admin Presets: Ok so using PokeAlarm filtering for the standard for presets, can probably do that.

nileplumb commented 3 years ago

yeah customisable presets would be more of an advanced and optional thing deployed by a server admin, (though including XL karp and Tiny Rat presets would be welcome by many ) I think some filter configuration by json is acceptable for them.