Register - Login
Views: 99395559
Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies
04-24-22 12:38:48 PM
Jul - The Cutting Room Floor - Splitting "Regional Changes" into cosmetic/gameplay changes? New poll - New thread - New reply
Next newer thread | Next older thread
Xkeeper

Level: 263


Posts: 23358/25343
EXP: 296724887
For next: 2235566

Since: 07-03-07

Pronouns: they/them/????????

Since last post: 9 days
Last activity: 3 days

Posted on 04-30-18 04:01:10 PM Link | Quote
This might need to be the case for revisions, too, but someone brought up a good point that some changes are reasonably "cosmetic only" (e.g. Kirby going from being a jolly fellow to a clearly upset pink blob), while others are more gameplay-oriented, like making enemies more difficult or changing how some level layout was.

It might be too much work for too little gain to split these up, but I'm curious what everyone thinks.

____________________
(Lv 243 with 224486943 EXP)
Ehm
Member
Level: 49


Posts: 533/533
EXP: 843385
For next: 40498

Since: 06-13-09

From: Canada

Since last post: 4.0 years
Last activity: 4.0 years

Posted on 04-30-18 04:08:13 PM Link | Quote
It might be something to add as a new category to easily locate that kind of content on the site, but if these changes still occur at the regional/revisional level then I don't see a need to remove them from those sections on a page.
RanAS
Member
Level: 55


Posts: 423/844
EXP: 1286494
For next: 27695

Since: 10-10-14

From: São Paulo, Brazil

Since last post: 1 day
Last activity: 1 day

Posted on 05-03-18 08:55:04 AM Link | Quote
The gameplay-oriented changes are certainly more interesting, but they're all still regional differences anyway. It could be good if a page has a ton of content in its regional changes section to split it into multiple categories, but overall I don't think it's necessary.

____________________

"The quieter you become, the more you are able to hear." --Ram Dass
BatElite
Member
Level: 35


Posts: 131/345
EXP: 273825
For next: 6111

Since: 04-24-17

Pronouns: they/them, preferably she/her (fluidity is heck)

Since last post: 10 days
Last activity: 1 day

Posted on 05-08-18 09:28:17 AM Link | Quote

If you're going to make that split I think you might as well count revisional differences under the same categories. That would mean it's not obvious which of those two is going on without reading the article.

I'm not sure what you'd gain from doing it, but I'm indifferent about it I guess.

____________________
"Rusted old machines should stay home and play with their toasters!"

Next newer thread | Next older thread
Jul - The Cutting Room Floor - Splitting "Regional Changes" into cosmetic/gameplay changes? New poll - New thread - New reply


Rusted Logic

Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

30 database queries.
Query execution time:  0.256815 seconds
Script execution time:  0.012203 seconds
Total render time:  0.269018 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 2 column 301 - Warning: unescaped & or unknown entity "&page"
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 241 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 91 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 177 column 102 - Warning: unescaped & or unknown entity "&postid"
line 179 column 74 - Warning: <style> isn't allowed in <td> elements
line 179 column 9 - Info: <td> previously mentioned
line 184 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 186 column 9 - Warning: missing <tr>
line 204 column 13 - Warning: missing <tr>
line 205 column 102 - Warning: unescaped & or unknown entity "&postid"
line 210 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 212 column 9 - Warning: missing <tr>
line 230 column 13 - Warning: missing <tr>
line 231 column 102 - Warning: unescaped & or unknown entity "&postid"
line 233 column 74 - Warning: <style> isn't allowed in <td> elements
line 233 column 9 - Info: <td> previously mentioned
line 236 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 238 column 9 - Warning: missing <tr>
line 256 column 13 - Warning: missing <tr>
line 257 column 102 - Warning: unescaped & or unknown entity "&postid"
line 267 column 17 - Warning: missing <tr>
line 267 column 17 - Warning: discarding unexpected <table>
line 270 column 35 - Warning: missing <tr>
line 270 column 50 - Warning: missing </font> before </td>
line 270 column 91 - Warning: missing </font> before </table>
line 272 column 35 - Warning: missing <tr>
line 272 column 50 - Warning: missing </font> before </td>
line 273 column 37 - Warning: unescaped & or unknown entity "&id"
line 272 column 241 - Warning: missing </font> before </table>
line 274 column 17 - Warning: discarding unexpected </textarea>
line 274 column 28 - Warning: discarding unexpected </form>
line 274 column 35 - Warning: discarding unexpected </embed>
line 274 column 43 - Warning: discarding unexpected </noembed>
line 274 column 53 - Warning: discarding unexpected </noscript>
line 274 column 64 - Warning: discarding unexpected </noembed>
line 274 column 74 - Warning: discarding unexpected </embed>
line 274 column 82 - Warning: discarding unexpected </table>
line 274 column 90 - Warning: discarding unexpected </table>
line 276 column 9 - Warning: missing </font> before <table>
line 288 column 25 - Warning: discarding unexpected </font>
line 297 column 37 - Warning: discarding unexpected </font>
line 275 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 161 column 23 - Warning: <img> lacks "alt" attribute
line 161 column 64 - Warning: <img> lacks "alt" attribute
line 161 column 113 - Warning: <img> lacks "alt" attribute
line 161 column 163 - Warning: <img> lacks "alt" attribute
line 162 column 11 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 189 column 22 - Warning: <img> lacks "alt" attribute
line 189 column 63 - Warning: <img> lacks "alt" attribute
line 189 column 112 - Warning: <img> lacks "alt" attribute
line 189 column 162 - Warning: <img> lacks "alt" attribute
line 190 column 11 - Warning: <img> lacks "alt" attribute
line 200 column 15 - Warning: <img> lacks "alt" attribute
line 215 column 22 - Warning: <img> lacks "alt" attribute
line 215 column 63 - Warning: <img> lacks "alt" attribute
line 215 column 112 - Warning: <img> lacks "alt" attribute
line 215 column 162 - Warning: <img> lacks "alt" attribute
line 216 column 11 - Warning: <img> lacks "alt" attribute
line 226 column 15 - Warning: <img> lacks "alt" attribute
line 233 column 1563 - Warning: <img> lacks "alt" attribute
line 241 column 22 - Warning: <img> lacks "alt" attribute
line 241 column 63 - Warning: <img> lacks "alt" attribute
line 241 column 112 - Warning: <img> lacks "alt" attribute
line 241 column 162 - Warning: <img> lacks "alt" attribute
line 242 column 11 - Warning: <img> lacks "alt" attribute
line 252 column 15 - Warning: <img> lacks "alt" attribute
line 273 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 273 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 273 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 282 column 25 - Warning: <img> lacks "alt" attribute
line 287 column 267 - Warning: <img> lacks "alt" attribute
line 149 column 50 - Warning: trimming empty <font>
line 267 column 17 - Warning: trimming empty <tr>
line 270 column 50 - Warning: trimming empty <font>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
line 205 column 27 - Warning: <nobr> is not approved by W3C
line 231 column 27 - Warning: <nobr> is not approved by W3C
line 257 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 102 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md