Leaving Colonization Events broken for synthetics at release, Really?

So am I really the only one who thinks going to release with this broken is a bad idea?

Very strongly agreed indeed. At least remove the Yor then patch them in. Releasing with broken features is a way to get very bad press.

Honestly I think just change the events that can't generically apply to synthetics and non-synthetics until they can add some filtering in a patch. be a bigger shame to remove synthetics altogether. But I agree even removing synthetics for now would make the game look less unfinished to reviewers.

Yes releasing with a broken faction is bad. Take it out and release as dlc when it is fixed

You don't think removing a faction because of fluff is a bit overkill?

Edit: I agree that a game feels better when everything in it tells a cohesive story, but cutting a huge piece of content from the base game because the writing doesn't match their fluff won't make the game better.

And given that there are game play bugs and balance issues still being worked on there are bigger fish to fry imo.

I do I'd actually rather they just implemented a solution or failing that replaced events that couldn't apply to any race.

It's not in anyway fluff, not only do many of the descriptions make no sense for synthetics and so make the game appear broken many of the negative and positive effects of some events dont impact them meaningfully either. So yes I view the event system as broken for synthetics at the moment and I don't see the event system as fluff. I doubt reviews will fail to notice or mention it.

Which stream was this mentioned in?  I don't recall hearing it last week.  And as one of the first people to bring this up, while I'd be disappointed that it couldn't be addressed by launch, calling for the Yor to be removed is EXTREME overkill, as ultimately all but a couple of colonization events are mostly fluff In regards to this issue. There's only a couple where it matters mechanically, IIRC.

Yes, it would be great to be addressed, but calling it "broken" is overly dramatic.  

Gamers will whine about anything in reviews though, as the so-called controversy in regards to Pillars of Eternity shows.

Will it be perceived as a negative? Sure.  I'll agree with that.  Game breakingly so?  Not remotely.  This is something that can be addressed by a patch post-release, worse comes to worse.

It is disappointing as this is sort of thing that a polished title should add.It ruins immersion.

What puzzles me actually as someone who was done a lot of programming in many languages is why this is so difficult to ressolve. Though I admit I make a few assumptions about how events are being handled. I assume the following;

1. Events get stored as objects.

2. When a new planet is colonised the game randomly selects an event.

So that being the case I suggest the following; 

1. add two new element types to the event xml

<onlyforraceattrib>

And

<notforraceattrib>

Now they can choose to only allow one of each of these tags which is good enough to solve the synthetics issue by including the later tag in all inappropriate events with "synnthetic" in it.

So to then make these tags work in game.

1. Load the events into objects as before , the objects need new attributes to hold the content of the new tags. Thats not complex.

2. When a planet is colonised the game randomly chooses an event as normal then it checks you race attributes against the new properties of the event and if not appropriate disgards it and rolls another event, repeat until you get one that fits.

That doesn't sound like a difficult implementation, an I making a wrong assumption about how it currently works maybe?

 This solution is also very modder friendly and will automatically work for custom synthetics and allow events only applicable for other attributes of races too giving the event system a lot more depth.

It was in fact mentioned in an answer to a question on the good friday dev stream which I watched tuesday.

Paul said it would be too difficult to fix before release, he seemed to imply it would require storing a matrix of all races against events hence my suggestion above that there could be an easier solution.

I also think that dismissing problems like this as some people will whine about it but it doesn't matter in order to defend stardock doesn't help them and encourages bad release decisions like elemental.

But I agree removing the yor isnt the best workaround. Removing events that dont work for all races until you can later patch the solution in is much better. 

First off, I must have missed that bit from last weeks stream.  But I did have some connection issues, so it might have happened then.  So thanks for the info.

As for the rest, I'm not "dissmissing" the problem.  In fact, I was one of the first, if not THE first to bring it up. And I'm certianly not defending them over this.

What I am doing is puttting this issue into perspective.  Unless we want the game released in July or August (June is out of the question since that's when the already delayed Sorcerer King is released), or later, some things aren't going to be fixed/done by late May.  This is an unfortunate side-effect of the studio system.  Even a mid-small sized one like Stardock.  Recognizing this isn't defending them, simply acknowledging the obvious: There's only so many dev hours to go around.

So the issue ultimately becomes one of priority.  And for me, there are a LOT of things I'd rather see addressed by launch than this.

Well, it won't bother me because I rarely (if ever) play as the Yor but all the references to food and disease would be distracting for those who do.

When I read the thread originally I thought the Yor problem was worse, involving reproduction (which has been fixed I assume). I can see why they would release but they will get some feed back I'll bet. 

I think the events need a pass regardless of whether they fix them for synthetic races or not.  I think the best solution is to keep synthetic races in mind with doing that pass.

To be fair its only discussed briefly in the stream so easy to miss.

I actually don't mind when they release the game since I can already play it anyway. But the release version will be the one reviewed and the one that creates an impression of the game for those who aren't already fans so it really does matter as to the quality of the experience even if you choose to play as synthetics. 

Realistically though I can see delaying release impacts stardocks bottom line as does committing resources to fixing this. But so does the release version of the game seeming obviously broken should someone play as a synthetic race.

I would have though if they seriously can't fit in a code fix for this before release fixing it by editing out the events that seem to not generalise well is a quick and dirty way to stop the game appearing broken.