đŸ€Ź 😈 The BM report thread

4

Battle ID: 10481

When will this guy get a ban? :man_shrugging:t2:


4 Likes

Had the privilege to meet nagao 3 times today. 2/3 were dc’s
 @Dev_VKC How long are you going to ignore him?

Furthermore, what even is the point of rewamping the pvp log with battle codes if you’re not going to do anything about these anyway?

3 Likes

He never dc against me

Literally everyone who has played PvP for more than a month knows that Nagao disconnects the moment he starts losing.

If they would make a top 100 of disconnecting players, the legendary Nagao would definitely be #1.

3 Likes



Reporting this sore loser :index_pointing_at_the_viewer:t2:

Alternative Title: @Mr.X cosplaying Nagao the moment his Tenguko dies.


Battle id 635c5
Do they even check or we just posting like idiots?

I have suggested an easy solution: if you disconnect 3 times per 24 h , you won’t be able to access pvp for 3 days , disconnecting and reconnecting because of bad internet won’t be counted , to be counted it should be permanent disconnect and the game will be over , no bad network talk it’s your responsibility to have a good network, if you don’t avoid pvp untill you have a good internet , I’m sure devs can do this it’s easy and will solve the DC problems

1 Like

Sounds like a good idea on paper, but the false positives could run rampant. instead of just that, a list of disconnecters with a BM level (0-10) that would decide ban length. For example nagao, a lvl 10, would get days bans each time they exceed threshold. Whereas a lvl 5 would get a shorter ban, with a more lenient threshold.

This would protect users with bad connection to a certain degree, and not punish them like they’re actual BMs. There are other cases too like game crashing, phone shut off and not having enough time to reconnect, or one of those disconnects leading to “can’t reconnect” scenarios even though everything on players side is normal.

I know you said “only count real disconnects”, but you can’t always say which is which.

3 Likes

Let them bm. U enjoy your win.

1 Like

Your idea is excellent, even if and once from a ban for several days it would obtain a time counter, while the active counter is disconnected by connection error or by BM, automatically loses the PVP without the possibility of reconnecting

1 Like

Make it per season and ye got a deal

1 Like

Kinda like this. Except, it is easier to factor in then and dissuades disconnecting from the get go:

If you disconnect, you get a small timer where you’re basically banned from entering pvp for a period.

Lvl 1: 15 minutes(about the length of a long pvp match)
Lvl 2: 30 minutes
Lvl 3: 3 hours
Lvl 4: 12 hours
Lvl 5: week
Lvl 6: The rest of the season/month in case it’s the end of season

It’s supposed to discourage disconnecting bm, and you ‘level up’ with successive disconnects in a combo of your next let’s say 30 matches, and a hidden dev chosen timer if you somehow get 30 matches played in that dev chosen timer before starting to DC again.

This way, the ‘BM Checker’ can bonk you even if you play one match, wait a week to offset dev BM Check timer, and you still have 30 matches or so to go through legit and without salt otherwise you ‘level up’ your BM Check.

If you think it’s harsh, it’s probably not harsh enough then XD.

It should be very clear.

DON’T. BM. VIA. DC.

2 Likes


I don’t know if they check this as you say, but it frustrates me to have to wait because there are simply people who don’t accept their loss on FL


Battle ID: 16cb2

Traiganle una faldita a la niña

When will action be taken against players who disconnect when they lose? This Tavaray is supposed to be a “veteran,” but it’s a shame. He loses every time, and instead of changing this FD team, which isn’t good, he prefers DC. It’s very annoying.

and why when the game bugs and disconnects me from the fight and when I try to come back the message “the fight is over” it never takes 99 seconds but when people Dc I wait for at least two minutes

I want to denounce this funny man who waited almost a minute to then disconnect.
@Dev_VKC