d_item_user can be anywhere from 0 to 255 unfortunately. It's a lot of trial and error at the moment, and I've still not been successful in finding any semblance of a pattern in these numbers.How many values of d_user_item should I be cycling through?
I've tried d_user_item values up to 26 with the item codes 75 (plant) and 129 (Key 1) with the username LUCKY with no success.
Huh. And Byte_5 was 0 when you changed Byte_4? That's interesting because it potentially shows some addition a structure I wasn't aware of.I found that a d_item_value of 71 works with the username LUCKY and the item_code 129 (key1), however I tried setting Byte 4 to the values 1, 55 and 166, and the password didn't work on all three occasions.
Yeah, byte_5 was left as 0.Huh. And Byte_5 was 0 when you changed Byte_4? That's interesting because it potentially shows some addition a structure I wasn't aware of.
Interesting! Either I've forgotten to add a BIN2DEC somewhere in the generator or there's something I've totally not accounted for.Yeah, byte_5 was left as 0.
Although it can be difficult for a human to get their head around, the operations used in decoding a password are actually really simple for a computer written in an assembly language (like the one Tamagotchis are written in) to perform. In some senses it's kind of the simplest way they could do it while still maintaining some level of username encryption!Quick questions from someone who is both really bad at math and really impressed by your research so far--
If a Tamagotchi is technically such a simple and small device, why does the password generation have to be so complex? I understand that the developers didn't want people being able to cheat to get easy codes for everything and ruin the fun, but is it REALLY that difficult of an algorithm, or is it just really difficult to narrow it down to what they chose to do with it?
I'm having a ton of fun reading through these posts
I'm wondering if the reason some of the passwords aren't working is to do with the Y at the end of the username? This puts a 1 at the start of the username constant which I'm not sure how to deal with yet - it could be having adverse effects on the rest of the password.Found some more working codes
Also bought some airplane tickets which gave me the following codes
Australia code (Username:LUCKY): 67864 34388
Switzerland code (LUCKY): 12472 35059
Item code
d_item_user
byte_04 (working)
byte_04 (non-working)
130
70
1
56, 87, 148
131
69
2
1, 4, 126, 244
132
68
1, 2
126, 244
Oh wow. I had speculated that Passwords might be able to be used to obtain unused items or unoccupied item IDs, but my personal testing had led to finding no such working passwords. I'm honestly kind of surprised that these "items" do exist, after all![SIZE=12pt]Item code [/SIZE]
[SIZE=12pt]d_item_user [/SIZE]
[SIZE=12pt]byte_04 (working) [/SIZE]
[SIZE=12pt]byte_04 (non-working) [/SIZE]
[SIZE=12pt]128[/SIZE]
[SIZE=12pt]72[/SIZE]
[SIZE=12pt]1, 2, 126, 244, 255[/SIZE]
[SIZE=12pt]129[/SIZE]
[SIZE=12pt]71[/SIZE]
[SIZE=12pt]1, 2, 126, 244[/SIZE]
[SIZE=12pt]130 [/SIZE]
[SIZE=12pt]70 [/SIZE]
[SIZE=12pt]1 [/SIZE]
[SIZE=12pt]56, 87, 148 [/SIZE]
[SIZE=12pt]131 [/SIZE]
[SIZE=12pt]69 [/SIZE]
[SIZE=12pt]2 [/SIZE]
[SIZE=12pt]1, 4, 126, 244 [/SIZE]
[SIZE=12pt]132 [/SIZE]
[SIZE=12pt]68 [/SIZE]
[SIZE=12pt]1, 2 [/SIZE]
[SIZE=12pt]126, 244 [/SIZE]
[SIZE=12pt]133[/SIZE]
[SIZE=12pt]67[/SIZE]
[SIZE=12pt]244[/SIZE]
[SIZE=12pt]1, 2, 126[/SIZE]
[SIZE=12pt]134[/SIZE]
[SIZE=12pt]66[/SIZE]
[SIZE=12pt]1, 244[/SIZE]
[SIZE=12pt]2, 56[/SIZE]
[SIZE=12pt]135[/SIZE]
[SIZE=12pt]65[/SIZE]
[SIZE=12pt]2, 244[/SIZE]
[SIZE=12pt]1, 56, 126[/SIZE]
[SIZE=12pt]136[/SIZE]
[SIZE=12pt]64[/SIZE]
[SIZE=12pt]1, 2, 244[/SIZE]
[SIZE=12pt]126[/SIZE]
I’ve also generated some passwords for the ‘undefined’ item codes from 127-113 after finding that d_item user increased sequentially. This worked from item_code 127-120, and I was getting text in ‘map tile’ format blocks from these codes. I’ve included a photo of item_code 125 as an example.
https://i.imgur.com/U60xLb1.jpg
[SIZE=12pt]Item code [/SIZE]
[SIZE=12pt]d_item_user [/SIZE]
[SIZE=12pt]Tile[/SIZE]
[SIZE=12pt]127[/SIZE]
[SIZE=12pt]73[/SIZE]
[SIZE=12pt]TIE[/SIZE]
[SIZE=12pt]126[/SIZE]
[SIZE=12pt]74[/SIZE]
[SIZE=12pt]P[/SIZE]
[SIZE=12pt]125[/SIZE]
[SIZE=12pt]75[/SIZE]
[SIZE=12pt]SG CK[/SIZE]
[SIZE=12pt]124[/SIZE]
[SIZE=12pt]76[/SIZE]
[SIZE=12pt]TS[/SIZE]
[SIZE=12pt]123[/SIZE]
[SIZE=12pt]77[/SIZE]
[SIZE=12pt]W[/SIZE]
[SIZE=12pt]122[/SIZE]
[SIZE=12pt]78[/SIZE]
[SIZE=12pt]AR2 (The A was cut in half)[/SIZE]
[SIZE=12pt]121[/SIZE]
[SIZE=12pt]79[/SIZE]
·[SIZE=12pt]OY(First dot looked like part of a ‘T’)[/SIZE]
Also managed to snag another ticket code.
China (LUCKY): 20690 70397
They don't appear in your inventory or souvenir list and can't be bought.Oh wow. I had speculated that Passwords might be able to be used to obtain unused items or unoccupied item IDs, but my personal testing had led to finding no such working passwords. I'm honestly kind of surprised that these "items" do exist, after all!
Can any of them be bought or used?
Ahh, so presumably you just receive them as you would with a souvenir and it presents the garbage data it's received as though it's a souvenir but there's no menu option for it or anything. Interesting!They don't appear in your inventory or souvenir list and can't be bought.
Enter your email address to join: