Oh my Goodness! At the beginning as I heard that you made Essentials I thought you were nice, but now you proved the opposite. As you said some words that are a little offensive to me: "Making the game work properly (I didn't say that) really out to be too obvious to mention. stupid idea, wouldn't be use by anyone. How dull. Not worth."
I do not try to be rude. I know I can be blunt at times, but I certainly don't try to offend.
My answers come from the perspective of the developer of Pokémon Essentials, which, as its name suggests, is for the basics of what is needed to make a Pokémon game. Frills and unnecessary features are, at best, low priority, and more often than not are simply excluded for being niche or vague or not worth adding. What is "worth" adding? Well, frankly, that's up to me, because I'm the only one working on Essentials (everyone is free to volunteer, but they don't because it's
Someone Else's Problem). And I expressed my thoughts on the suggestions you gave, because you apparently wanted me to - I originally didn't want to, remember, but you prompted me into it.
Please note that the suggestions you gave aren't your original ideas. Other people have thought of them before, and suggested them before, and I've responded similarly before. Any distaste I show is towards the ideas,
not to the people suggesting them. I welcome all ideas, but that is of course not the same as
accepting them all. My time is finite, and I don't want to spend it on things which I think will be of minimal use (such as being able to sit on chairs).
"Making the game work properly (I didn't say that)" really out to be too obvious to mention.
A bug in a game is an instance of the game not working properly. By definition, fixing bugs means making the game work (more) properly. As I said before, this is a general statement that doesn't help with anything, because it doesn't highlight one particular thing that needs fixing. If I said "my car doesn't work properly", how useful is that statement? Which part of it doesn't work? Is there just one aspect that's broken somehow, or multiple issues? How are these things broken, and how should they work instead? There's nothing to go on, no piece of information which tells me what I should be looking at.
Really, the whole point of me working on Essentials at all is to make it better. I'm not going to purposely make it
worse, am I? Making improvements and fixing bugs is the very core of my presence here, so if there's one thing that
doesn't need to be suggested to me, it's to make improvements and fix bugs, particularly if you say it in such a general way as you did. It
does go without saying.
I did not know about that with the Pickup that you can put the items to the bag.
You would be quite easily able to edit the code to make this happen. As I said, though, Essentials tries to mimic the official games, so Pickup works like it does in the official games, i.e. the picked-up items become held items. I just gave you a suggestion of how you could adapt the ability to work more like the example you gave (wanting Pokémon holding an item to still be able to pick up items).
I know the wiki isn't up to date or complete. It's a big task. Everyone is free to update it, but no one does, either through laziness or assuming someone else will do it or because they don't know about the subject. Again, my time and attention are finite, and if I'm having to do it all myself, of course it's going to be slow progress. If you have suggestions for how the wiki can be improved (specific suggestions, please, not sweeping statements like "make it more user-friendly"), please do share them.
Essentials and the wiki are not intended to be used by complete newbies, which I think is reasonable. Anyone using them will be making a game, and that requires dedication and imagination and skills. You need to know how to use RMXP, for one - the wiki isn't going to explain that kind of thing. The wiki is also not going to describe in detail every single possible thing you could do with it, because that's an infinite amount of possibility and it'd just be ridiculous to expect that. No, it can explain the basics, and occasionally give the reader ideas of things they could customise, but if someone wants some outlandishly original feature, they ought to figure it out for themselves - they have imagination and dedication, and they should know how tough making a game can be, so they can either learn and achieve for themselves or they can compromise.
And Maruno I am not lazy, I am the opposite of lazy! I work everyday at my game.
I never said or implied you were lazy.
This is getting off-topic now. If you have something further to say, please do talk to me in PMs about it.