JSON guide

The game uses the JSON format to store its data. Here is explained how it works for each object. The fields in italic are facultative.

OpMon

The OpMons are stored in opmon.json. Here is an exemple of the format:

{
    "HP":65,
    "atk":60,
    "atkSpe":30,
    "def":58,
    "defSpe":52,
    "spe":33,
    "evolution":{
      "level":28,
      "species":7,
      "type":"level"
    },
    "evs":[
      6
    ],
    "opDex":4,
    "types":[
      6,
      -1
    ],
    "captureRate":45,
    "curve":1000000,
    "expGiven":93,
    "height":0.5,
    "weight":20.0
}

Warning : the JSON file has been generated automatically the first time, to spare some time. The fields are not in this order, but JSON works anyway, no matter the order. This exemple has been sorted to make it more understandable.

Field list

• HP : The HP base stat (Number)
• atk : The attack base stat (Number)
• atkSpe : The special attack base stat (Number)
• def : The defense base stat (Number)
• defSpe : The special defense base stat (Number)
• spe : The Speed base stat (Number)
• evolution : Evolution data (Sub-type Evolution)
• evs : The EVs given when the OpMon is defeated (Stat Array, each stat corresponding to a number)
• opDex : The OpDex number of the OpMon. It determines the OpMon's name too, search in the key opmon.name.X where X is the opDex value. If you want to add an OpMon, don't forget to add its name in the keys files.
• types : The two types of the OpMon (Two types in an array, each type corresponding to a number)
• captureRate : The OpMon's capture rate. If it's low, the OpMon will be hard to capture, and vice versa (Number)
• curve : The EXP the OpMon will have at level 100 (Standard max EXP)
• expGiven : The base EXP the OpMon will give when defeated (Number)
• height : The OpMon's height (Number)
• weight : The OpMon's weight (Number)

Special Types

Sub-type Evolution

There is several types of evolutions. Every Evolution has the "type" field, which can be filled with the type name.

Type : "no"

"evolution":{
      "level":-1,
      "species":-1,
      "type":"no"
}

The type "no" means no evolution. "level" and "species" must stay to -1.

Type : "level"

"evolution":{
      "level":28,
      "species":7,
      "type":"level"
}

• level : The level at which the OpMon evolves (Number)
• species : The opDex number of the species in which the OpMon evolves (Number)