Game mode: [PVP official: (Online official ]
Type of issue: [Enter one of the following: | Bug exploit]
Server type: [Enter one of the following: PvP
Region: [eu official pvp server #1131]
I think you know about the out of raid time abuse, please check logins on server official pvp #1131 on 14/9/18, you will surely be able to see who the culprits are and ban them! although I don’t actually expect you to act…
This sounds like it could be a time zone issue i have a NA dedicated server and tried setting my purge times as in my time zone before realizing they were set off a different time zone. So had to figure out the time zone they were set on and adjust my times from there so you could see them as raiding on non raid times to ypur time zone but they could be on during raid times. Just a thought could be wrong though
it’s not a timezone issue, these guys did an all nighter, place bombs, ignite and log off or suicide before it explodes and you get out of raid hours damage, we tested it as soon as we heard about this bug, which is on youtube btw…
I was told it worked in pve so i tested in a pve c server with my friend and we couldn’t get it to work.
it clearly works as our base was raided in PVE time.
They need to Sort this out ASAP or whats the point.if devs need relevant steam names of the offenders this is not a problem !!
I wont be playing again until this is sorted ,consider it uninstalled
in pve time? what type of server? what platform?
read the beginning of the thread man its all there
I did. I think if you read my original reply you will see that it appears you didn’t read it in full or understand.
but now I do understand your reply after re reading your original post.
sorry but that makes about as much sense as a chocolate fireguard. lets keep it on topic ?
ok chocolate fireguard I will spell it out.
on topic:the exploit mentioned in the original post. You know the one about bombs, signing off line and such." with me so far?
it was stated by some on reddit to work in pve and pvp servers. Not just pvp. still with me?
I tested in a pve-c server and it did not seem to work there. Have I lost you?
If the topic is your personal issue and not the exploit in general I apologize for getting off topic.
had a rad day sir.
wheres the block/mute button on here? lol
Damn there isn’t one ……Ignore mode activated
I’ve only seen it happen in pvp server so can’t say anything about a full PVE server.
what? I’ve not withdrawn it, is this some kind of censorship?
You must have by accident as just calm down as I did it one time by accident as well.
and @Saxon1 see above reply and as a FYI on your own comments, consider the following
Please don’t tell people how to use exploits. This causes more problems and confusion than needed, instead
If you think something is an exploit, report it using Found an Exploit? We'll pay you for it!
If there’s major harassment use Harassment and Griefing Issues
Alternatively, if you have any other issues, they are also pinned on the same Players Helping Players subforum.
“I wont be playing again until this is sorted ,consider it uninstalled” - Whoopass
That will actually be the best improvement that server can get 
Official server 1322 is being cleared by ppl in non raid time windows aswell. Nothing shows up in the logs, they use explosives in combination with something i wont explain (or know in detail). I witnessed it live at 02:00 servertime from saturday 15th to sunday 16th on another clans base - and last night on our own base.
If you let those ppl get away, your product is ruined. Fixing it is one thing, banning the ones who used it is a must if your policies and marketing should be worth anything.
Until you react accordingly: i can only refrain from using your companies products. Using something like this cannot be explained away by the users when it contrasts a major feature of your game - the raid time window, which is self explanatory even if you would use this exploit by mistake - but continue using it.
well, a hotfix was released, was it sped up by people making this bug common knowledge? guess we’ll never know, I suspect it was.