|
Post by wanderer on Feb 6, 2018 1:12:07 GMT -5
|
|
|
Post by Cory Trese on Feb 6, 2018 15:06:17 GMT -5
We'll have to trim that down or try to re-write it. We can't expand that list, it just doesn't fit.
|
|
|
Post by fallen on Feb 6, 2018 20:52:29 GMT -5
Thanks, trimmed down!
|
|
|
Post by wanderer on Feb 9, 2018 1:03:16 GMT -5
|
|
|
Post by fallen on Feb 9, 2018 11:26:33 GMT -5
Sorry, we can't fix bugs without updates. We did not publish this update yet.
|
|
|
Post by wanderer on Feb 9, 2018 22:15:49 GMT -5
I see. Would something like this be mentioned in the Update notes, so we know not to post the same bug again?
|
|
|
Post by MintDragon on Feb 9, 2018 22:20:27 GMT -5
I see. Would something like this be mentioned in the Update notes, so we know not to post the same bug again? Normally the devs will use the term FFN (fixed for next), meaning it will be in the next update. If it's something major, it will probably be in the notes, but a spelling error/truncation/etc... probably won't be mentioned. If you see it re-occur after, nothing wrong with coming back to this post and adding to it. :-) (btw, the next update just got released on Steam)
|
|
|
Post by fallen on Feb 9, 2018 22:52:48 GMT -5
We try to include everything that we can in the updates. However, I'd classify this as a typo, so it wasn't mentioned. It was included in v2.1.7.
If you see issues like this again, please feel free to post!
|
|