Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

raidboss: ASS/S simplify Rush of Might 1 #5167

Merged
merged 3 commits into from
Jan 2, 2023
Merged

Conversation

quisquous
Copy link
Owner

This is subjective, but I find this style of instructions much easier to read and understand.

I asked a few people about this, and nobody is thinking about absolute north during this mechanic, and so "go east" when everybody is looking at the gladiators requires a lot more thinking.

I also understand that there is some ambiguity in "go left 1, right 2" (is it saying you need to go 2 the left or is the left one blinking 2 so you go 2 to the right, but hopefully the word "go" there makes it more obvious?)

This is subjective, but I find this style of instructions much
easier to read and understand.

I asked a few people about this, and nobody is thinking about
absolute north during this mechanic, and so "go east" when
everybody is looking at the gladiators requires a lot more thinking.
@quisquous
Copy link
Owner Author

cc @Legends0 for wording opinions here; if other folks like the original better, I'm happy to just leave it as-is. This worked for my brain a lot better.

@Legends0
Copy link
Contributor

I don't quite understand how the text output covers all the cases because It's always saying go left, which means either west for the first rush set or east for the second. I thought this mechanic can force the safe spot to be on the right instead of left.

The only other concern I have is that the 2/3 or 3/2 case here where the place to stand is not different enough in phrasing to differentiate it from the other cases. Perhaps the original phrasing had this problem of where to stand as well.

@quisquous
Copy link
Owner Author

quisquous commented Dec 29, 2022

Yeah, the thought here is instead of trying to say precisely where to stand, it's to say how many notches to go down each line. So "go 1 left 3 right" would mean on the line going front left to back right on the 3rd notch of that line. In that case you'd be "on the right". You have to be able to form the intersection in your mind and go to the intersection from that.

@quisquous
Copy link
Owner Author

And, given your own confusion with what this is saying, it's possible there's just not a great answer here.

@xiashtra
Copy link
Contributor

xiashtra commented Dec 29, 2022

I think these are over-specific to the point of information overload. I maintain my thoughts from the previous discussion on this mechanic: #5005 (comment)

The only information needed is which side is dashing farther and how far. Instead of "left [x] right [y]" it could be "left [x]" or "right [y]". The only pattern that might need a more unique call would be the 2/3 combinations, but again all you really need to know is which side is dashing farther and that it's a 2/3 combo.

@quisquous
Copy link
Owner Author

I think I disagree with "you only need to know which side is dashing further". As you say, you have to know if it's a 2/3 or a 1/3. And if you know that, then you know how far both sides are dashing, and not just the further one. Just one side is not sufficient here.

Do you feel like "go right 1 left 3" is information overload as well?

@xiashtra
Copy link
Contributor

I think I disagree with "you only need to know which side is dashing further". As you say, you have to know if it's a 2/3 or a 1/3. And if you know that, then you know how far both sides are dashing, and not just the further one. Just one side is not sufficient here.

Do you feel like "go right 1 left 3" is information overload as well?

I think a call that includes both the words "left" and "right" simultaneously opens up the possibility of confusion in which side a player should move towards, when it could give you the same info with "right behind third line", "left behind second line" etc.

At the very least the call should order the side you need to move towards immediately after the word "go". As it is currently, it can call "go right 3 left 1" when you should be moving towards the left.

@quisquous
Copy link
Owner Author

At the very least the call should order the side you need to move towards immediately after the word "go". As it is currently, it can call "go right 3 left 1" when you should be moving towards the left.

Good idea. This should be an easy fix to do.

@quisquous
Copy link
Owner Author

@xiashtra does this look like what you're asking for?

@quisquous
Copy link
Owner Author

Another option is that I could add all 6 possibilities and people could word them however they want.

@quisquous
Copy link
Owner Author

Ok, there's all options, and better wording for on the line.

@xiashtra
Copy link
Contributor

xiashtra commented Jan 2, 2023

Another option is that I could add all 6 possibilities and people could word them however they want.

I think either of these works fine. Having all 6 options allows for maximum user customization for those that want it.

@quisquous quisquous merged commit 4fdcd13 into main Jan 2, 2023
@quisquous quisquous deleted the criterion_rush_of_might branch January 2, 2023 05:30
github-actions bot pushed a commit that referenced this pull request Jan 2, 2023
This is subjective, but I find this style of instructions much easier to
read and understand.

I asked a few people about this, and nobody is thinking about absolute
north during this mechanic, and so "go east" when everybody is looking
at the gladiators requires a lot more thinking.

I also understand that there is some ambiguity in "go left 1, right 2"
(is it saying you need to go 2 the left or is the left one blinking 2 so
you go 2 to the right, but hopefully the word "go" there makes it more
obvious?) 4fdcd13
github-actions bot pushed a commit that referenced this pull request Jan 2, 2023
This is subjective, but I find this style of instructions much easier to
read and understand.

I asked a few people about this, and nobody is thinking about absolute
north during this mechanic, and so "go east" when everybody is looking
at the gladiators requires a lot more thinking.

I also understand that there is some ambiguity in "go left 1, right 2"
(is it saying you need to go 2 the left or is the left one blinking 2 so
you go 2 to the right, but hopefully the word "go" there makes it more
obvious?) 4fdcd13
@ssilve1989
Copy link

Just throwing my thoughts in here that what was there previously was perfectly fine. I find the new defaults confusing to know if its inside/outside. However looks like I'll just have to customize out of the defaults.

In general, I find cardinal directions better to use over relative directions because it doesn't assume the direction anyone is facing. Sure, most parties will be looking south for the second rush, but you by no means have to, especially with Legacy movement.

@ibenny1011
Copy link

how do you customize back to the old one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants