We all have had this problem. You know the one I’m talking about.
Not being able to detect text answers with block code. this is a STRUGGLE for wanting to load save codes. but all this time we have been trying to detect thing outside gimkit, without thinking outside the box. if we cant detect text input, why not just make that text input in gimkit ourself?
introducing
PSUEDO TEXT-ENTRY!
It’s simple but costly in memory, but it will do for now till we can find something better.
first place a trigger! then make a “When Triggered” block code. make it like this!
then copy that trigger 51 times and change the letter to match the number key it is.
then we set up that property!
Hooray the text inputting has been made, but we aren’t done. remember what this is solving? we need a way to check that text property now.
WE NEED A TRIGGER CHECK!
this is how the trigger check will be set up.
we will have a button that once pressed brodcasts a message, like this!
Yes this keyboard has already been made several times, while it won’t be flagged because of Blackhole’s rules on flagging duplicate guides please try to do something more original. I’m fine with several keyboard guides however this is very similar to some of the other ones. Also please remove technical, technical guides are guides that are more on the complex side and use a ton of block code[1]. For example, I would say @getrithekd’s Player Selector guide was technical. Also in general why is there the code tag? Most guides with blockcode don’t even use it… Second: Please don’t make a guide off of a Help post. You made a help post asking how to do this very thing and I responded with the answer and saying something like “However that way is not very memory efficient”. My third point: Some people don’t really memory efficiency their systems and that’s fine to a certain extent. When a system is 10% memory, okay fine. But when a system in 25-35% memory maybe look into some efficiency systems. My fourth and final point: If you want to do a keyboard guide do a variation that’s never been done before, like using counter arrays!
Like the idea, like really well - but hasn’t this been made before? Maybe I’m tweaking but this already exists. We’re also looking for a memory efficient version.
This guide has been done many times before, for example:
So first, this is a duplicate.
Why We Don’t Like Duplicates
why do we need more than one guide on a topic? We have the information already, why say it again when we don’t need to.
Your Formatting
you have A LOT of pictures, which is good, but we could keep it tidier if we used text, and only used pictures when needed. Also, more dropdowns so its more divided and easy to read.
Why does This Work?
you show how to do it, but not why it works.
The title
the titles a bit wordy, maybe put the warning in the guide?
The introduction
introductios good, waiting for it to be great.
Conclusion
there is none.
Poll
obviously take away the uneeded options, because people are goofy goobers who like to choose 11/10 for everything
Drop-down Names
boring, don’t really catch my eye
Overall Rating
5/10
********************************************************************************************************************************************************************************************************************************************************************************************* Did you like my essay?
