Talk:Hades

Possibly usable notes - please review to cut down on purple prose and script regurgitation
--BbS--

Still building up his army, Hades noticed a strong dark and brooding warrior outside the Coliseum - Terra. Pretending to offer Terra the chance to learn how to master the darkness, Hades signed him up for the Games in the hopes that combat would force Terra to rely on his darkness and grow stronger. However, when it appeared that this wasn't going to work, Hades decided to manipulate Terra's final opponent Zack by controlling his darkness. However, Terra freed Zack, prompting Hades to give up on his plans and flee.

When Aqua arrived, Hades has been winning in the West bracket, earning the right to challenge the East bracket winner for the championship. Deciding to check out who his opponent is, Hades appears before Aqua, finding that she's just a "little bluebird". He makes the mistake of insulting Terra, by calling him a coward for not using his darkness. Facing off with Aqua, Hades called in a copy of the Ice Titan called the Ice Colossus as his back-up. However, Aqua defeated him, and Hades decides that he needed a real titan if he wants to take out heroes like Aqua and Terra.

--KH-- He later attends the meeting to discuss Jafar's defeat, where Maleficent again warns him about succumbing to darkness. Hades rebuffs the statement, instead helping her inform Riku that they have kept their end of the deal and located Kairi.

James Woods's Confirmation for KHIII
Well, it's not an explicit confirmation, per se, but it's pretty obvious that he's working on KHIII. Just putting the tweet here for future reference, to abide to our policy.-- 20:14, 30 March 2018 (UTC)

Unlock
Can someone please unlock the article? It's been long enough and it could use some updating. Soroxas (talk) 03:50, 19 August 2018 (UTC)
 * If a page is locked, changes to the page should be brought up on the talk page. What updating are you suggesting? 13:36, 20 August 2018 (UTC)


 * There's no reason for it to be locked anymore. That should be enough of a reason for it to be unlocked, I shouldn't have to justify it with further reasons, but here's three:
 * Hades will be in KH3, so it should be unlocked so people can help with KH3 eventually. You may say "but we can simply unlock it when KH3 is released", but it's always nice to prepare.
 * I would like to move images from his Gallery to illustrate the text.
 * Chain of Memories category is broken.


 * And I've occasionally stopped by the article a few times for other edits I can't remember right now. Soroxas (talk) 14:35, 20 August 2018 (UTC)
 * The first reason you gave is specifically why it was locked in the first place. It's not "always nice to prepare" when there is a history of multiple editors repeatedly using the opportunity to "prepare" to instead violate policy, which is why the page was locked. Pages don't get locked willy-nilly, they get locked when people were misbehaving, and get reopened when the opportunity to misbehave has passed by.
 * By wiki policy, there's nothing that can be prepared in advance of the game's release, beyond something like "SE has confirmed Hades will appear in KH3, within Olympus." or something similar. Is that what you're proposing to add?
 * Yes, you should have to justify it. That's how locking pages works, on wikipedia or any other wiki. I can't edit it anymore than you can, so I have to give a request to the admins of what changes I'd like to make, and they'll either perform the change themselves, or they'll decide the article is now safe and unlock it.
 * Mods: re: "broken category", this is due to the infobox using "Kingdom Hearts: Chain of Memories" instead of "Kingdom Hearts Chain of Memories". Please make sure to include this change in your next AWB sweep. 16:18, 20 August 2018 (UTC)
 * Personally, I think we can unlock this page. There are other pages on characters that are confirmed for KH3 that are not protected, and aren't edited to add that information. However, I'd like to hear the opinion of other admins first.
 * I actually did another AWB sweep yesterday, since I noticed there were some pages still using the colon, but I guess it must have skipped this page, because it's protected. 16:30, 20 August 2018 (UTC)