User talk:SadakoTetsuwan
From the Kingdom Hearts Wiki, the Kingdom Hearts encyclopedia
Jump to navigationJump to search
The ultimate battle for KINGDOM HEARTS is upon us.
| |
We hope you enjoy your time on the Kingdom Hearts Wiki! Before you contribute, please see the following:
Thank you for joining the Kingdom Hearts Wiki community! We look forward to working with you. May your heart be your guiding key! |
Hey, there. I just wanted to let you know I'm working on a possible template for the Keyblade stats for the KHUX wiki. You can see it here. Since I don't want the Keyblade pages to be the exact same on this wiki and yours, I made a template that has to be used once for every level, like how the Divine Rose page looks on the KHUX wiki. What do you think? Should I add or change anything? (I'm not done yet, but I thought I'd ask for your feedback.) TheSilentHero 20:52, 13 April 2016 (UTC)
- Wow, that's really elegant! I don't mind filling things in individually, so that's fine with me. I think any extra information could just be noted outside of a template, since additional information is fairly rare and can just be noted outside the template. SadakoTetsuwan (talk) 22:09, 13 April 2016 (UTC)
- The template is finished. Does the KHUX wiki already have the ripped images of the Keyblades and ingredients, and if so, is there a standard naming scheme (If there is, I can code it in the template so you have to add less information). If not, you can copy the images we have, as long as you give credit to the user who ripped them (I think). TheSilentHero 17:52, 14 April 2016 (UTC)
- I'd really rather we keep the same naming scheme, as it would make porting stuff between wikis the easiest. As far as crediting, if we do something like this, with a link back to the image on the KH Wiki, there should be no problem, and that could easily be automated so that all you have to do is pick the "KHWiki" license from the drop-down."We're werewolves, not swearwolves." (KrytenKoro) 15:35, 15 April 2016 (UTC)
- I agree that naming images the same would be the easiest, but it would seem pointless to add the KHX tag, since the wiki only covers KHX/KHUX. Would you be able to write the text for a template like that? I'm not very familiar with copyright laws and stuff. TheSilentHero 17:16, 15 April 2016 (UTC)
- It may still be worth having the game tag, even if there's only three games the wiki covers. Besides, like Kryten said, it would be quicker to port images between our wikis if the file names were exactly the same. TheFifteenthMember 18:56, 15 April 2016 (UTC)
- Having the license template would be fine--you guys have done your share of heavy lifting, too, after all! So far, I've just been using screenshots.
- It may still be worth having the game tag, even if there's only three games the wiki covers. Besides, like Kryten said, it would be quicker to port images between our wikis if the file names were exactly the same. TheFifteenthMember 18:56, 15 April 2016 (UTC)
- I agree that naming images the same would be the easiest, but it would seem pointless to add the KHX tag, since the wiki only covers KHX/KHUX. Would you be able to write the text for a template like that? I'm not very familiar with copyright laws and stuff. TheSilentHero 17:16, 15 April 2016 (UTC)
- I'd really rather we keep the same naming scheme, as it would make porting stuff between wikis the easiest. As far as crediting, if we do something like this, with a link back to the image on the KH Wiki, there should be no problem, and that could easily be automated so that all you have to do is pick the "KHWiki" license from the drop-down."We're werewolves, not swearwolves." (KrytenKoro) 15:35, 15 April 2016 (UTC)
- The template is finished. Does the KHUX wiki already have the ripped images of the Keyblades and ingredients, and if so, is there a standard naming scheme (If there is, I can code it in the template so you have to add less information). If not, you can copy the images we have, as long as you give credit to the user who ripped them (I think). TheSilentHero 17:52, 14 April 2016 (UTC)
- In the interest of keeping the ease of porting as a prime back-end consideration, I'm totally willing to go with any naming scheme you currently have in place. SadakoTetsuwan (talk) 21:40, 16 April 2016 (UTC)