Time.
It’s an important factor when making a gimkit map.
You don’t want to spend too much time on little things.
This guide consists of tips in which to save time and work on your GKC maps.
Tip 1
When you place down a lot of props of terrain blocks and realize that they aren’t in the setting you wanted them to be in, its a frustrating time-wasting experience.
Let’s face it, we’ve all done this a couple of times when making our gimkit maps.
A solution to this is to test all the props and terrain by starting the game to make sure they’re in the proper setting you want them to be in before using them in large numbers.
While this sounds relatively easy, a lot of us forget to do this and end up wasting a lot of time.
If you don’t want to crash out like the leprechaun in the photo, make sure to play test your props and terrain before using a lot of them!
Tip 2
If you’re wiring 2 things to each other, it can be annoying to try to find which device/prop is wired to another one if they are far apart.
You can easily get lost and spend more time while trying to retrace the wire to its connected partner.
There are 2 solutions to this:
- You can use channels instead of wires
- You can wire things more closely to each other so you can easily spot on the wire connecting them
Tip 3
Ever had a lot of the same prop and you wanted to change a layer of one?
It can take a long time just to find the prop you want to change its layer to and therefore this is time-wasting.
A solution to this is renaming the prop so you can easily spot it on among the lists of props in the layer setting.
To rename your prop, click on a prop and go to the top left.
It’ll say the prop’s original name and click on that and it’ll let you rename it.
Tip 4
Always have smaller props and devices above bigger devices.
This way if you want to edit a smaller prop or device, instead of moving the bigger device, you can simply click on it rather than having to move the larger device and re-adding it.
Tip 5
Group your devices together if they’re in the same mechanic.
If you have your devices separated, it can be a hard task to figure out the problem of a mechanic.
This way when a mechanic doesn’t work you can easily go to your group of devices that are managing the mechanic and fix it.
Example:
I will add more tips later, but that’s it for now!
This is my first guide so I hope you enjoy.
this is actually surprisingly good and useful, i did the same errors a long time ago… it was like this:(the code was from like 90 years ago)