#Tax collectors can't collect taxes in mines
19 messages Β· Page 1 of 1 (latest)
This has completely broken my save. I hope this gets prioritized. Nothing I can do fixes it and eventually all my tax collectors get stuck trying to collect from a mine. At this point 0 taxes are collected. The only solution I can think of is to have more tax collectors than you have mines so that each mine has a stuck collector and no other collecters try, lol. So... ya I didn't do that and just started a new save, and I won't unlock that upgrade.
I think the current solution is: disable taxes for mines -> remove said mines -> rebuild said mines
100% not ideal of course
Also donβt reenable taxes for them
I'll give that a try, thanks!
I have the same problem. There are earlier bug reports regarding this issue. I had to reload an autosave to before I enabled mining taxes. Upped the post.
We are actively working on fixing this issue.
Same problem with some mines - but others also work
It seems not to matter where setting the parts of the mine - some don't work, and some work - this doesn't change
Same issue, but now it broke my whole game. No taxes are collected at all, the tax collector is stuck at his workplace.
Tried to disable the mine collection, but it did not help.
same here
A workaround that imho works is to not move the stairs after the placement
never moved a single one, this started to happen immeditely after mines tax was enacted. initially I thought that some house spawn blocked the way, so I cleared a bit - but w/o luck
I just noticed in my current run the Stone Mines are collected the iron mines arent
Funny story. I was encountering the same "tax collector can't collect tax from a mine" problem with a stuck tax collector. I built a door directly on the Tax Office and the collector went out of it, picked up taxes from the mine, then went back into the Tax Office and remained stuck again. π
can confirm, neither are marble or gold mines, only stone works
For anyone who hasn't seen the announcement yet: #announcements message
This issue seems to be resolved with the today bugfix version π
--> Patch #announcements message
Should be fixed indeed π