Talk:The Sealed Cavern
From Guild Wars 2 Wiki
Jump to navigationJump to search
Method 3 has been removed. Anet has blocked landing on the roof of the Vinewrath Tangle, as such this method of unlocking Sealed Cavern no longer works. 86.25.107.236 10:33, 14 September 2017 (UTC)
- Confirmed, couldn't throw my mesmer greatsword 2 projectile through it either. -Chieftain Alex
17:41, 14 September 2017 (UTC)
- While it's certainly helpful in some situations to include map breaks like that, I wonder if the wiki should document them? Some people see map breaking as exploiting, and it certainly can be used to exploit environments. Also, listing a map break in a widely used public forum like this just means that it will be closed much sooner, meaning that the information on the page is temporary, and will need to be double checked frequently. I guess what I'm saying is that I don't think we should include map breaks in "how to get there" or w/e sections. Using a map break to get cool pictures is one thing, using a map break to get around a "play the content" wall is abuse.-Rain Spell (talk) 18:07, 14 September 2017 (UTC)
- Documenting a map break for the sake of a map break seems arbitrary at best; however, past and (current?) articles documented bugs as a whole. Were we to document breaks as general bugs, akin to script-breaks/bad enemy placement/etc, I could see that being a viable course of action. --
Traveler (talk) 18:24, 14 September 2017 (UTC)
- I view map breaking as an exploit more than a bug since that's is performed by the players looking for a weak point more than something being broken. I will say though, I do know sometimes bugs can occur that force players out of the map similar to map breaking such as being under a chest when it spawns and such(happened to me twice), and that I would document as a bug. - Doodleplex 18:37, 14 September 2017 (UTC):
- True. The reason I opted for bug instead of exploit was to tag off of Rain's comment: "I don't think we should include map breaks in "how to get there" or w/e sections." Documenting exploitable content for unintended gain should not be our main goal; that does bring up the question, however, of how to document it at all without piquing someone's interest to go exploit it. -- Traveler (talk) 18:58, 14 September 2017 (UTC)
- I believe the majority of our bug sections either just mention the bug exists, mention how the bug occurs/how to avoid it occuring, or how to un-bug something that's bugged. I think that's a valuable service. I'm someone who map breaks. I do it for fun, for the cool screenshots, the weird environments, and for the odd objects devs leave behind when they ship a map. Anet has said that they don't care about map breaking, as long as it isn't used to "gain an advantage" or to complete content. (I.E. no underground mining, no untargettable fighting, no jumping into WvW keeps, etc.) I can't find the post now that the forums have been updated, but it's there. I really enjoy map breaking, but I don't think it should feature a place on the wiki as a way around content, or as a "bug fix".--Rain Spell (talk)
- I think the enticing players to use things to map break can be avoided if the bug comment is worded in way that makes it seem more like a negative than a positive. For example, instead of "X will cause you to map break" it'd be "X will force a player out of the map boundaries which can only be fixed by using a waypoint or changing maps". (Also I will say though I have no idea how to do it because somebody was porting to it, being in the aquarium in DR is totally fun. XD) - Doodleplex 19:23, 14 September 2017 (UTC)
- (Message me in game sometime and I could show you how to get there. I love that one and getting on top of the archways best. Sadly, the dome doesn't "exist".)>.> --Rain Spell (talk)
- https://imgur.com/a/VcT93 Yeah Divinity's Reach is cool too. Iirc the Silverwastes gliding one only allowed you to unfog the area and look down on top, you couldn't get into the cave. -Chieftain Alex 20:36, 14 September 2017 (UTC)
- https://imgur.com/a/VcT93 Yeah Divinity's Reach is cool too. Iirc the Silverwastes gliding one only allowed you to unfog the area and look down on top, you couldn't get into the cave. -Chieftain Alex
- (Message me in game sometime and I could show you how to get there. I love that one and getting on top of the archways best. Sadly, the dome doesn't "exist".)>.> --Rain Spell (talk)
- I think the enticing players to use things to map break can be avoided if the bug comment is worded in way that makes it seem more like a negative than a positive. For example, instead of "X will cause you to map break" it'd be "X will force a player out of the map boundaries which can only be fixed by using a waypoint or changing maps". (Also I will say though I have no idea how to do it because somebody was porting to it, being in the aquarium in DR is totally fun. XD) - Doodleplex 19:23, 14 September 2017 (UTC)
- I believe the majority of our bug sections either just mention the bug exists, mention how the bug occurs/how to avoid it occuring, or how to un-bug something that's bugged. I think that's a valuable service. I'm someone who map breaks. I do it for fun, for the cool screenshots, the weird environments, and for the odd objects devs leave behind when they ship a map. Anet has said that they don't care about map breaking, as long as it isn't used to "gain an advantage" or to complete content. (I.E. no underground mining, no untargettable fighting, no jumping into WvW keeps, etc.) I can't find the post now that the forums have been updated, but it's there. I really enjoy map breaking, but I don't think it should feature a place on the wiki as a way around content, or as a "bug fix".--Rain Spell (talk)
- True. The reason I opted for bug instead of exploit was to tag off of Rain's comment: "I don't think we should include map breaks in "how to get there" or w/e sections." Documenting exploitable content for unintended gain should not be our main goal; that does bring up the question, however, of how to document it at all without piquing someone's interest to go exploit it. --
- I view map breaking as an exploit more than a bug since that's is performed by the players looking for a weak point more than something being broken. I will say though, I do know sometimes bugs can occur that force players out of the map similar to map breaking such as being under a chest when it spawns and such(happened to me twice), and that I would document as a bug. - Doodleplex 18:37, 14 September 2017 (UTC):
- Documenting a map break for the sake of a map break seems arbitrary at best; however, past and (current?) articles documented bugs as a whole. Were we to document breaks as general bugs, akin to script-breaks/bad enemy placement/etc, I could see that being a viable course of action. --
- While it's certainly helpful in some situations to include map breaks like that, I wonder if the wiki should document them? Some people see map breaking as exploiting, and it certainly can be used to exploit environments. Also, listing a map break in a widely used public forum like this just means that it will be closed much sooner, meaning that the information on the page is temporary, and will need to be double checked frequently. I guess what I'm saying is that I don't think we should include map breaks in "how to get there" or w/e sections. Using a map break to get cool pictures is one thing, using a map break to get around a "play the content" wall is abuse.-Rain Spell (talk) 18:07, 14 September 2017 (UTC)
Feedback 2017/10/28[edit]
Replace with feedback text. --61.228.209.91 15:12, 28 October 2017 (UTC)
You can reveal the area easily with a level 3 springer now. Just jump up the cliffs (north east of Desperate Passage).
