Ephinea PSO Wiki:Enemy Stats
From Ephinea PSO Wiki
There's a lot of enemy stats in the game. Adding them all is annoying. If you want to help out, follow these steps.
- Get this zip and extract it somewhere. Keep track of the file names: the
_on
suffix means it's for multiplayer mode, and no_on
suffix means it's for singleplayer (or One Person) mode. The_lab
suffix is for Episode 2, the_ep4
suffix is for Episode 4, and no suffix means it's for Episode 1. - Open the BP Editor exe and pick a file. If you're starting from scratch for an enemy stat, you'll want to start with either the Episode 1 multiplayer file (
BattleParamEntry_on.dat
) or the Episode 1 singleplayer file (BattleParamEntry.dat
). - Using the nhpon template as both a style and enemy name reference, fill in the template of your chosen stat.
- The formatting of the template name is Template:[
difficulty
][stat
][on/off
], wheredifficulty
can ben
for Normal,h
for Hard,vh
for Very Hard, andu
for Ultimate. stat
can be the name of any of the stats as displayed in the BP Editor. We're not keeping track of Range1, Range2, HP2, TP, or any of the attack/movement parameters, so don't bother adding those.on/off
ison
if you're working with a multiplayer stat, oroff
if you're working with a singleplayer (One Person) stat.- An example template name is Template:Uespoff for enemy ESP in One Person mode under the Ultimate difficulty.
- The formatting of the template name is Template:[
- You can skip enemies that have a stat of 0 and they'll be displayed as 0, provided you follow the template to a T. Just don't forget the
| 0
at the end of the reference template. - If two enemies have the same stat, you only have to write the actual stat once. This is kind of complicated and not really useful unless the enemies are right next to each other, and it looks like this in the template:
| Sinow Beat
| Sinow Gold = 100
- In this example, the Sinow Beat's stat will also be recorded as 100.
That's about it. There's a bit of cleanup to do on another page, but we can take care of that. If you have any questions, contact Ryan or Matt, since they're both kind of alright at explaining this, sort of.