Project Bronze Forever Auto-Catch Hubs

Auto-catch hubs are the second script family around Project Bronze Forever. Where Umbra Hub moves you, these stacks play the game: find a spawn, start the fight, throw a ball, dump the catch, heal, repeat. This page names the usual modules so you can recognise a screenshot. It does not include a paste, an executor, or a host URL. Read script safety before you even test a toggle on an alt.

Roria is large and the shiny rate is still a shiny rate. That is the sales pitch. The cost is that auto battle touches combat, inventory, and PC APIs the revival already watches. Copies get taken down for platform reasons. Files also get punished for looking like a farm. Data is designed to persist, which is a warning as much as a comfort.

Modules you will see on a panel

Auto finder. The client scans nearby tiles or spawn tables and walks or teleports you toward a match. Combined with a species filter it becomes a Dex filler. Combined with a shiny check it becomes a hunt. Finder loops are loud: unnatural pathing, instant turns, and the same grass patch for hours.

Shiny wishlist. You tick species. The stack ignores everything else, including useful random shinies you might have wanted. A wishlist that includes a legendary bird or a static Regi is how people KO a one-chance encounter because the battle module used the wrong move. Turn autosave off for statics. A script will not remember that for you.

Auto battle. The fight driver. It chooses Tackle or a type-colouring move, throws a ball from a list, and runs if HP is low. Fine for Magikarp. Catastrophic for a Volcanion or Victini static if the ball table is empty. Never point auto battle at a set encounter you cannot reset.

EV training. A loop that kills the same species for HP, Attack, or Speed EVs, then heals. This is the ‘I will be here overnight’ module. It is also a perfect report pattern: one account, one route, no chat, hours of identical battles.

Heal and PC. After a catch or a faint, the stack opens a healer or dumps into a box. Full boxes halt the loop. People think the script ‘stole’ a shiny when the PC write failed during a copy hitch. Check boxes by hand after any overnight run, then stop using overnight runs.

Repel, speed, noclip. Quality of life borrowed from movement hubs. Repel keeps trash spawns down while you hunt one species. Extra speed and noclip get you through geometry the finder cannot path. Those extras make an auto-catch stack look even less like a player. See Umbra for what speed and deletes already risk on their own.

What auto-catch will not fix

It will not redeem 4KCHEF or T0X1CB4G0N. Use the real codes box. It will not pick a good starter or teach you controls. It will not hold a Z-Crystal hunt. It will not trade for you in the Trade Resort. If the current place is down, no amount of finder logic helps; that is game status.

Wishlist entries for Rotom or Eeveelutions still need the overworld method. A stack that only reads wild grass will never open a washing machine or an evolution stone NPC.

Ban, desync, and the alt rule

Project Bronze Forever has used anti-cheat. Auto battle plus noclip is a signature. Outcomes people report: kick, ban, rolled-back Dex, empty party, or a file that loads into a black map after the next re-upload. Because progress is meant to carry across copies, assume a punishment can carry too.

If you still run a stack:

• Alt only. Never the file with gym badges you care about.
• No Trade Resort, no Colosseum, no live codes on that alt.
• No static legendaries on the wishlist.
• Watch the first twenty battles yourself so you know the ball table is not empty.
• Stop when Discord says a new copy is going up. Scripts and place IDs do not migrate cleanly.

The scripts hub exists to put this next to Umbra so you do not mix a movement cap of 30 with an overnight EV farm and call it ‘quality of life.’

If you still run an auto-catch stack, park it on an alt, log every shiny, and assume the session can end without warning. That is the only honest way to use these hubs.