Jump to content

Show your support for fixing the Dread battle MM


Recommended Posts

This needs to be fixed ASAP!!!! Why it is taking so long I have no idea, it has been broken for weeks now. Come on Devs sort it out!!

 

AMLH9UG.jpg

 

We couldn't even register because someone else did for us, I guess the same happened for everyone else!!

Share this post


Link to post
Share on other sites

I propose a temporary inter-corporate truce until this problem is resolved, the terms being that unless we play on our own dreadnoughts, we don't play dreadnoughts at all.

Share this post


Link to post
Share on other sites

I propose a temporary inter-corporate truce until this problem is resolved, the terms being that unless we play on our own dreadnoughts, we don't play dreadnoughts at all.

 

Won't work

Share this post


Link to post
Share on other sites

The update 1.2.1 will fix this problem.

For me, this would be more like a priority hot-fix, since this is a critical bug.

If the next update won't fully fix this problem, then I really see no excuses.

It boggles my mind, how can something, which works perfectly gets broken with the next update.

Share this post


Link to post
Share on other sites

For me, this would be more like a priority hot-fix, since this is a critical bug.

 

I totally agree, this is worthy of a hot-fix, as is contracts not auto-signing. 

 

What is the point of of getting organised then waiting for a total of about 30mins for no match. This sort of stuff royally pisses players off. 

 

Then again it may not be as simple as it seems, as I guess it has something to do with the incorporation of solo pilots being able to play dreads.

Share this post


Link to post
Share on other sites

@millanbel: That occured to me last night when I was speaking to G4, but a (big) protest is still needed where corporations come together to raise the overall awareness of the problem.

 

@Koromac: Simple. Instead of testing the feature first, they release the patch straight away and make a lot of customers angry.

 

@Wags: They need to remove that feature as much as they can and make it so that players only join teams that have wings, meaning no defense slots become occupied by a whole team of randoms. That's just straight up inconvenient and I'd rather play another team trying to get the sector.

Share this post


Link to post
Share on other sites

Personally, I am extremely surprised there hasn't been a priority hot-fix yet. The bugs with dreadnoughts have been widely known for several weeks now, and frankly, to let it go this long without a fix of any sort is quite inconsiderate and downright disgraceful of the dev team. They are destroying their own game by not fixing critical bugs such as this, bugs that ruin a huge aspect of the game. 

 

As much as I would love an inter-corporate truce for this, it won't work, mill is right. Even if we got every US and EU corp to boycott dreadnoughts until they are fixed, there are still a lot of RU corps who we couldn't communicate with or couldn't convince to join us in the boycott. I'm sure for them, the bugs are working out in their favor. (I mean, take Deft for example, we beat them yesterday in dreadnoughts, but since we used NIKA's dreadnought, and someone else used Deft's dreadnought, NIKA and Deft got to play for sector control in the tournament, and NIKA didn't even show up for the first phase of that sector fight). See below screenshot:

 

RBerWef.jpg

Share this post


Link to post
Share on other sites

or you could have go on Public Test servers and verify that it is indeed fixed or not instead of this

Share this post


Link to post
Share on other sites

or you could have go on Public Test servers and verify that it is indeed fixed or not instead of this

Public servers were very slow. To equip 1 equipment slot with some item I needed like 10 seconds!

I tested a lot of other features and I can tell you that the implant changes ruined the whole thing for me.

It is their game and their right, to do what they want, I guess.

 

As for dreadnought bug, if this glitch won't be fully fixed in the update 1.2.1, then I really have no words to describe this.

Fully written and posted bug reports just don't get fixed months after publication, so it wouldn't surprise me.

Share this post


Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...