@dreadzly no, you're the one who made several wrong assumptions here.
First, the two weeks have nothing to do with why I knew that you're a relative new user, no matter how much time you worked with the program. That came because you had to ask how to display a variable in show text and the two weeks you mentioned only confirmed that.
And my answer to that question wasn't a generalization, but a direkt pointer to both the solution and the most important part of the show text command: the text codes or control codes.
If you even start to make a show text command in any event, you'll have to click with the mouse into the text frame.
If you then pause even two or three seconds to think what to write (without moving the mouse away), you get a large popup listing all default text codes - that is how important they are, important enough for the programmers to place them into a sometimes annoying popup on the main input of the show text command.
One of these text codes allows the display of variable content, others are for name replacements or color control or time control of the show text command.
Second, my mentioning of event pages and conditions to improve your event.
While this was a short form and no detailed "click here and write that" instruction, it should have been enough to point someone with the basics into the correct direction for that, again because the event pages and their conditions are an important part of eventing.
When you continue to be part of this community, you'll find that a lot of people helping you will give you similiar answers to point you into one direction instead of providing an exact solution.
That has a lot of reasons, and none of them have anything to do with being rude. It's simply the fact that we cannot make your game for you, you are the only one who can really work on it.
No one here on the forum gets paid for helping others, we all help in our free time instead of working on our own games. I could easily continue to work on the specification for a plugin I need to commission instead of writing these explanations for you.
And over the years everyone on this forum has learned again and again that directly providing someone who hasn't the basics with a solution to a specific problem will cause more problems in the long run if that user simply copies without understanding what the event really does. A lot of games have been abandoned and their developers left in frustration because they didn't take the time to learn the basics for understanding what the engine does.
So what we want is for the new users to start thinking on the pointers we give to start them learning, and come back with specific questions (preferably including screenshots of the events they have so far) if the general pointers are not enough. If we simply give a solution for one specific case, it often results in a dozen questions later when that user tries to do the same in different cases and wonders why it doesn't work elsewhere (usually because one of the settings was for that specific case and needs to be different for the other cases).
Third, one of the things I tried to make clear to you with the first sentences is that there is no shame to not know everything, because the RM engine is extremely large in its options.
Yes, it can be learned by a child (in fact there are people here who have their children using RM before they were 10), but that doesn't mean it can be used without putting in time to learn it. It takes years to master all its aspects.
But because it has so many parts it is basically impossible to learn it without tutorials as a guidance that point you to everything. "Learning by doing" is extremely slow if you don't check the help file or tutorials to learn that an option even exists.
And that is another reason why you will often get referred to tutorials - the instructions could get very long and repetive if we had to explain everything again and again.
I even wrote that "starting point" tutorial in my signature with the express intention to get new users through the steps that show them everything the engine can do as fast as possible. But that "as fast as possible" is about a month of intense work through those tutorials in my opinion (and most people have agreed with that, both that it is the fastest way and that it is important to get everything listed there).
If that way of handling things is not something you prefer, then I'm sorry. But it has been proven as the most effective way that takes both sides into consideration - not only the side of the user who wants an answer, but also the side of the expert that doesn't want to waste his own free time for explaining every single click again and again.
And you'll find that as long as you do your part of any task (not only giving details when asking questions, but also giving details when you request someone to do a sprite or audio or script for you for free), then this community is extremely helpfull.
We are just tired of helping people who refuse to do their own part of getting help (and that is not against you, there was just a case shortly ago where a user had problems with error messages, we asked questions to get the details of what caused those error messages and always only got 20% of them answered with changing descriptions of what the user wants. That was very frustrating and couldn't be solved in the end, after several people wasted hours of their time to reproduce the problem)
