Difference between revisions of "Version history/Upcoming"
From Pixelmon Wiki
Line 6: | Line 6: | ||
===Version 5.1.3=== | ===Version 5.1.3=== | ||
====Features==== | ====Features==== | ||
− | *Added | + | *Added Forfeit Clause to [[battle rules]] to disallow forfeiting |
*Added tiers to [[battle rules]] | *Added tiers to [[battle rules]] | ||
====Tweaks==== | ====Tweaks==== |
Revision as of 16:56, 13 July 2017
This is a list of changes to Pixelmon that have been confirmed to be in the upcoming version of Pixelmon.
Note: The Pixelmon team may choose to not reveal certain features and changes until the next version's release.
Version 5.1.3
Features
- Added Forfeit Clause to battle rules to disallow forfeiting
- Added tiers to battle rules
Tweaks
- Allowed number of Mew clones to be edited with a Pokémon editor
- Made boss Pokémon have maximum IVs and EVs
- Removed comments from default external JSON files
- Replaced several button selections with drop-down menus in the Pokémon editor, NPC editor, and chisel
Fixes
- Corrected Abomasnow's base stats
- Fixed battle crash when an NPC Trainer switches out with a move
- Fixed battle rules not importing clauses correctly
- Fixed battle rules resetting when the screen is resized
- Fixed battles causing errors when a client crashes during battle and rejoins
- Fixed crash with Berry trees
- Fixed
/endbattle
causing NPC Trainers to give out rewards multiple times - Fixed experience gain displaying incorrectly when sidemods change experience amounts
- Fixed Gym structures not being registered correctly
- Fixed Heat Crash and Heavy Slam sometimes dealing no damage
- Fixed Multiscale affecting Endeavor
- Fixed Outrage, Petal Dance, and Thrash lasting too many turns
- Fixed Power-Up Punch not being a contact move
- Fixed Regenerator animating HP restoration
- Fixed Regenerator not updating HP in the switching screen
- Fixed selected party Pokémon rarely changing when starting a battle
- Fixed Sticky Web failing when targeting a fainted Pokémon
- Fixed Transform displaying HP incorrectly client-side with the Raise to Cap battle rule