Tails Adventures Password Format Guide
By XFox Prower
| Release date: | 11/24/03 |
|---|
| Last Revision: | 05/07/04 |
|---|
Introduction
This document has been writen to describe the format used in the Tails Adventures password system for storing items and bosses beat, and stages cleared. You can find the password generator Here
The Password Screen
The password screen is made up of 16 cells in a 4x4 grid. Each cell holds a character ranging from 0 through F. Since there are 16 addresses in the grid, I will also label them 0 through F (left to right, top to bottom). Anything stored in the password will be referred to as an "event." Each event uses 2 or more cells in the password grid that it corresponds to. Most events use a checksum address (Address F). The checksum address works with the modifications to the other addresses in order to verify that an event is added correctly.
Starting Password
The password below represents a "new game" in which you start with the Regular Bomb and Vulcan Cannon.
D219
54D4
AE59
D2E0
Working with the events
Each event has a primary address. They may also have a secondary address. All items have an even primary address. All stage and boss events have an odd primary address. Secondary addresses for any type of event are always odd. Not every event uses the checksum address.
There are also 2 Checksum Exceptions that are used by some items. An item can have a T2, T3, or no exception at all.
| Poloy Forest Beat: Volcanic Tunnel |
| | | | ±8 |
| | | | |
| | | | ±8 |
| | | | |
| Volcanic Tunnel Beat |
| | | | |
| | ±8 | | |
| | | | |
| | | | ±8 |
| Lake Rocky Beat: Cavern Island |
| | | | |
| | | | -4 |
| | | | |
| | | | -4 |
| Cavern Island Boss Beat |
| | +1 | | |
| | | | |
| | | | -1 |
| | | | T2 |
| Poloy Forest Beat: Caron Forest |
| | ±8 | | |
| | | | |
| | | | |
| | | | ±8 |
| Lake Rocky Beat: Green Island |
| | | | |
| | -4 | | |
| | | | +4 |
| | | | ±8 |
| Lake Rocky Beat: Lake Crystal |
| | | | +4 |
| | | | |
| | | | |
| | | | -4 |
| Volcanic Tunnel Boss Beat |
| | | | |
| | +2 | | |
| | | | |
| | | | T2 |
| Lake Rocky Gate Destroyed |
| | | | |
| | | | +2 |
| | | | +2 |
| | | | -4 |
| Lake Rocky Beat: Coco Island |
| | -2 | | |
| | | | |
| | | | |
| | | | T2 |
| Battle Fortress Beat |
| | -2 | | |
| | | | |
| | | | |
| | | | T2 |
| Battle Fortress Miniboss Beat |
| | | | -1 |
| | | | |
| | | | |
| | | | T3 |
Checksum Exceptions
The checksum is usually simple and easily predictable. If the charts above say +2, then you just add 2, etc. But sometimes, there's a few twists and turns. Each address is 4-bit (0 through F). Different things can happen depending on which bits are turned on in the value of the checksum address. But only bits 2^1 and 2^0 are ever used. Type 2 is the when 2^1 is turned on and 8 is added before the initial checkum addition. Type 3 occurs in certain items when both 2^1 and 2^0 are on (2^1+2^0=3).in this case, 8 is added before the initial checksum addition. See the diagrams below:
 |  | Type 2 If checksum contains bit 1 (2^1) then add 8. Next add 2 (regardless if we added 8 or not). |
|
 |  | Type 3 If checksum contains bit 1 (2^1) and bit 0 (2^0) then add 8. Next add 1 (regardless if we added 8 or not). |
Normally the checksum is modified in some simple addition or subtraction without need of an event (see blue lines). But the events still keep a balance (see red lines). It makes an interesting crossover pattern. If you want to go by graphics, there's 2 blue lines before each red in type 2, and there's 3 blue lines before each red in type 3.