Nuzlock Ruleset

Description

Source: https://github.com/Ordalca/Nuzlocke/

Posting on Curseforge with the permission of the original mod creator Ordalca via the pixelmon discord. 

This project adapts the Nuzlocke Pokémon Challenge for Pixelmon. Nuzlockes typically operate under 2 main rules:

1. Only the first Pokémon per route can be caught
2. Any Pokémon that faints is "dead" and must be released or permanently put in the pc

The configuration file for this mod is located at config/pixelmon/nuzlocke.yml


The following options can be enabled:

1. first-encounter-restriction
   • Only the first Pokémon fought or captured for each biome can be caught
     • (true/false)
2. dupes-clause
   • Encountering a previously caught species does not count as a first encounter
     • (true/false)
3. shiny-clause
   • Shiny Pokémon can always be caught
     • (true/false)
4. pvp-death-enforced
   • Battles between players cause the faint penalty for any fainted Pokémon
     • (true/false)
5. faint-result
   • Result of a pokemon fainting
     • FAINT (Pokemon faints and can be revived using healers or beds)
     • DEAD (Pokemon faints and cannot be revived)
     • DELETE (Pokemon is deleted from the user's party upon battle's end)
6. wipe-result
   • Result of the full team fainting:
     • NONE (No penalty)
     • TELEPORT (Player is teleported to last healer/bed, equivalent to Teleport external move)
     • DEATH (Player is killed, can be used with Hardcore mode to run true Nuzlockes)
7. bag-use
   • Rules for use of items in battle:
     • UNRESTRICTED (All items permitted except for Revival items)
     • NOHEALS (Prevents HP and Status restore items)
     • NOITEMS (Can only use Pokeball section in battle)
8. block-master-ball
   • Prevents the use of Master/Park/Origin balls
     • (true/false)
9. block-in-battle-stronger
   • Prevents player from catching overleveled Pokémon in battle
     • (true/false)
10. stronger-threshold
    • Level difference allowed above strongest Pokémon, determines what "overleveled" means
      • integer values
11. block-out-of-battle-legends
    • Prevents player from catching legendary Pokémon outside battle
      • (true/false)
12. block-out-of-battle-mythical
    • Prevents player from catching mythical Pokémon outside battle
      • (true/false)
13. block-out-of-battle-ultra
    • Prevents player from catching ultrabeasts outside battle
      • (true/false)
14. block-out-of-battle-stronger
    • Prevents player from catching overleveled Pokémon outside battle
      • (true/false)
15. elite-trainer-pokemon
    • All trainer Pokémon have max IVs and max EVs in every stat
      • (true/false)
16. trainer-skill
    • Sets trainer battle AI levels
      • STANDARD (Levels match those set in battle.yml)
      • MIXED (Randomly picks between aggressive, advanced, and tactical AIs)
      • AGGRESSIVE (Trainer will use the move that deals the most damage to the opponent, avoiding status moves)
      • TACTICAL (Trainer knows how to use status moves, but will not switch)
      • ADVANCED (Trainer knows how to use status moves and will switch Pokémon if advantageous)
17. pokemon-aggression
    • Sets pokemon movement AI
      • TIMID (All Pokémon attempt to avoid the player)
      • PASSIVE (All Pokémon are passive)
      • STANDARD (No Changes, based on other configs)
      • ENCOUNTER (All Pokémon constantly hunt players until the "first encounter per biome" of the nuzlocke occurs)
      • AGGRESSIVE (All Pokémon constantly hunt the players, similar to hostile mobs in Vanilla)

What means Verified?

• Compatibility: The mod should be compatible with the latest version of Minecraft and be clearly labeled with its supported versions.
• Functionality: The mod should work as advertised and not cause any game-breaking bugs or crashes.
• Security: The mod should not contain any malicious code or attempts to steal personal information.
• Performance: The mod should not cause a significant decrease in the game's performance, such as by causing lag or reducing frame rates.
• Originality: The mod should be original and not a copy of someone else's work.
• Up-to-date: The mod should be regularly updated to fix bugs, improve performance, and maintain compatibility with the latest version of Minecraft.
• Support: The mod should have an active developer who provides support and troubleshooting assistance to users.
• License: The mod should be released under a clear and open source license that allows others to use, modify, and redistribute the code.
• Documentation: The mod should come with clear and detailed documentation on how to install and use it.

How to Install