Description
Simple voting system has been added to http://gw2dungeons.net/Voting. Each week I will create a discussion topic on forums and add relevant polls there, if needed. Guild leaders are given an account which can be used to vote. Polls stay up for one week.
Guild leaders can apply for a vote by sending me your preferred login name and reason why you should have a vote (was in previous rule meetings, have records, etc.) via in-game, forums or email. Optionally you can also give me your email so I can send a reminder about new polls if there hasn’t been any for a while.
Current vote holders:
- Daemoniic [HeX]
- Enko [LOD]
- Deathly [qT]
- Skywalker [TDN]
- Der/p/y Moa [vC]
- Ashlee [geek]
- Jerem [SC]
- Nikephoros [DnT]
- Sanderinoa [rT]
- Veckna [QQ]
- Senior Magic [iG]
Keep in mind that anyone is free to give their opinion and ideas on this topic!
Results of week 24 voting
Since any exceptions were voted against (and because of last week’s discussion) I checked current exception list. I reverted two path specific bans because they aren’t based on rules. This will probably be changed next week so I wouldn’t base your runs on this.
So now:
- CMP3: Using the air guns against bosses is allowed.
- Arah: Using reflects on Lupicus’ wall in phase 2 is allowed.
90% agreed to allow abuse of path selection so ArahP3 door trick (and AC exp burrow) remain allowed. A rule has been added to allow this.
67% agreed to allow being past blockades if you get there before they close and 70% agreed that blockades don’t have to be opened. These slightly contradict each other but as mentioned last week, the former will overrule the latter. Rules have been modified to clarify this.
Definition: A pathway is open if it can be passed without jumping or using skills. A pathway is blocked if it’s not open but can be opened.
Technically this means that jumping on the CoE gate is allowed but you can’t jump down before the gate opens. If this feels problematic please let me know.
100% agreed to require path completion on unrestricted ruleset. This requirement has been added to all rulesets for symmetry.
I was also requested to give a broad statement about the restricted rule set to make sure every voter is on the same page. I have chosen “Restricted ruleset is what you want it to be.” because that’s the only one I can realistically enforce. If anyone is found voting “not how he wants”, his/her voting rights will be revoked. You have been warned.
Issue1: NPC manipulation
People have figured out that they can manipulate NPC behavior by waypointing or by killing the NPC. In some cases this can be used to skip NPC dialogue to speed up the run. Currently abusing of event scripting is banned which can be understood both ways.
A) Allow NPC manipulation to break/skip dialogue
- Also makes triggering dialogue not mandatory
- Less restrictive
B) Don’t allow
- Also makes triggering dialogue mandatory (this can be refined later if needed)
- More restrictive
I’m not aware that NPC manipulation would have been used to break cutscenes, yet. So a similar question about cutscenes. Currently rules state that “All cutscenes within a dungeon that are relevant to the path must be triggered.”
A) Allow NPC manipulation to break/skip cutscenes
- Also makes triggering cutscenes not mandatory
- Less restrictive
B) Don’t allow.
- Keeps triggering cutscenes mandatory (this can be refined later if needed)
- More restrictive (keeps the current rule)
Issue2: Banning behavior
Currently there are two kind of bans. Either a specific player action or a specific result is banned. For example entering inside a geometry is banned even if you didn’t gain any advantage. Similarly bugging bosses is banned regardless the way you do it.
But there is one more kind. Banning a specific action with a specific result. For example abuse of path selection. Currently it affects both ArahP3 gate and Arah exp burrow. But if it only affected “mandatory events” it could be made only affect ArahP3 gate.
A) Allow banning a specific action with a specific result
- Allows fine tuning the rules (which may slow down the process)
- Complicates rules
B) Keep actions and results separated on the rules
- Keeps rules simple
Issue3: Exceptions
Reopened from week 22 with a good reason (see replies below). So what to do with encounter specific rules (exceptions)?
A) Decide case by case with voting. Allows exceptions.
- Exceptions may override main rules
B) Wethospu decides based on rules.
- No exceptions. Encounter rules are just for clarifications.
- Allows “wall on wall” on Lupicus
- Allows using air guns against bosses in CMP3
C) Same as A) but exceptions can’t override general rules
- Exceptions may only take care of special cases.
- Rule changes may lead to conflicts with exceptions which have to be resolved
(edited by Wethospu.6437)