And you're under the presumption that this wasn't the case.
Again, you're missing the point about an UNEXPECTED thing arising.
It was not anticipated to be an issue, but unexpectedly it was. Therefore ruining their project management.
That's
precisely why good project management builds in contingency buffers: not because it can predict the exact issue, but because it accepts that something will go wrong at some point.
So no, I’m not assuming they
didn’t do any risk planning - but if a single unexpected issue was enough to completely blow past a public deadline with no alternative plan in place, that points to either a lack of sufficient buffer or overconfidence in the schedule. That’s not a moral failure - but it
is a planning flaw, and it's valid for the community to notice that.
Saying “this wasn’t anticipated, so it’s not bad project management” misses the point. Good project management doesn’t hinge on avoiding surprises - it hinges on absorbing them without letting everything slip.
Again, this is under the assumption that this UNEXPECTED scenario was something that was clearly evident and expectable.
It is most likely that the overall implementation was not seen as risky but this unexpected issue suddenly caused it to be out of nowhere.
I'm not assuming that the specific issue was obvious or “clearly evident” ahead of time. I’m saying that if any part of the project still depends on components that are
inherently unstable or prone to unexpected complications - then publicly committing to a date
without explicitly accounting for that risk is a misstep.
No schedule is risk-free. That’s why public dates - especially when self-imposed - need to be backed not just by optimism, but by a realistic appraisal of remaining uncertainties. If you leave no margin for error and something goes wrong, that’s not just bad luck - it’s a lack of strategic buffer.
So whether the issue was
likely or not isn’t the point. If it was
possible, it should have been part of the decision calculus before going public with a deadline.
Yes, but that's the thing. Any single hinting towards anything will ALWAYS lead to people assuming that said thing has been explicitly promised.
This is the nature of things. This is why developers have to be very careful of what they say, especially in regards to content that is in development.
I agree that developers have to be cautious with how they communicate - especially when features are still in flux. But transparency doesn’t require promising or even hinting at content. It can simply mean acknowledging
why a delay happened in more meaningful terms than “it’s not ready.”. Clarity doesn’t create false promises - it creates trust.
So yes, I agree: words matter. But avoiding
all specifics out of fear that players will misinterpret them often results in sterile, opaque communication, which can feel like a lack of accountability - even when that’s not the intent.
You quite literally accused them of "Dishonesty"
Just to be clear -
I’ve never accused the developers of lying or being dishonest.
If someone inferred that from what I wrote, then I’d like to clarify: my criticism was focused on
communication style, not
intentions. I’ve spoken about the
lack of clarity,
vagueness, or
incoherence that can emerge when dates are missed without meaningful explanations - but that’s not the same as accusing anyone of acting in bad faith.
At no point did I use the word
“dishonesty”, nor did I imply that the team deliberately misled the community. I’ve consistently argued for better communication, not because I believe the developers are untrustworthy, but because clear and responsible messaging is part of maintaining a strong relationship with the player base - especially when things don’t go as planned.
Please don’t attribute claims to me that I haven’t made. I’m here to exchange ideas and perspectives, not to question anyone’s integrity.
What's not straightforward about the update of "Patch isn't ready. It needs more work. We'll update you later"?
Yes, it doesn't say specifically what the exact issue is... But you don't NEED to know the exact specifics to know what is being communicated. That the content is not ready for release and needs more development time.
The message
"it's not ready, we'll update you later" is indeed straightforward in form - but what I’m pointing out is that, when it follows a missed public deadline,
that level of vagueness can easily come across as evasive, even if it’s not meant to be.
I’m not saying we need to know every technical detail - but when you set a specific timeframe and then miss it without offering any meaningful context (even at a high level), it
creates a communication gap. That’s where frustration builds, and it’s fair for people to feel that the messaging has become more about damage control than community transparency.
A good middle ground exists:
acknowledging what type of issue arose - without overpromising or naming specific features. That kind of honesty helps maintain trust, even in the face of delays.
Again, you seem to be under the assumption that they were NOT reasonably confident in being able to meet the deadline.
Again, I'll mention that it's most likely that they were entirely confident in meeting the deadline, hence them setting the deadline. With the only disruption to that estimation being an UNEXPECTED issue.
It's entirely possible they were confident internally. But confidence alone doesn't justify making a public commitment unless you’ve also factored in a buffer for uncertainty.
That’s really the core of what I’m saying: it's not that they
didn't believe they could meet the deadline - it's that when you go public with a specific date, you're assuming a communication responsibility. And if something unexpected does derail the plan, it’s then also reasonable for people to ask:
was that risk truly unforeseeable, or just underestimated?
Public announcements aren’t just reflections of internal confidence - they’re also promises to the audience, and with that comes the expectation of accountability if things don’t go as planned.
But... What else should they say?
You say that deep technical insight isn't necessary, but clear communication that doesn't involve it is somehow not enough?
Yes, it's generic. But that's because not everything is a wholly unique and special scenario. In this case it's quite a simple thing. Patch is not ready for the time being, thus they're delaying its release until its ready. They'll update us when they have news to share (Which is normally just "We'll announce a new release date when we figure it out")
I understand that sometimes the situation may be straightforward, and the patch simply isn’t ready.
However, clear communication isn’t just about stating the obvious; it’s about how you present it. Saying “the patch isn’t ready, we’ll update you later” may be factually correct, but it lacks the tone and nuance that make the community feel respected and included in the process - especially after a missed deadline.
Acknowledging that the delay is disappointing, explaining that the team is working hard to resolve specific kinds of challenges (without going into technical minutiae), or even just recognizing the impact on player expectations can go a long way in building trust.
So it’s not about providing “deep technical insight” - it’s about demonstrating accountability and empathy, which generic statements often fail to do.
But they haven't gone silent. They provided this update that says they're delaying it to work on it more.
Also, moderators aren't "Community Voices". They're moderators. They help manage the forums, ensuring people follow the rules and clean up threads. That's it. Outside that, they're simply any other forum user with their own independent views and opinions that are unrelated to any sort of relation to CDPR or the community as a whole.
I agree moderators are not official representatives of CDPR, nor do they speak on behalf of the company.
My point was more about the perception of silence or insufficient official communication - when official channels provide only minimal updates or no detailed context, players naturally turn to community voices (including moderator) to seek clarification or fill gaps.
This is less about who exactly those voices are, and more about the dynamic that emerges when people feel they don’t have enough information from official sources.
Clear, transparent, and timely communication from the developers helps prevent misunderstandings and speculation within the community. When that’s lacking, even well-meaning moderators or community members can become focal points for discussion - whether they want to or not.
Where have they gone radio silent?
They quite literally made an update. That's what this thread is. Them communicating the update.
That they haven't made any further updates simply suggests that there is nothing new to report. Unless you want a daily blog of them saying "Still working on the patch"
I understand that frequent updates on the same status might feel redundant. However, my point is not about the quantity of updates, but about the quality and clarity of the communication.
There’s a difference between saying “the patch isn’t ready, we’ll update later” and providing updates that help the community understand what challenges are being faced, even in broad terms. The goal isn’t daily status reports, but meaningful communication that balances honesty, transparency, and managing expectations - so that the community doesn’t feel left in the dark or dismissed.
Also, it’s worth noting that several days have passed since the June 26 update, and we still haven’t received any additional information or context beyond what was already communicated at the time of the delay announcement. This prolonged silence can unintentionally contribute to frustration and speculation, as the community is left wondering about the progress or challenges faced.
Regular, even if brief, updates that acknowledge ongoing work - even without new breakthroughs - can help maintain trust and reduce uncertainty.
Where's the weak communication?
THIS THREAD IS LITERALLY THEM COMMUNICATING!
I've experienced companies with weak communication. You know what they do? Nothing. Literally nothing. Never respond to anything. Something is delayed? No updates it just doesn't ship when it's supposed to and eventually drops sometime later.
CDPR have quite literally communicated that the patch is being delayed. A reason for the delay. Also, they mention that they will provide more communication later.
This is a far cry from any notion of "Weak Communication". We are not left in the dark. We know exactly what is going on.
I understand that CDPR made an initial update announcing the delay, and that is indeed a form of communication.
However, it’s important to note that this
first post is the only official communication so far - the same message that has been shared across various channels.
Since then, what follows in this thread are mostly community posts and discussions,
without further direct interaction or updates from CDPR or their official representatives.
In that sense, the ongoing conversation here isn’t really “communication” from the developers, but rather community members trying to interpret, speculate, or ask for more information.
True communication implies an ongoing dialogue or at least periodic official updates to keep the community informed, not just a single announcement followed by silence.
The crux is "Reasonable"
From my point of view, what they have done is reasonable. Since I understand the situation as it pertains to this announced content, I don't feel confused about what is happening, I don't feel left in the dark about what is happening, I am not left with a bunch of questions I want answered.
Yes, I am disappointed that the content was not ready for its stated release date. But I'm not going to lambaste them over it, because there's a myriad of things that can cause issues with meeting deadlines especially in regards to programming. I know I've had my fair share of deadline mishaps due to unexpected issues throughout my life.
Maybe I'd be less lenient if this was an ongoing trend... But outside the initial game release there hasn't been any issues like this. Phantom Liberty and all prior patches released without unexpected delays. So I would not consider 2 hiccups 5 years apart to be a "Trend" (No, I'd consider something like Blizzard patches to be a trend... Where EVERY SINGLE ONE has issues and has done forever). Even more so when you consider the overall development turmoil surrounding the initial release.
Holding developers to a reasonable standard of communication and accountability
is not about harsh criticism or hostility - it’s about fostering trust and showing respect for the player community’s investment and opportunities to strengthen that trust through clearer, more transparent communication - especially given the scale of interest and passion around the game.