0009297: Visitors refuse to leave fort when location forbidden or retired

Notes
(0033724) Talvieno (reporter) 2015-12-10 09:18	Can confirm. I'd hoped to have an easy way of saying, "We're closed, kthxbai"

(0033909) Zarathustra30 (reporter) 2015-12-14 23:40	There is always a way to say "kthxbai" in Dwarf Fortress. It generally involves magma. Anyway, visitors also stick around if you retire the location they want to visit. It is a bit annoying, because I can't bring them back.

(0033913) Detros (manager) 2015-12-15 00:51 edited on: 2015-12-16 02:48	If it works that way, Zarathustra30, it works similarly to trade caravan. And those generally come less often, so no usable Trade Depot is worse. EDIT: Sorry, Zarathustra30, I somehow read your note as "I don't like visitors will turn and go away when I retire location they are going to". I reread it now and it is in fact the opposite thing, "I don't like visitors won't go away even when I retire location they are in".

(0033954) martinuzz (reporter) 2015-12-16 02:12 edited on: 2015-12-16 02:12	There's about 60 visitors in my tavern that have been there for the past 4 dwarf years. They're not leaving. They kill my FPS. Please fix, so that they leave normally.

(0034209) Ogg the Blinky Sock (reporter) 2015-12-26 21:03	This issue is still present in 0.42.04. Is this ticket a duplicate item? It's not marked as acknowledged, so the status is unclear, and maybe not everyone is experiencing this. Experience with my current fort is that there are 80+ guests and no clear way to reduce or moderate that number in a non-homicidal fashion.

(0034214) lethosor (manager) 2015-12-27 08:44 edited on: 2015-12-27 08:45	I didn't notice any duplicates in a search, but not all non-duplicate issues are marked as acknowledged/confirmed automatically. It sounds like visitors gravitate to a meeting area once all locations are retired or set to forbid visitors. What happens if you remove that meeting area (or all meeting areas)? What's displayed when selecting these visitors with [v]-[g]? A save would also be helpful - without saves, it's difficult to confirm or fix bugs that have 4-year reproduction processes.

(0034217) lethosor (manager) 2015-12-27 08:59	There is also a VISITOR_CAP setting in data/init/d_init.txt (explained further there), which helps address performance issues resulting from lots of visitors.

(0035005) Toothspit (reporter) 2016-04-13 00:31	Here you go, lethosor: http://dffd.bay12games.com/file.php?id=11947 [^]

(0035006) PatrikLundell (reporter) 2016-04-13 01:25	It seems visitors know what location they wanted to visit (displayed on their general info screen) and if that location is destroyed (The Breakfast of Lunch tavern, for instance) they get confused. Recreating such a location and then changing the name to exactly match the one the visitors came to visit worked in at least one case to get visitors to behave normally again (the original location had a zone problem, which was the original reason the location was deleted, so after renaming the tavern its zone had to be removed and recreated for things to recover completely).

(0036242) FantasticDorf (reporter) 2017-01-30 06:10	I have a possibly related report over at 0010129 (Buggy meeting sites behaviour breaking locations (and meeting sites function)) with a supplied save that might help explain the relation between them moving meeting sites after the tavern is decommissioned. The site needs to be 'removed' with (i) then (x) to clear the area properly. Location/meeting sites remain active while turned off if the zone (can be seen on locations dance floor & (R)) still exists. If they are already in a meeting area, unless they have the need to socialise desperately they will not return to the tavern if it is disabled (no 'active' meeting zone or 'meeting zone' enabled) to over-indulge in merryment only going when their needs are slightly distracted or worse, else idling in blank meeting zone/fulfilling other needs. This would be a instance it seems where visitors are dissatisfied, and aren't ready to leave because the tavern location site has been removed/otherwise inaccessible, and without the meeting site active to hold them there don't overfill their needs to a good level = No departure. Information about whether they are 'curious' or came for a 'good-time' would be helpful please to see if there is a correlation between visitor departure & relevant need fufillment for taverns.

Issue History
Date Modified	Username	Field	Change
2015-12-10 04:10	skaltum	New Issue
2015-12-10 09:10	Hedede	Issue Monitored: Hedede
2015-12-10 09:18	Talvieno	Note Added: 0033724
2015-12-10 09:18	Talvieno	Issue Monitored: Talvieno
2015-12-14 23:40	Zarathustra30	Note Added: 0033909
2015-12-15 00:51	Detros	Note Added: 0033913
2015-12-16 02:12	martinuzz	Note Added: 0033954
2015-12-16 02:12	martinuzz	Note Edited: 0033954	View Revisions
2015-12-16 02:48	Detros	Note Edited: 0033913	View Revisions
2015-12-26 21:03	Ogg the Blinky Sock	Note Added: 0034209
2015-12-26 21:03	Ogg the Blinky Sock	Tag Attached: 0.42.03
2015-12-26 21:03	Ogg the Blinky Sock	Tag Attached: 0.42.04
2015-12-27 08:44	lethosor	Note Added: 0034214
2015-12-27 08:44	lethosor	Assigned To	=> lethosor
2015-12-27 08:44	lethosor	Status	new => needs feedback
2015-12-27 08:45	lethosor	Note Edited: 0034214	View Revisions
2015-12-27 08:59	lethosor	Note Added: 0034217
2015-12-27 09:17	Huntthetroll	Issue Monitored: Huntthetroll
2016-01-10 21:25	Zarathustra30	Issue Monitored: Zarathustra30
2016-02-14 11:08	Lidi	Tag Attached: 0.42.06
2016-04-13 00:31	Toothspit	Note Added: 0035005
2016-04-13 01:25	PatrikLundell	Note Added: 0035006
2016-04-13 03:45	Toothspit	Issue Monitored: Toothspit
2017-01-15 10:53	Loci	Status	needs feedback => acknowledged
2017-01-15 10:54	Loci	Summary	Visitors refuse to leave fort => Visitors refuse to leave fort when location forbidden or retired
2017-01-30 06:10	FantasticDorf	Note Added: 0036242

Relationships