I know this isn’t related to GKC directly, but it is very useful, please understand. Ok, so over my months here on the forum, I have noticed that I, among others, do not always have the time to jump on GKC and put together all of the blocks. So often people will use this:
If guide is good then
do give a like
Yeah, this works, but users are all over the board on how they represent the blocks, so sometime’s it can get confusing. Therefore, I propose the Universal Typing of Code.
Well, how do you say we type it?
Glad you asked. Some important things for getting across the block code to others needing it include the following:
- All of the used blocks. Can’t just assume they know what you mean?
- Separation of blocks. Don’t want to combine set property and random text like they are one, as it might confuse new users
Yeah, so I will show you how this works.
For blocks next to blocks (connected), use these: {*
For drop downs, use these: [drop down option]
For within blocks** use these: (block)
*-- No right one is needed, as it will just be an enter to start a new line
**-- Within blocks are blocks that are within others. Like a get property inside of an if
Now, here’s an example:
(Picture is from @Axolotl’s guide, titled “random code by axolotl”. This is used for example purposes only. Also, it was convenient.)
This now becomes:
set [pick random] to { random integer from (1) to (2)
if { (pick random) [=] (1)
do { Broadcast Message On Channel { energy bar
Well, that’s it. Don’t worry about the colour, no body can help that. I hope you all find this good. Polls: (Please be honest, not goofy)
- Terrible, block code shouldn’t exist
- Okay, but people wouldn’t need this
- Good, but only for people who talk about and use block code often
- Awesome! Glad you made such an effective system for blocks communication!
- No, this is outrageous!
- It’s good, but I think some tweaking could be used
- Perfect! I look forward to using this as I show others useful block code!
Anyways, I’m Here_to_Help, and Happy Gimkitting!