Thump

So you're saying AAA companies who have hundreds of people could simply do it with 3 and a hamster? Might want to let UBIsoft in on this, they are struggling.

Both sentences have nothing to do with each other. And I never said he couldn't be happy...so THAT statement is simply not true.

The distraction eats resources better spent elsewhere. It is costing the community, just not in money.

At that point, it's no better than a random mod maker. Will be equally accurate.

It exists for the sole purpose of distraction. Jingle the keys.

The sheer amount of BS magic dust they are going to have to douse this module in will be meme worthy.

2052 And beyond* We're still waiting for 2016's dynamic weather and a decade's worth of other promises. Why can you not set realistic expectations?

Wow

This should have never been an issue to begin with when it was submitted for initial approval.a. As a customer, I saw the overlap IMMEDIATELY. They all (ED & ORT) should have seen this issue comming from a mile away and never released it with that content. They also can't just take away what was sold at time of purchase. That would be the equivalent of chevy taking your tires back from your truck because Ford had them first a year after you bought your vehicle. To top it off, they either tried to hide/ignore the move or they are incompetent in communication. Any way you slice it, ORT, ED, And now Urgas are ALL in the wrong.

Everyone's asking why now and in good DCS fashion both ED and Third parties are not being transparent. The fact that they were allowed to implement it at all is a clear sign of a systems failure on ED's end as the corporation leading these sales. This is especially a problem if ED is going to absolve itself from 3rd Party actions after initial approval. What we are seeing is a symptom of a greater problem that has existed in DCS's ecosystem for years (decades?) now. It's still there and that was the main point. Overlapping terrain. And who knows...maybe there are plans to expand into that area (if we're going that route)

Please don't defend an exceedingly poor move by the dev.

Didn't appear so, but if you're walking the original statement back, then ok.

You said it was to not step on toes...how is this a surprise & that you don't have info on this decision?

It is not a bug and can VERY loosely be defined as a "problem" if you're looking to stretch the meaning of the term. Putting it well behind the sections takes the issue out of the view of any potential customers as they are less than likely to go there than those who currently own the product. If their intent was only to consolidate, then that thread should have been pushed forward to the forefront, mine merged into it, and pinned. And you are right, this isn't ED's first time.

I'm not in your discord. Also, I'm not talking about THIS thread specifically but the one I made which was apparently too much in public view to remain where it was. Thanks

Not a huge fan of hiding threads through merging to avoid bad publicity. A large chunk of the map was removed. Exceedingly poor form by the developer. This should have been communicated immediately once the decision was made, not dropped on the community without warning nor addressed in the patch notes. Unsat x2

This is not a bug, please do not intentionally hide the thread to avoid bad publicity.

Taking away parts of the product after selling it is VERY poor form. The map should not have had a large chunk removed. This happening a year+ after release is even worse. Unsat

This is a terrible take

While there is frustration at the last second "no jump tonight," I will give credit where it is due. This level of open communication as presented in the newsletter is exactly what is needed. The hope would be to see an earlier call made to delay if needed with a newsletter providing insight as to the challenges faced by the development team. Early calls with explanation to provide context would go a long way to rebuild trust & goodwill.

Back to the topic at hand.... The delay is simply a matter of course due to the rushed nature of the module's release. Is it good that they delayed it, yes. Should it have unfolded in this manner, no. Much like the Viper's impact on the Hornet prior to its release, the community could see the warning signs before the company (was willing to publically admit). This speaks to a core issue.

Calm your tits. I have praised them when they've done right. It's a difference between having standards and not.

ED can do no wrong (or improve) apparently.

Still not a complete module.

It's cute you think it'll be a complete module in a year, you sweet summer child.