Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This is currently being discussed by our development team.
We should have a fix very soon!
Apologies for the inconvenience caused.
First time actually trying this, sad it's a bug that is still going on. Thank you, Frontier for responding though. I guess I'll turn that section into my amphibian house instead.
Here is a screen shot I just did in sandbox to explain. The vendor in in the background can be fired, leave shop, rehired and has no problem entering the shop. The vendor in the foreground can be fired, leave shop, and then when rehired can not enter shop. Same if leave for break and try to come back.
https://steamcommunity.com/sharedfiles/filedetails/?id=3238562651
What I have found is I have to let the shop's auto path connect to the main path and not place a path from the main path to the shop. Even though the main path to shop connects it messes up the vendors navigation for some reason.
Having said all this and you did let the shop's auto path connect to the main path, I might have been just lucky.
It's often better to assign a group of vendors to multiple shops within a single work zone. This strategy normally keeps fresh staff at shops with the need for fewer staff. Generally four vendors for every three shops is a good starting point.
Is there a solution to this? I still have this bug today
In general the issue has been fixed. There are still random events like this but rare. Older builds created before the 1.7 updates that had the issue sometimes retain the issue.