Click here to edit contents of this page.
Click here to toggle editing of individual sections of the page (if possible). Watch headings for an "edit" link when available.
Append content without editing the whole page source.
Check out how this page has evolved in the past.
If you want to discuss contents of this page - this is the easiest way to do it.
View and manage file attachments for this page.
A few useful tools to manage this Site.
See pages that link to and include this page.
Change the name (also URL address, possibly the category) of the page.
View wiki source for this page without editing.
View/set parent page (used for creating breadcrumbs and structured layout).
Notify administrators if there is objectionable content in this page.
Something does not work as expected? Find out what you can do.
General Wikidot.com documentation and help section.
Wikidot.com Terms of Service - what you can, what you should not etc.
Wikidot.com Privacy Policy.
Discussion
You could always use a random seed system to make a password.
This code could be used to create and store a password:
In which A would be a password, and B would be the randomized number based on it.
So the password 1234 would produce .0219931723, which could then be stored somewhere. This way, nobody can just read through variables to find the password.
Using this method, you could check to see if the password is correct with the code:
I have an idea for a password system. Instead of using variables A and B, you can use lists. You can store keycodes in a list and store them to an App Var to prevent easy tampering for calculator Greenies.
If you need examples, let me know.
Hewwo, my name is Achak Claw. I was formerly BioHazard.