Seconding the category name change, maybe to something like No Major Bugs, No Gamebreakers, or something like that. To get (needlessly) technical, a glitch is sort of a one-off event; sometimes, a series of variables lines up to produce a fault that is often a one-of-a-kind and difficult, if not impossible, to troubleshoot because of its ephemeral nature. Bugs, on the other hand, arise from errors in the code that are ever-present, and thus are subject to troubleshooting (or in our case, exploitation, lol)

This seems, by and large, to be a category based on avoiding the use of huge game-breaking bugs (namely SDG and Swaphopping), and the optimization of movement and use of the mechanics you have available in a regular playthrough. I'm ok with an arena skip, as it uses these mechanics and knowledge of the game's systems to circumvent something without requiring the use of a swaphop or an SDG, but also without essentially bending the game over your knee and spanking it with a chancla. Personally, I'd hate to see the run thrown out because of something relatively minor.

That being said, I'd also like to see more input on this prior to moving forward with any changes.

Done. Had no idea this was on Wii U!

This is a mere difference of opinion, nothing against you. Some communities decide to leave loading times out during timing, others roll with them. We, as a community, decided on the latter; I personally didn't want to fiddle with setting up an autosplitter, and apparently, neither did anyone else. RTA isn't "wrong"; it just factors in loading times, which vary from machine to machine. You have a consistently accurate measurement of time either way.

If you feel the desire to set up an autosplitter RTA run, feel free to let us know.

Dealt with.

No, we're not. My stance hasn't changed: it's accurate, and you have to deal with loading times as part of that.

An autosplitter would totally be fine.

No one knows for sure. Even before SDG, there was noticeable difference in the time we actually spent playing the game, and the time the leaderboard gave us. A running theory is that cutscenes, area loading zones, menus, and pausing all might affect it, but there's no concrete set of variables that we've been able to discern thus far.

Oh, and thread locked.

As I've previously stated, the in-game timer is an inconsistent measurement of time that isn't used; this decision is made primarily based upon two key factors:

1. SDG foils the accurate measurement of time, many times in ways we do not fully understand. (If you can prove, without a doubt, that this timer somehow provides an accurate measurement, then my hat's off to you.)
2. RTA measures the run from start to finish, loading times included, accurately and consistently (not counting extremely rare cases where the timer might crash, or otherwise malfunction).

While I understand that you feel this is unfair, this is an aspect of speedrunning a game on a PC that has existed ever since the hobby began, and something that the rest of the community inherently understands, accepts, and generally does not view as a point of contention. Perhaps setting up an auto-splitter for Guacamelee! is something you might consider, as this will allow you to eliminate timing loading times as part of the run, and if you do decide to proceed with making this happen, we would be happy to see the results.

The use of an external timer for RTA still remains the de facto method for an accurate time measurement in many speedruns in spite of any loading times. If you cannot accept this, then I suggest finding another hobby.

Good day, sir.

Yo, thanks for the heads up. Everything's updated so that we have subcategories for any possible combination of difficulty/# of players.