Search the Community

Hello. This thread came off the "Development of a PP Tier" thread. Essentially, it is a description for a clause that I dubbed the 'Easy Mode' clause that would be for beginners in standard battling. What it is: The Easy Mode clause is essentially a small list of banned pokemon that currently dominate the Standard metagame. These pokemon would be powerhouses and pokemon that are in general difficult to deal with. Why it does: New players in the competitive scene often find themselves overwhelmed by the amount of options there are available. What combinations will work? Can I use them? Will the just get beaten down? Unfortunately, because of the way this metagame is designed, new players without much experience in prediction will often resort to using the powerhouses of the metagame. These powerhouses are the tried and true pokemon that are the best of the best. They can sweep like theres no tomorrow. Banning these incredibly powerful pokemon would seriously open up the metagame for less used pokemon to fill in the spots. Why its useful: Allowing a new player to have a much more free selection of pokemon creates a much more new-player friendly metagame. If people can choose often overlooked pokemon on their teams and get used to the way they work, they can seriously get to know the odder pokemon in the Standard tier, and once they move off the Easy Mode, they'll have a much better appreciation for the less used pokemon and a much better understanding of strategy and prediction. Another reason it would be useful is it allows new players to easily determine other new players. Experienced battlers probably wouldn't enjoy Easy Mode very much, so newer players could fight other newer players at a fairly equal skill level. --- Randomspot made an excellent argument, and a revamping of the banlist is due: Proposed banlist: Tyranitar Salamence Scizor Latias Heatran Togekiss? Gyarados? Reasoning: What do you think of this clause as a whole? Please vote in the poll.

If you want the quick way to do this, here is a link to the Sword/Shield part of the Un-Nerf Compendium containing the patch and how to apply it :) Hey all! Once again, we have made some breakthroughs into ROM research, including removing Battle Tower restrictions and giving permanence / persistence to the Crowned Zacian / Crowned Zamazenta / Eternatus Eternamax formes! Ethical Disclaimer: Research was AI-assisted, but verified by me. Two small `.pchtxt` code mods for Pokémon Sword & Shield, for personal/offline use on emulator (built and confirmed on Eden v0.2.0, game v1.3.1). Both are tiny IPSwitch text patches - no ROM redistribution, you supply your own dump. Sword and Shield offsets included. --- 1) FormePersist - Crowned Zacian / Crowned Zamazenta / Eternamax Eternatus stay set Set the forme in PKHeX and it now persists through save + reload with no held item, and shows correctly on the team menu. SwSh treats these as battle-only formes and resets them to base on load; this forces the game's `IsBattleOnlyForme()` detector to return 0 so the reset paths never fire. It's the Gen-8 analogue of the Gen-6/7 Mega/Primal persistence patches. 2) NoTowerClause - Battle Tower species + item clause removed Lets you enter the Battle Tower with **two of the same Pokémon** and/or **two of the same held item**. SwSh's Tower has no banned-species list - the species clause and item clause are the entire restriction - so this lifts it fully. All other entry checks are untouched. --- **Install (Eden/Yuzu):** drop the title-id folder into `…\eden\load\`, e.g. `…\load\0100ABF008968000\NoTowerClause\exefs\noclause.pchtxt` (Sword) / `…\load\01008DB008C2C000\…` (Shield), then Properties -> Add-Ons -> tick it. (Make sure the GDB stub is off.) Patch contents (v1.3.1): FormePersist - `IsBattleOnlyForme` -> return 0: ``` Sword @nsobid-4628A512… Shield @nsobid-DBDDD138… 013AE910 00008052 013AE940 00008052 013AE914 C0035FD6 013AE944 C0035FD6 013AEC68 1F2003D5 013AEC98 1F2003D5 ``` NoTowerClause - force the per-slot duplicate-species & duplicate-item flags to 0: ``` Sword Shield 014F9654 08008052 014F96C4 08008052 014F965C 19000014 014F96CC 19000014 014F96DC 09008052 014F974C 09008052 014F96E4 1B000014 014F9754 1B000014 ``` Two Eden gotchas if you roll your own: `@enabled` is mandatory (without it Eden applies zero bytes), and use `@flag offset_shift 0x100`. Offsets are for v1.3.1 (build IDs above); a different game update needs them re-derived. Single-player/offline use - don't take these into pvp battle without your opponent's permission. (Bonus in the same folder: `DynamaxCandyAll`, a one-liner that lets you feed Dynamax Candy to the three legendaries. Actually letting them *Dynamax* is a RomFS personal-table flag - `CanNotDynamax` - i.e. the pkNX edit, not a code patch.) Here's the article explaining the in-depth reverse-engineering behind removing Battle Tower restrictions. And here's the deep dive into permanent formes for Gen 8. -IS2L *If there's any additional discoveries for Sword and Shield, I will just addend this thread so that I don't clog up the rest of the forums. Will make the title of this post reflect that.*