So I was working on my chess project, and I thought of something. The one MAJOR issue with gimkit (in my opinion), is the lack of the ability to send parameters with broadcasts.
This is a basic workaround/explanation, and isn’t that complicated either.
If you have alot of buttons, such as this, then it can be a pain to detect which button you pressed without wasting alot of memory on triggers.
My solution is to wire or send a broadcast to a counter for each button, which updates a property. Each counter starts at a different value (you can use basically any value you want), and when it increments by one, the property updates.
You set a setting in the property so when it updates a trigger runs.
This trigger has block code to take that property and output whatever data you’d like based on the number.
So we can detect which button is pressed for 35 memory instead of using 550 memory.
Also @Blackhole927, you probably already knew this, but I was thinking about this and it might be possible to do your bitwise AND operation using a counter. We can say each counter represents a bit, so by chaining them together, you can in theory compare counters…
(Though it’s 100% impossible algebraically with looping through 1 by 1, since if you think about it, computer systems are BUILT in binary, so they can innately do this.)
Don’t worry about it
It took me way too long to think of this lol (literally hours), and I wouldn’t have thought of this without my current project, so yk, hope it’s useful to you one day!
Its good that you made a guide on this unspoken rule. Its kind of hard to put those things into words, probably a key to why there wasn’t a previous guide on this
