- 35
- Posts
- 4
- Years
- Seen Mar 19, 2025
[Pokémon Essentials version 20.1]
Exception: RuntimeError
Message: Undefined value COUNTER in GameData::Evolution
File PBS/pokemon.txt, section , key Evolutions
VAPOREON,Item,WATERSTONE,JOLTEON,Item,THUNDERSTONE,FLAREON,Item,FIRESTONE,LEAFEON,LocationFlag,MossRock,LEAFEON,Item,LEAFSTONE,GLACEON,LocationFlag,IceRock,GLACEON,Item,ICESTONE,SYLVEON,HappinessMoveT...
Backtrace:
380:Compiler:345:in `checkEnumField'
380:Compiler:320:in `csvEnumField!'
380:Compiler:523:in `block (2 levels) in pbGetCsvRecord'
380:Compiler:415:in `each'
380:Compiler:415:in `block in pbGetCsvRecord'
380:Compiler:413:in `loop'
380:Compiler:413:in `pbGetCsvRecord'
381:Compiler_CompilePBS:633:in `block (3 levels) in compile_pokemon'
381:Compiler_CompilePBS:626:in `each_key'
381:Compiler_CompilePBS:626:in `block (2 levels) in compile_pokemon'
I'm trying to make it a level with move evolution like Mamoswine, Yanmega,etc. but with Counter. The really confusing bit for me is that when I swapped it out for Rollout to see if it was an error with Counter that also threw up the error.
Exception: RuntimeError
Message: Undefined value COUNTER in GameData::Evolution
File PBS/pokemon.txt, section , key Evolutions
VAPOREON,Item,WATERSTONE,JOLTEON,Item,THUNDERSTONE,FLAREON,Item,FIRESTONE,LEAFEON,LocationFlag,MossRock,LEAFEON,Item,LEAFSTONE,GLACEON,LocationFlag,IceRock,GLACEON,Item,ICESTONE,SYLVEON,HappinessMoveT...
Backtrace:
380:Compiler:345:in `checkEnumField'
380:Compiler:320:in `csvEnumField!'
380:Compiler:523:in `block (2 levels) in pbGetCsvRecord'
380:Compiler:415:in `each'
380:Compiler:415:in `block in pbGetCsvRecord'
380:Compiler:413:in `loop'
380:Compiler:413:in `pbGetCsvRecord'
381:Compiler_CompilePBS:633:in `block (3 levels) in compile_pokemon'
381:Compiler_CompilePBS:626:in `each_key'
381:Compiler_CompilePBS:626:in `block (2 levels) in compile_pokemon'
I'm trying to make it a level with move evolution like Mamoswine, Yanmega,etc. but with Counter. The really confusing bit for me is that when I swapped it out for Rollout to see if it was an error with Counter that also threw up the error.