Don't have an account yet? Then register once and completely free of charge and use our wide range of topics, features and great options. As a registered member on our site, you can use all functions to actively participate in community life. Write posts, open topics, upload your pictures, put your videos online, talk to other members and help us to constantly improve our project and grow together! So, what are you waiting for? Become a part of us today!
Login or registerTo get support for a technical issue such as installing the software, to query a purchase that you've made/would like to make, or anything other than using our software, please visit our Customer Service Desk:
Open a Ticket
Hello
My method : Please login to see this link.
+
Good one Patrice!
I was doing it via global values to test the joystick input but then was wondering how I would do the reset if the player pressed wrong.
Your method is the way!
Very Nice, Thanx Patrice 
Alright, that's nice and all, but a really cheesy way to clear stuff out. Here's a much better method:
Please login to see this link.
Alright, that's nice and all, but a really cheesy way to clear stuff out. Here's a much better method:
Please login to see this link.
Patrice's method may seem convoluted, but it works. Yours on the other-hand allows the user to mistype or do an extra key press and still get the trick to work, Patrice's method works perfectly.
Buurrrnnn. :p
But yeah, clever method Patrice!
Patrice's method may seem convoluted, but it works. Yours on the other-hand allows the user to mistype or do an extra key press and still get the trick to work, Patrice's method works perfectly.
Er, yeah. I'm pretty sure that's what's supposed to happen. As long as the last things you pushed were ↑↑↓↓←→←→BA Then it should work... right?
If not, here's a small fix to make it work like you need.
Please login to see this link.
Alright, I'll give up. 
But the original version didn't allow wrong keystrokes. I don't know what made you think that. :L
Patrice - Nice example, works well, but I try to avoid long hard coded conditions like the one you use to clear the string input when wrong - they feel a bit messy and can be hard to alter if you need to change the code later for some reason.
SuperDisk - Your second example seems to be the same as your first and simply ignores clearing the string input when wrong. Also, if you start off wrong, eg
A, up, up, down, down, left, right, left, right, B, A
it doesn't work - I think you meant to use Right$ instead of Left$ in your last condition.
I thought it might be useful to be able to check more than one cheat code, eg for unlimited ammo, unlimited time, maximum lives, etc.
So here's an example that uses a List Object to hold the cheat codes and checks the user's input against them for a match.
nicely done AyreGuitar !
Thx very nice adaptation
Awesome guys, thanks for all your concept and ideas!
And also thanks a lot for share with the communauty !
Nice play!
AyreGuitar: in your MFA if we don't enter following input command suffisely quickly, it then cancel all commands input and we must restart from zero. -> IS it intentional
Backstaged - No, it's not intentional (and I can't repeat that here).
There shouldn't be any kind of time limit for entering the code - it only clears the input if it doesn't begin to match the codes in the List object.
If you try to start with Left then the string remains blank, because none of the codes start with L
Perhaps you made a mistake (or I made the code wrong in the List object?!)
Thanks for answer AyreGuitar, here I can't no more reproduce the bug.
Then perhaps It was me, or you, well.. We never know who is the fault 
But, hey, thanks again for your piece of work
Don’t have an account yet? Register yourself now and be a part of our community!
Almightyzentaco (Fusion 2.5 Tutorials)
Captain Quail (Firefly Tutorials)
