Calculator Suggestion: Let us Toggle Megas, Generations and NFE Pokémon!

Question

Title sums it up. I can't imagine those features would be difficult to code in. I do hear that there's just this one guy that works on this site though. Does anybody know how I can get in touch with him, or alternatively, does anybody know of a calculator that lets me do the things I'm asking be implemented?

Somebody made a suggestion that had to do with toggling generations back in 2012, but I don't think that went anywhere. Why do the people in charge turn a blind eye? Or maybe they don't know? Anyway, thank you.

Comments

You don't need to make the same suggestion twice. You can edit your original thread to mention NFE Pokemon if you so desire. The site admin (whose name is Pokemaster) periodically checks the Meta section and will almost certainly read your thread. We've learned to be patient with that.
I'll leave this thread up to answer your other questions, though:
- You are correct that one person runs pokemondb.net. This site is not his main vocation. You can contact him through the email address linked on this page. https://pokemondb.net/about
- Assuming that you're looking at the same thread as me, I wouldn't say Pokemaster turned a blind eye so much as he seemed apathetic to the idea itself. I gauge that adding non-essential (though convenient) updates to the type coverage checker is not a high priority for him right now. https://pokemondb.net/pokebase/meta/21696/

---

Even if these features wouldn't be 'difficult' to code in (as a person who codes, that isn't always the case, as simple things like programming a deck of cards to play war isn't easy-peasy and takes at least 3-5 hours from scratch, if you know all of the essential 'techniques' needed) it will take a fair bit of time to do (probably due to making a lot of exceptions for specific things and writing on-off code for them, and especially when debugging), which our webmaster is already filling with life and other things. If we get this site's open source repository on Github like was mentioned a while back, someone else with time can add code to implement these changes and all PM has to do is accept (or decline :P) and merge, and then update the site, which is probably how most significant changes to stuff like the Type Coverage Checker would happen. :P

The one thing we should hope for is that PM gets the hard work done of setting up the Github and the converter, which he is almost definitely busy with in terms of this site. Personally, I think that this is the best route for most of the minor suggestions of the site. :P

Sorry if I got a little salty about programming, I have very strong opinions. :P

---

I don't know how to respond to the two of you individually, but thank you. My concern was the webmaster wouldn't bother checking the Meta section. It seems like changes to the Calculator will take some time to be fully developed, as he's busy in his own right. My apologies in making the same suggestion twice over. I don't quite know how I should frame this question but how long do either of you think it will take until changes can come about?

---

That's hard to say. It depends entirely on what his priorities are at the moment. I think he'd still be looking to improve the Sw/Sh database at the minute, though he might update you on that personally when he checks in here.