[0.10.2][kovarex] "WRONG CHEST" error

[champ]

@transport belt madness level3.

One of the inserters fail to move the metal bars onto the belt, due to a "wrong chest" error (see picture below).




.


[edit]
I'm not sure if its necessary, though often requested in other posts, here is a link to the savegame:

Code: Select all

http://speedy.sh/8qZes/belt-lvl3b.zip

[Turtle]

I don't have this scenario, but it looks to me like you're getting "wrong chest" because your coal and circuit belts are mixed up.

[champ]

I don't have this scenario, but it looks to me like you're getting "wrong chest" because your coal and circuit belts are mixed up.

Not really.

[champ]

In fact, it doesn't matter how I build it, this one chests (containing the correct item however) just gives this error. The inserter is unable to move the items out of it.


On another note, another scenario pack also has bugs.
The limited-space scenario, where you need to get a certain income in a fixed amount of time, fails to sell the items you didn't use each round; therefore making it almost impossible to win the scenario.

I assume these fairly obvious and game breaking bugs are still there due to a lack of testing as few people paid extra to be able to play them. Nevertheless it seems to be easy to fix.

[kovarex]

This is really strange error.
The level is finishable without problem when played standardly, but for some reason, in the internals of the save, the reference to the iron chest is missing, so I get the same level when using your save, but when I restart the level it doesn't happen.

The wrong chest is internal error and doesn't indicate error of player, In the savegame you provided, you were using testing mod, it might have something to do with it but I'm really not sure. Were you doing something special with the testing mod, does it say the wrong chest error when you restart the level and click start?

[kovarex]

P.S. The tightspot is working correctly for us, doesn't it have something to do with the testing mod as well?

[champ]

This is odd indeed. I restarted the game, just as you described, and it seems to work with no problems at all.
Testing mode is still enabled, including 10+ other mods. The update to 0.10.3 popped up, though the changelog doesn't suggest any changes there.

Well, problem solved I suppose, though really strange error.
I appreciate the support however. Thanks.