seeing bunch of long post by malice , i wind up all things im doing , take a drink and on my poach i relax my self and taking a long breadth start reading it

im gonna screenshot your post milan and whenever i and aister clash again over the issue that devs are concentrating more on sm then bd which has affected bd ill show him ur post
thanks

Btw, some of you know the bug where people should have landed on the op but backed at 00:00 and managed to turn but with +1 tick longer (The time and reason our friend and PRESIDENT OF BD NIKO went full rage mode) no one moved a finger about that one (only NIKO getting banned)

To add, many people abused it!

Perhaps because that one can't be done on purpose. Unless you manage to control the BD server and time your turn up to the microsecond and you are lucky enough to exactly turn between the time it takes the server to process the taking of OPs/battles/and the landing sequence

Milan, due all those server maintenance it wasn't a hard thing to do. Isn't that abusing? I actually did it couple of times just for fun

Really now? I never managed to do it and only saw it happen 3 times in all my time on BD. But yes, I agree that is a bug that needs to be fixed as well. Only that bug is one where you can't do it on purpose (at least I didn't think so) whereas the floating OP bug is.

Fear me.



Not every bug is even considered for removal as well. Some are too much of a hassle to fix. For instance, the bug that if a conquer starts to rebel, but the conqueror doesn't refresh his browser, you can still force relocate them. There is also the bug with ions, much in the same manner. If you don't refresh when multiple are happening, there is a chance you will double ion 1 squad and it will instead be 2 ticks behind (which means you essentially wasted 250 energy).

However, this particular bug, I'm not sure if it can be fixed. There are already parameter's to prevent it from happening (the fact that there are no build areas). This bug is finding a loophole in the system's ability to prevent it by different means, which essentially allows for a total bypass in all cases. I will of course, not explain what that process is, as we don't want even more abuser's to use this means.

I did and I saw a lot of people doing it a lot of times, it was pretty easy to do while the maintenance thing was happening all the time. http://prntscr.com/57z67c If that camp get's deleted, I'm 100% sure you can plant the op again. You call it a bug but it isn't

I'd be fine with it being deleted so we can settle this discussion. But here's what I can see from trying to simply test OP making ANYWHERE on the map.



I could not get an exact centering on the OP that was built, though, I could get pretty close (as seen in the above screenshot). However, pretty close is NOT the same as exact, and the OP is built exactly centered. Not barely to the left or right. EXACT center. While I can say there was the possibility of an OP being allowed to be placed there, you can CLEARLY see the huge overlap from the other OPs. I played around all morning since seeing this with OPs all over the map. The screenshot next to it is the closest to other OPs and the furthest overlap I could possibly get. Pretty simple rule of thumb; you can't overlap more than halfway through another OP. You can very clearly see this OP WAY overlaps 2 of the OPs in question.

EDIT:
I decided to try with 2 of the same OPs instead of just using 2 OPs and came up with the following screenshot



Still couldn't get an exact centering on the OP that was placed, but as you can see, very close. If we get nitty gritty here, I still believe that too much overlap occurred on the llll OP, BUT I will admit that it is a very close scenario with room for error here.

This is preety funny considering last era, the same players exploited a bug to kill a sizeable portion of GML's army, and at that point they weren't complaining about it at all

Malice, it wasn't about the distance to other OPs, it was about the fact that they exact spot it supposed to give "cannot build on water" error.



Wait, what bug did we exploit to kill a sizeable portion of GML army? And I'd have to disagree with "the same players", since I was called out by many from last era that I was playing against VND and their old subs.