View Issue Details

IDProjectCategoryView StatusLast Update
0003787Return of ReckoningGeneralpublic2023-08-13 02:44
ReporterReturnOfReckoning Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionopen 
Summary0003787: Scenario flags bug
DescriptionReporter: Luranni

Sorry the screenshot didn't save. But there's a bug of some sort in this scenario that allows you to prevent the flag from being capped by a side, nobody on the flag except Destro, the flag bugs out and caps to order then can't be de-capped. I'll try and get another screenshot if I see it happen again.
TagsScenarios

Activities

ReturnOfReckoning

ReturnOfReckoning

2023-08-13 02:44

reporter   ~0006204

Commenter: gittoaster

It kind of sounds similar to the bug when a dead person doesn't release but he continues to build the Objective while dead. Did u notice any bodies there?
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 02:44

reporter   ~0006205

Commenter: vove-RoR

I am not sure if this is what you are talking about but if it is it is only visual.

Happened few times to me, flag was ours but standing on it caused the progress bar to empty and refill again. This is only visual and you get regular amount of the points over time and you don't receive the points for capture.

It looks like you would be able to recap the BO you have already capped.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 02:44

reporter   ~0006206

Commenter: Luranni

No there were no points being gained from the flag.

From: vove-RoR [mailto:notifications@github.com]
Sent: 17 January 2016 13:55
To: WarEmu/WarBugs
Cc: Luranni
Subject: Re: [WarBugs] Lost Temple of Isha flag bug (0003787)

I am not sure if this is what you are talking about but if it is it is only visual.

Happened few times to me, flag was ours but standing on it caused he progress bar to empty and refill again. This is only visual and you get regular amount of the points over time and you don't receive the points for capture.

It looks like you would be able to recap the BO you have already capped.


Reply to this email directly or view https://github.com/WarEmu/WarBugs/issues/3787#issuecomment-172322598 it on GitHub.Image removed by sender.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 02:44

reporter   ~0006207

Commenter: CornerbackAC

Same issue occurs also in other scenarios. Workshop-Flag in Reikland factory was capped by destru and we coulnd't recap it.

Also occured several times in temple of isha.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 02:44

reporter   ~0006208

Commenter: vove-RoR

It happened to me yesterday in Gates of Ekrund playing as destro and I can confirm it was only visual. We couldn't recap our flag, on map BO appeared as controlled by Order, the flag on the bo was also blue.

Basically Order controlled 1 point and the "bugged" one. Destro controlled mid only (that's how it appeared on map). Yet we were receiving more points than Order did and eventually won the match, thus I am sure the point we couldn't cap was already marked as ours and only appeared as belonging to Order.

It seems to be same issue as the one happening with BOs in RvR when you cap BO as Order and on map it appears as assaulted by Destruction, it also prints a message that the forces of Destruction were the ones to cap it, not Order, which is extremely confusing.

Not counting the confusion it causes it doesn't affect the gameplay that much.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 02:44

reporter   ~0006209

Commenter: CornerbackAC

No, the bug we are talking about is not only visual.

We lost Temple of Isha several times because the flag could not be tapped although we were dominating destru and stood around the flag.

Yet destru won as the flag ticked for them.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 02:44

reporter   ~0006210

Commenter: Torquemadra

Also seeing this on occasion, opposition controlled flag, no enemies around, bar rises as if control is to be relinquished and nothing happens, control remains with the opposition realm. No opposition players living or dead in the vicinity.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 02:44

reporter   ~0006211

Commenter: Evildoor

Possibly connected with lags / packet corruption / something like that. Had this bug today, there was a KotBS on a point who lagged for some time, then he disappeared and message was written that he disconnected uncleanly. After that, point was impossible to capture for destro, and captured itself for the order side when destro left it.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 02:44

reporter   ~0006212

Commenter: runebbb

just adding this
![baroz_007](https://cloud.githubusercontent.com/assets/20157418/18023409/29b2b800-6bf9-11e6-8a89-1e697db26693.jpg)

Issue History

Date Modified Username Field Change
2023-08-13 02:44 ReturnOfReckoning New Issue
2023-08-13 02:44 ReturnOfReckoning Tag Attached: Scenarios
2023-08-13 02:44 ReturnOfReckoning Note Added: 0006204
2023-08-13 02:44 ReturnOfReckoning Note Added: 0006205
2023-08-13 02:44 ReturnOfReckoning Note Added: 0006206
2023-08-13 02:44 ReturnOfReckoning Note Added: 0006207
2023-08-13 02:44 ReturnOfReckoning Note Added: 0006208
2023-08-13 02:44 ReturnOfReckoning Note Added: 0006209
2023-08-13 02:44 ReturnOfReckoning Note Added: 0006210
2023-08-13 02:44 ReturnOfReckoning Note Added: 0006211
2023-08-13 02:44 ReturnOfReckoning Note Added: 0006212
2023-08-13 02:44 ReturnOfReckoning Status new => closed