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!
then we place another trigger, but not for a key we set it up like this.
How difficult is this guide?
1/10
2/10
3/10
4/10
5/10
6/10
7/10
8/10
9/10
10/10
11/10
0voters
Extra Features!
Caps lock
CAPS LOCK!
that wasn’t a mistake, I’m talking about the key caps lock. we can do this by placing the old key script in an if then, checking if a property equals “lowercase” and if it does we do the old one, if not we duplicate the old one switching it for an Capital letter. make sure to make the property for it.
Backspace!
Ever made a mistake writting and had to start all over? no? that’s because the backspace key, we can EASILY replicate it, it will take some block code but its manageable. first duplicate a key trigger, but delete the script it contains, we are making an entirely new one. add a block code script and set it like this
In conclusion this can be very useful for save codes, although Im going to soon update this guide (once I can figure for the life of me what a counter array does.)
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?
You can use numbers to replace letters and store them using counter arrays instead of block code.
One way would be a button that cycles through the alphabet using a counter array like this:
Ha → Hb → Hc → Hd → He → Hf → Hg → Hh → Hi
1 → 2 → 3 → 4 → 5 → 6 → 7 → 8 → 9
Click enter then move onto the next letter.
Also this isn’t really a “Pseudo” either. There is no text entry in GKC so this isn’t a “not genuine” version of it.
until I get home and try to understand that a bit more, I added some extra features for now like caps lock and backspace. I think I get it, basically it saves letters as numbers but how would I conbine the text to the property from there @harharharhar83?
@here I’m just going to make an entirely new keyboard guide, its very unique from others, just will take quite a bit till it releases as its quite complex to explain. its also quite memory efficient as it is only 3% memory (most of that was due to me using Counter Arrays, thanks getrithekid).
. I’m only in 8th grade and the school year started 2 months ago, idk how I got this far if Im gonna be honest.