[BUG] Alienation

[Morgan]

After getting the mutation Alienation, whenever I start a game it gives me an error saying that alientation has no color for the flask.
Hope you wonderful developers over yonder fix this soon, love this game.

[LegionDoom]

yea game is unplayable right now after you get alienation i would hate to restart my progress

[ChaosSabre]

So don't unlock alienation. Got it.

[AgentFlea]

Same problem. Game is broken for me now. Here's the error if it helps.
I don't know how active the devs are on this.

this item Alienation has no color for the flask

Called from en.deco.CellFlask.setItem (en/deco/CellFlask.hx line 107)
Called from level.BiomeDisp.initFlasks (level/BiomeDisp.hx line 250)
Called from level.BiomeDisp.initDecoEntities (level/BiomeDisp.hx line 131)
Called from level.LevelDisp.render (level/LevelDisp.hx line 274)
Called from pr.Level.initRender (pr/Level.hx line 959)
Called from pr.Level.onActivation (pr/Level.hx line 1090)
Called from pr.Level.resume (pr/Level.hx line 1062)
Called from pr.Game.activateSubLevel (pr/Game.hx line 387)
Called from pr.Game.loadMainLevel (pr/Game.hx line 321)
Called from cine.LevelTransition.loadNewLevel (cine/LevelTransition.hx line 55)
Called from cine.$LevelTransition.__constructor__ (cine/LevelTransition.hx line 46)
Called from cine.$LevelTransition.goto (cine/LevelTransition.hx line 14)
Called from pr.$Game.__constructor__ (pr/Game.hx line 76)
Called from User.newGame (User.hx line 578)
Called from Main.initGame (Main.hx line 323)
Called from Main.getGame (Main.hx line 294)
Called from local function #4550 (Main.hx line 222)
Called from local function #4613 (Main.hx line 369)
Called from mt.Delayer.update (mt/Delayer.hx line 106)
Called from mt.$Process._update (mt/Process.hx line 255)
Called from mt.$Process.updateAll (mt/Process.hx line 221)
Called from Boot.update (Boot.hx line 263)
Called from hxd.App.mainLoop (hxd/App.hx line 112)
Called from hxd.$System.mainLoop (hxd/System.hl.hx line 69)
Called from hxd.$System.runMainLoop (hxd/System.hl.hx line 123)
Called from hxd.$System.runMainLoop (hxd/System.hl.hx line 121)
Called from local function #11203 (C:\Projects\haxeTools\std/haxe/Timer.hx line 140)
Called from local function #11204 (C:\Projects\haxeTools\std/haxe/Timer.hx line 74)
Called from haxe.$MainLoop.tick (C:\Projects\haxeTools\std/haxe/MainLoop.hx line 156)
Called from haxe.$EntryPoint.processEvents (C:\Projects\haxeTools\std/haxe/EntryPoint.hx line 106)
Called from haxe.$EntryPoint.run (C:\Projects\haxeTools\std/haxe/EntryPoint.hx line 135)

[Morgan]

@ChaosSabre Yeah, just avoid it for now unless you want basically all your progress wiped. I just hope the devs fix this soon.

[AgentFlea]

Originally posted by Daddy Don:

@ChaosSabre Yeah, just avoid it for now unless you want basically all your progress wiped. I just hope the devs fix this soon.

Do they patch or update the Beta branch often? Seems like we won't be getting a fix for this until at least a few months, once this moves to the regular build of the game.

2-4 months?

[WheresWillow]

I’d imagine with a bug that literally prevents you from playing the game they would do something at least. If a ton of people can’t play the beta there’s not really a point in having it.

Originally posted by Aegis:

Originally posted by Daddy Don:

@ChaosSabre Yeah, just avoid it for now unless you want basically all your progress wiped. I just hope the devs fix this soon.

Do they patch or update the Beta branch often? Seems like we won't be getting a fix for this until at least a few months, once this moves to the regular build of the game.

2-4 months?

[Morgan]

Originally posted by Wilbur_puptato:

I’d imagine with a bug that literally prevents you from playing the game they would do something at least. If a ton of people can’t play the beta there’s not really a point in having it.

Originally posted by Aegis:

Do they patch or update the Beta branch often? Seems like we won't be getting a fix for this until at least a few months, once this moves to the regular build of the game.

2-4 months?

In the alpha they were pretty quick to fix things up, I'd imagine that they would act the same with this bug. Of course that could just be me being a tad too optimistic.

[WheresWillow]

I don’t think you’re being too optimistic, the devs are really great.

Originally posted by Daddy Don:

Originally posted by Wilbur_puptato:

I’d imagine with a bug that literally prevents you from playing the game they would do something at least. If a ton of people can’t play the beta there’s not really a point in having it.

In the alpha they were pretty quick to fix things up, I'd imagine that they would act the same with this bug. Of course that could just be me being a tad too optimistic.

[sbm311]

Originally posted by Aegis:

Do they patch or update the Beta branch often? Seems like we won't be getting a fix for this until at least a few months, once this moves to the regular build of the game.

2-4 months?

At the weekend there were no updates, since from important information it is clear that "Working Hours: 9AM - 6PM CET Mon - Fri (We're based in Bordeaux, France)".

The latest updates for this month came out: two on December 15, 14, 12, 9, 6, 5 and 1 December. So this kind of a bug fix, you can expect even today. Because many people can no longer play because of these error crashes, and they will become more and more, it can be said a critical bug requiring immediate fix.

[WheresWillow]

Originally posted by sbm311:

Originally posted by Aegis:

Do they patch or update the Beta branch often? Seems like we won't be getting a fix for this until at least a few months, once this moves to the regular build of the game.

2-4 months?

At the weekend there were no updates, since from important information it is clear that "Working Hours: 9AM - 6PM CET Mon - Fri (We're based in Bordeaux, France)".

The latest updates for this month came out: two on December 15, 14, 12, 9, 6, 5 and 1 December. So this kind of a bug fix, you can expect even today. Because many people can no longer play because of these error crashes, and they will become more and more, it can be said a critical bug requiring immediate fix.

If not sometime today, certainly by Wednesday id imagine. its just too big not to do something about.

[Morgan]

Originally posted by Wilbur_puptato:

Originally posted by sbm311:

At the weekend there were no updates, since from important information it is clear that "Working Hours: 9AM - 6PM CET Mon - Fri (We're based in Bordeaux, France)".

The latest updates for this month came out: two on December 15, 14, 12, 9, 6, 5 and 1 December. So this kind of a bug fix, you can expect even today. Because many people can no longer play because of these error crashes, and they will become more and more, it can be said a critical bug requiring immediate fix.

If not sometime today, certainly by Wednesday id imagine. its just too big not to do something about.

If not by then, surely it should be by the time the update comes out onto the main branch, which looks relatively soon-ish.

[WheresWillow]

Originally posted by Daddy Don:

Originally posted by Wilbur_puptato:

If not sometime today, certainly by Wednesday id imagine. its just too big not to do something about.

If not by then, surely it should be by the time the update comes out onto the main branch, which looks relatively soon-ish.

oh yeah for sure, if it was released into the main branch with this bug there would be riots.

[Tipyx]

Thanks for the report! It'll be fixed in the next hotfix update :)

[Morgan]

Originally posted by Tipyx:

Thanks for the report! It'll be fixed in the next hotfix update :)

Yay! Thank you guys, you all over there are the best. :D

[WheresWillow]

its been fixed