r/TheSilphRoad • u/SilentKiller2809 South East Asia • Aug 10 '25

Discussion Raiding is RUINED

With the 200m raid joining "exploit" getting patched, raiding as we knew it has been ruined.

1) The raid ended in the overworld, but if you are in the lobby (120s) or if the battle has already started, you could do the raid no problem. Now if you try to heal your pokemon by exiting out to the lobby, or if they all faint, you'll get kicked

2) If you happened to be in the lobby when the boss dies, you would just automatically get to the "raid win" screen and get the encounter. Now, nothing happens automatically, okay, not the end of the world. But rejoin battle doesnt work either. The raid timer keeps counting down in the lobby, even though the raid has been defeated by other players, you think ok once it gets to 0 it will realize the raid has been won and give me the encounter. No, nothing happens. If the raid is over you don't even get the raid "rewards", much less the encounter. And you just wasted a pass and revives + potions.

And this is all in 3 raids. I was planning to go join my nearby community meetup around 2 pm to do atleast 30 raids, and do the active raid at my home gym in the meantime. This is a nightmare. Raiding is the thing I enjoy most and it has been ruined for me. Not to mention they keep recycling these origin forms with only a "chance" at the moves and apparently they are not even shiny boosted this time.

909 Upvotes

78% Upvoted

275 comments sorted by

View all comments

716

u/TheRealHankWolfman UK & Ireland - Yorkshire - Mystic - L50 Aug 10 '25

The first one was happening long before the trick was patched. You shouldn't do raids close to the boss refreshing unless you're sure you can beat it without your team fainting.

375

u/Substantial_Mix_1634 Aug 10 '25

Doesn’t that just amplify the fact that they should be fixing problems like this that actually matter?

271

u/dod6666 Wellington NZ Beta Tester Aug 10 '25

Yes, there is no excuse for that bug being in the game as long as it has been.

Hell there is no excuse for booting players from a raid after they have joined and burned their pass at all.

75

u/Substantial_Mix_1634 Aug 10 '25

Yeah and support is usually useless because it’s all done by some bot. I’ve gotten raid passes back after being kicked out, but you have to be very specific with what you say the problem is (I say it’s a purchasing error with it not working as intended rather than a raid error) otherwise support will say that partaking in the raid and receiving the rewards is what matters and that the encounter is just a “bonus” so they can’t compensate you. It’s a piss take. Anyway rant over

19

u/OGShiGuy Aug 10 '25

Yeaa, I’ve found this to be true as well. Don’t put it under raid error and I feel like you’re more likely to get compensation.

3

u/chefhero93 South East Asia Aug 11 '25

also never compile errors. submit a ticket for each otherwise they'll say their limit is 1 and you've been compensated after they give you the 1 despite losing 2 or more.

6

u/Substantial_Mix_1634 Aug 10 '25

Exactly. They’ll just ignore everything you say if you say it’s a raid error.

11

u/AutisticPenguin2 Aug 10 '25

Yeah I think raid errors are basically just ">is ticket submitted? >deny ticket". I've not seen the bot actually put out yet, no matter how many legitimate complaints I have.

14

u/Substantial_Mix_1634 Aug 10 '25

I can’t guarantee it will work but, for remote passes for example, I’ve had more success raising it under purchasing help and saying it didn’t work as intended/advertised. I usually get a remote raid pass back the next day.

3

u/chefhero93 South East Asia Aug 11 '25

usually that's the only way to get actual support. if you file a claim under raid issues, then a bot will just say you have no issues or already been compensated.

2

u/rubber_psyducky Aug 10 '25

Thank you for the advice!

-7

u/ManagerHot8709 Aug 10 '25

But this also is an old problem that most raid players have adapted to. And forget bugs, if you somehow fail the raid, you'll be screwed regardless.

9

u/Substantial_Mix_1634 Aug 10 '25

What’s your point? It should still get fixed.

-8

u/ManagerHot8709 Aug 10 '25

My point is that there is a point where the player is also the problem.

13

u/Substantial_Mix_1634 Aug 10 '25 edited Aug 10 '25

If you’re able to use a raid pass and join a raid, the game shouldn’t kick you out and let you waste it. End of

25

u/Jazs1994 Aug 10 '25

This was before the patch fix but only like 3 months ago. Last time I did a short timer raid and had to relobby because of fainting out it was fine, didn't get kicked out or anything

4

u/Elect_Locution Aug 10 '25

Easier said than done. I'll host a raid, it'll take 10-30+ minutes waiting for my lobby to be up, 1-3 minutes to get people ready. The options are either repeat the process and hope for a better timed raid (if I can find one), or roll the dice on it going smoothly. I can't tell you how many times I've nearly been able to start a raid, but it'd end just as my lobby is ready.

1

u/Ok_Sea8789 Aug 12 '25

This is why I only create lobbies while it's still an egg. The queue time is too long on PG. They should make them shorter. I'd rather be timed out sooner than be disappointed after nearly an hour kol

1

u/chefhero93 South East Asia Aug 11 '25

yeah. same with no. 2

1

u/Vivid-Speed Aug 11 '25

I’m confused- if my pokemon faint, I have always and still have the option to heal. I’m not sure what OP is talking about? Am i missing something ?

7

u/TheRealHankWolfman UK & Ireland - Yorkshire - Mystic - L50 Aug 11 '25

During events where raids are constantly back to back (such as raid days), the coding of the game is a little bit wonky. For whatever reason, if you're in a raid and all your Pokémon faint (or you manually attempt to go back to the lobby to heal up), if another raid has started on that gym, you will get booted from the raid you're doing instead of being allowed to heal up and continue battling.

3

u/Vivid-Speed Aug 11 '25

Gotchya. I’ve never experienced that. But I would be annoyed as hell if I did. Thanks for the info!

1

u/Western_Toe553 Aug 11 '25

I'm new to this as well. So are you referring to exiting an active raid to heal up, but the current "round" ends and a new one starts before you make it back in?

4

u/TheRealHankWolfman UK & Ireland - Yorkshire - Mystic - L50 Aug 11 '25

So let's say I get into a Palkia raid that has 2 minutes left before it despawns. Part way into the raid battle, it would despawn, and let's say it gets immediately replaced with a Dialga raid, as the raids pretty much instantly refresh during raid days. I'm still battling the Palkia raid at that gym though. If at any point my entire team faints after the Dialga raid has started at the same gym, or if I manually press the run button in the top left to attempt to go back into the lobby and heal up, the game will get confused because I'm in a raid that isn't the raid that's currently on the gym, and it'll kick me out because the Palkia raid no longer exists, even if there are still players actively battling that instance of it.

Under normal gameplay circumstances this wouldn't be an issue, as there's nearly always a gap between one raid ending and another one popping up. Even during raid hours on Wednesdays, there's a 5 minute gap which allows for a previous raid to be finished without the next one having started. During raid days though, this gap doesn't exist, and the programming of the game is not good enough to account for this.

-17

u/SilentKiller2809 South East Asia Aug 10 '25

Yes but in my experience it was a low chance of it happening. Now it seems to kick you no matter what, 4 players were in that raid everyone got kicked

28

u/majaaaaaaa_ Aug 10 '25

That's been on for a good while now, learned about it the hard way. Don't get into a raid unless there's at least 10 mins remaining, of course this doesn't apply if you're sure you can end the raid quickly without your team fainting.