#Kushify Cheat Codes update#
#Kushify Cheat Codes code#

#Kushify Cheat Codes update#

Now you might be thinking that it might makes sense to put this further up in the update function when we were checking for the return being pressed. If this happened then we’ll reset the string back to an empty string. The next “if” checks whether the enter or return key was pressed. We have to give the function a starting index, in this case the 0th character and and ending index, in this class the length of the string minus 1 so that we remove just the last character.

Which will essentially make a smaller string out of our “current string'. This is done with the “substring” function. If either was and the current string is longer than 0 characters we’re going to remove the last character in the string. So first we need to check if the backspace or delete (Mac, right?) keys have been pressed. While it’s unlikely that you can type so fast as to get multiple characters in a single frame it seems reasonable to cover all the cases. The value “Input.inputString” tracks all of the keys pressed in a given frame. To do this I’m using a foreach loop that will loop through all the characters in the current input string. If the player is typing then we need to process the characters that they’ve been typing. The next piece is a bit of a mess of if’s and such but hopefully isn’t too tough to follow. Try not to get too excited :)Īfter that we toggle the value of the “player typing” variable to the opposite of its current value. We’ll get to the “check cheat” function in just a bit.

#Kushify Cheat Codes code#

If this is done while (or after) the player was typing then that indicates that the cheat code is complete and we need to check if it’s correct. The first step is to check if the enter or return key has been pressed. Next up is the core of the code, which is sitting in an Update function. Which is HUGE! And I’m willing to bet that your project can benefit from cheat codes too. This changed a 5 minute testing cycle into a 30 second testing cycle. A few keystrokes and the resource was available. With a few lines of additional code I could instantly have as much of any resource as I needed. Now this didn’t take much more than 5 minutes, but when you need to do it 5, 6 or maybe 10 times in a row you end up wasting a lot of time.Īnd that’s where the cheat codes come in. If I wanted to test that my UI was working or the placement of a building was working, I’d have to start the game, create a bunch of workers, wait for them to collect the resource and then I could test the placement of the building. Those resources were then used to create things like buildings or catapults. In my game, like so many others, you had to collect resources. The idea was a suggestion of a twitch viewer (Wago) as a way to help with testing and debugging. I’m not sure anyone found them, but I thought it was a fun idea :)īut that wasn’t the reason I first put cheats into my game.

In my first game I placed cheat codes in the wallpapers that players could earn by collecting cards on Steam. Great question! There’s the obvious answer is that they can be fun easter eggs for your players to find and discover.