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.

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

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.

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.

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.

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.

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.