| ||||||
Incorrect name?[]
The full correct name for this quest is "Treasure Hunt: Treasures of Jamaica Plain" according to the game files. Should we rename the article? -- DeJuanNOnley (talk) 13:45, December 30, 2015 (UTC)
- "Find the Treasures of Jamaica Plain" is the in game name of this quest, so I don't see why any other name should title this article as that's what people would be searching for if interested in it. Having this one as a redirect or note might be good, though. —Preceding unsigned comment added by DWEco (talk • contribs). Please sign your posts with ~~~~!
- The internal name for the quest is "[DN070 - Jamaica Plain]"; quest DN070 (000e9914) - this contains the quest objective "Find the Treasures of Jamaica Plain" that is shown in the pip-boy. There is the related quest RETreasureHuntSC06_DN070 (0011132d) "Treasure Hunt: Treasures of Jamaica Plain", but it is not the main driving quest. --Alfwyn (talk) 14:00, December 30, 2015 (UTC)
- Thanks for the clarification. The missing quest IDs are leading to some confusion. I will update this article and the quests page appropriately. -- DeJuanNOnley (talk) 12:20, January 1, 2016 (UTC)
Can we now consider this verified, considering someone else has added PS4 to the list of systems affected by this bug? —Preceding unsigned comment added by WardenWolf (talk • contribs) 8 February, 2016. Please sign your posts with ~~~~!
Different quest trigger.[]
Something I found odd about this was that the way I discovered this quest was different than any stated. The way I found it was I heard two people talking about it while traversing Diamond City Market, and was then given the quest. I know this because I never saw a flyer for it, and I've checked everywhere and still haven't found a holotape I might have forgotten about from Hadrian. —Preceding unsigned comment added by 114.142.219.156 (talk • contribs) 7 May, 2017. Please sign your posts with ~~~~!
Bugged tripwire.[]
I never contributed to a wiki so I don't quite know how it works. The supposedly bugged tripwire doesn't seem to be bugged, the turret activates if the player interacts with it, being so close to the tripwire makes it easy to press the interact button on the turret instead of the tripwire. —Preceding unsigned comment added by 177.134.39.57 (talk • contribs) 19:31, November 28, 2017 (UTC). Please sign your posts with ~~~~!
- Thee thing with bugs is, they don't always trigger. This one has been tested and confirmed to work. It may have been fixed though. Sakaratte - Talk to the catmin 19:32, November 28, 2017 (UTC)
- Played through just now on PC/Steam. It still sets things off. Are we sure this is a bug and not a scripted event? Kind of a "Oh ho, you thought you were just going to clip every single tripwire, did you? Well get ready to run!". I mean the tripwire in question is almost exactly at the halfway mark, and there's an unusually dramatic delay between the detection alarm sounding and when the turrets actually start firing, long enough to get back out. All that's missing is a giant rolling boulder. predcon 16:35, June 5, 2019 (UTC)