Talk:TypeDex: Difference between revisions

From Glitch City Wiki
Latest comment: 30 days ago by Evie (Torchickens) in topic ??? type
Jump to navigation Jump to search
Content added Content deleted
mNo edit summary
No edit summary
Line 3: Line 3:
This type (belonging to Curse in Generation II) is missing. I've also heard rumours that if you hack it as a damaging move, it causes some more unexpected errors. Something like it is neither physical or special? Needs confirming. [[User:Evie (Torchickens)|Evie (Torchickens)]] ([[User talk:Evie (Torchickens)|talk]]) 11:38, 2 May 2024 (UTC)
This type (belonging to Curse in Generation II) is missing. I've also heard rumours that if you hack it as a damaging move, it causes some more unexpected errors. Something like it is neither physical or special? Needs confirming. [[User:Evie (Torchickens)|Evie (Torchickens)]] ([[User talk:Evie (Torchickens)|talk]]) 11:38, 2 May 2024 (UTC)
:Its index number is 0x13 in hex (dec:19). [[User:Evie (Torchickens)|Evie (Torchickens)]] ([[User talk:Evie (Torchickens)|talk]]) 11:50, 2 May 2024 (UTC)
:Its index number is 0x13 in hex (dec:19). [[User:Evie (Torchickens)|Evie (Torchickens)]] ([[User talk:Evie (Torchickens)|talk]]) 11:50, 2 May 2024 (UTC)
:I also wonder what happens if you turn a Pokémon species' type into ??? and using an attacking move on it? [[User:Evie (Torchickens)|Evie (Torchickens)]] ([[User talk:Evie (Torchickens)|talk]]) 11:52, 2 May 2024 (UTC)

Revision as of 11:52, 2 May 2024

??? type

This type (belonging to Curse in Generation II) is missing. I've also heard rumours that if you hack it as a damaging move, it causes some more unexpected errors. Something like it is neither physical or special? Needs confirming. Evie (Torchickens) (talk) 11:38, 2 May 2024 (UTC)Reply[reply]

Its index number is 0x13 in hex (dec:19). Evie (Torchickens) (talk) 11:50, 2 May 2024 (UTC)Reply[reply]
I also wonder what happens if you turn a Pokémon species' type into ??? and using an attacking move on it? Evie (Torchickens) (talk) 11:52, 2 May 2024 (UTC)Reply[reply]