-
Notifications
You must be signed in to change notification settings - Fork 46
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: rename M[1-4] #272
base: main
Are you sure you want to change the base?
Conversation
Follow community naming conventions for clarity.
Well, just saw this post on reddit, and it is also more likely called |
The NA pug raid discords community voted for M to be the naming convention some time ago, and that has been the more common nomenclature here. It also matches the in-game naming more closely (AAC Light-heavyweight M1, etc). |
I also note that that reddit post has no upvotes, and almost everyone in the comments is disagreeing with them. |
I look forward to next tier having |
Yeah, that's sad. 😞 |
I've continued to see r1n-r4n nomenclature used predominantly elsewhere. The rationale seems to be that 'r' refers to ARcadion, whereas 'M' in the name refers to 'match', which makes it very likely that next tier (Cruiserweight) will reuse M1-M4, making the use of 'M' as a designator confusing. This seems to be supported by the localization strings for the zone names themselves: (Note that the german name actually uses 'R1', not 'M1', so another reason not to try to rely on 'match' as being unique across tiers):
|
I see why people using M rather than R, so it turns out that there are no "R"-s in the English names. While German and Japanese do have the word Arcadion in their names. |
Resource file updates and content skeletons for Patch 7.05. This maintains parity with the current naming convention, but can be updated later if #272 is merged (sidenote: if so, the oopsy trigger files should also be renamed for both normal and savage.) This also updates the current `effect_id.ts` file notwithstanding the changes proposed in #286.
Resource file updates and content skeletons for Patch 7.05. This maintains parity with the current naming convention, but can be updated later if #272 is merged (sidenote: if so, the oopsy trigger files should also be renamed for both normal and savage.) This also updates the current `effect_id.ts` file notwithstanding the changes proposed in #286. 1be5017
Resource file updates and content skeletons for Patch 7.05. This maintains parity with the current naming convention, but can be updated later if #272 is merged (sidenote: if so, the oopsy trigger files should also be renamed for both normal and savage.) This also updates the current `effect_id.ts` file notwithstanding the changes proposed in #286. 1be5017
Resource file updates and content skeletons for Patch 7.05. This maintains parity with the current naming convention, but can be updated later if OverlayPlugin#272 is merged (sidenote: if so, the oopsy trigger files should also be renamed for both normal and savage.) This also updates the current `effect_id.ts` file notwithstanding the changes proposed in OverlayPlugin#286. 1be5017
Resource file updates and content skeletons for Patch 7.05. This maintains parity with the current naming convention, but can be updated later if OverlayPlugin#272 is merged (sidenote: if so, the oopsy trigger files should also be renamed for both normal and savage.) This also updates the current `effect_id.ts` file notwithstanding the changes proposed in OverlayPlugin#286. 1be5017
There's already precedent for this type of naming convention all the way back in ARR. T1-13 even though each tier restarts as Turn 1-4(5) so it doesn't matter that next tier would be match 1-4 again. In traditional FF fashion, follow the first occurrence of something and stick with that pattern forever. |
That only happened for ARR raids though, and we all know ARR raids don't count =P |
Seeing more 'M' than 'R' these days. I still think 'r' is better internally for differentiation, but I'm retracting my earlier preference - I don't care either way. |
I don't think it bothers users many because most of them are just internal use, in most pages we are showing the full name of the raid to the user so they English players can always see the M-what at the end. :P |
I mostly see 'M', but I frequent mainly US/english places where that stuck pretty quick. My friends were confused by the 'R' and didn't seem to like it. I still think that 'M' may get confusing later on with new tiers.. I also don't think it makes a lot of difference what the internal names are. |
The internal naming affects the configuration UI naming, which would be the main motivation for changing the naming scheme. An alternative may be to use the |
Follow community naming conventions for clarity.