User talk:SBEyes

Thanks
Hey thanks for welcoming me I will help you with anything. I uploaded all the images and hero bios just tell on my talk page what you want me to do next and how do I become part of the curse team? Viperroos (talk) 03:00, 9 December 2013 (UTC)

Adminship request
Hello. I wanted to ask you if you could grant me admin rights so that I can update the front page on this wiki, and any other protected pages that might need it. I had been working on this wiki in the past but eventually stopped because I didn't really play the game. I still don't play it much, but I feel the need of atleast help in what I whichever way I can. I've been an admin at Smite, Prime World and Infinite Crisis (three different MOBAs) wikis in gamepedia for a while now, so you can trust I have no ill intentions.--Malvodion (talk) 16:04, 8 December 2014 (UTC)
 * The content for the main page isn't actually protected because it's on section pages: Strife Wiki/Section 1, Strife Wiki/Section 2, Strife Wiki/Section 3, and Strife Wiki/Section 4. You'd only need admin rights to completely redesign the page; adding links and even new boxes to each section is something anyone can do. (The protection there is meant as a light defense against a casual vandal.) You can use View Source on the main page and the "Templates used on this page" at the bottom to find quick links to each section as well. As for giving you administrative rights, I have no opposition to doing so, but I'm not the primary liaison on this wiki anymore. I'll bump it up to User:Xerozohar. OOeyes 17:23, 8 December 2014 (UTC)
 * It is done. :) --Xerozohar (talk) 17:38, 8 December 2014 (UTC)
 * Oh, I see. I didn't remember that system. But anyhow, thank you. I'll start cleaning up the site a bit ASAP (though I can't really promise a full restoration, I'll do what I can.).--Malvodion (talk) 20:37, 8 December 2014 (UTC)

About the familar and item pages + hero stat tables
Looks like a fair portions of the information is wrong, mostly the cooldowns which have way too many 0s, and certain descriptions with random numbers written on front of it, and the items's recipe cost is displayed on the wrong spot, while the overall cost (component+recipe) isn't shown at all. I can fix it, but it could be undone by a future update. Example: Fervor Boots. Also: Would it be possible to automate the display of the item's component? The data already mentions wich items are used.

Familiars seem to have a similar issue with their abilities aswell, along with how the tags are displayed. Ex.: Shadow Stalk. Also I found the reason why the wiki has issues displaying the new familiar's abilities: There is two abilities that share the same name, for different familiars. I'm not sure how to correct this either.

By the way, looks like the hero pages are still trying to show armor and magic res. on the stat tables. I'd like to fix all of this myself, but I honestly have no clue what to really do, and I'm terrible with anything that goes beyond adding content...--Malvodion (talk) 06:46, 27 February 2015 (UTC)
 * Ah. yeah, I forgot to hit the hero stat tables yesterday. I probably won't be able to look into anything today due to surgery--most likely I'll have to tackle this tomorrow. As for abilities with the same name, this is what the  parameter documented on Ability infobox is for. There isn't a good way to automatically resolve same name issues, so that's there to help editors resolve them when they figure out how they want to deal with name collisions on their own. (In this case, maybe something like adding (tier 1), (tier 2), etc. to the page names and then connecting them manually perhaps?) &mdash;  oOeyes  [[Image:User-OOeyes-Sig.png|link=User talk:OOeyes]] 10:56, 27 February 2015 (UTC)


 * Looks like the changes I made to the familiar's abilities the other day worked (but took a while to take effect) so I guess thats fixed? Now whats left are the hero tables, and the item pages.
 * For items, what I was thinking was to make them look like a mix of the hero infoboxes, and the item infoboxes in this other wiki I maintain: Smite Wiki, showing the cost of the individual item or recipe, and then a total cost showing the overall cost, with passive and active effects (and cooldowns, if they got any) being displayed at the bottom. It'd make it easier to work with, and to read.--Malvodion (talk) 21:02, 27 February 2015 (UTC)
 * Yeah, unlike ordinary wiki templates and such, the automatic queries tend to have trouble with the wiki cache holding on to old values longer. MediaWiki's caching system wasn't built with this level of automation in mind and it tends to only notice that a change to one page affects another if a page is directly using a template or image that is changed, but this level of automation means that other types of changes can affect page content. It doesn't look like this is going to be changed anytime soon, either, and admittedly, tracking all the indirect links isn't trivial. When you need to force things along, making null edits (just edit and save with no changes) should cause a page to update immediately, though this needs to start with the item/hero/familiar pages themselves because that's where the properties are actually set. In extreme cases, you can always ask me to run a bot over a category or over pages using a specific template to hurry things along when a lot of pages are affected.
 * Hero tables should be fixed now, and components being missing was just an oversight because Xerozohar was just basically plugging into the existing infoboxes, which didn't have the components shown. I added a row for it now.
 * I'm confused on what to do with the recipe cost issue. We only have one cost field in the actual data. There's not an immediately obvious way for me to determine which type of cost it is. I could ask on Monday if there's anything more in the data, but I rather doubt it. Unless maybe I can assume that any item with at least one component will have a recipe cost instead of a normal cost? Otherwise, we may not be able to be able to automate that, though I could add a parameter to Item infobox that would let editors quickly identify items that need the cost swapped to recipe cost.
 * I can probably do a more thorough recipe listing in the infobox, but it's probably best to wait on that until the recipe cost issue is sorted out. &mdash; oOeyes  [[Image:User-OOeyes-Sig.png|link=User talk:OOeyes]] 19:38, 28 February 2015 (UTC)


 * Yes, we only have on cost field, but wouldn't it be posible to add another, separated one? If the bots can't automatically add the total cost (that is a value displayed in the game) then we (I) can just try to keep it up to date manually. But as long as the information from the bots about items is broken and/or out of date (like the previously linked boots having a cooldown of 13000 seconds), I can't do much there.


 * Also it looks like the tables broke, but for other stats now (Chester). And I think mitigation/resistance are still broken, since on the infobox it says the default is 10 resistance (and doesn't display mitigation), and the stats table says the first level is 54, which means one of them is wrong. Sorry to add more work to you, but someone has to take care of this site, and I only have the level of knowledge of a regular editor...--Malvodion (talk) 20:52, 28 February 2015 (UTC)


 * It's possible if they're separate in the game data, but if that were the case, I don't think the importer would have been built to combine them into a single field to begin with. That's not how he usually does things, though I will ask on Monday. The point is, I don't know if there's any automatic way to distinguish which are recipe costs. Again, maybe the cost is a recipe cost for every item that has components? I have no idea if that's a safe assumption. If not that or some other simple rule the importer or templates can use, the best I can do is add a parameter to the item infobox for editors to be able to manually flag it.


 * And yeah, I forgot about adjusting the times. The time is probably just in the data as milliseconds, just need to add a simple division. &mdash; oOeyes  [[Image:User-OOeyes-Sig.png|link=User talk:OOeyes]] 21:55, 28 February 2015 (UTC)


 * Oh, and the tables, I thought the headings had already been removed rather than new ones added. Resistance doesn't appear to increase with level, not that we saw in the game data. I'll ask about Mitigaton on Monday, as that stat didn't mentioned in our discussion. &mdash; oOeyes  [[Image:User-OOeyes-Sig.png|link=User talk:OOeyes]] 22:04, 28 February 2015 (UTC)

About the WIP frontpage
Its looking good, but I think the "about" section should probably go somewhere on the top. Maybe above the video section?

Also I think we'll probably need to reduce the icon size for those buttons since this is a moba and (if it manages to survive beta) it will get more, and more characters, and the page will just get bigger and bigger. 100x100 would probably be a better size. It'd also improve the loading times on older machines/slower connections aswell.--Malvodion (talk) 01:14, 9 March 2015 (UTC)
 * I disagree with moving the about section up. Most visitors will already be familiar with the game as visitors tend to hit wikis for specific information more often than general. Newer players are more likely to look over the whole front page anyway, being they're already less likely to know what they're looking for, and we already have the video above-the-fold that serves a similar purpose while being visually interesting as well. While I do think it's worth front-page status, I just don't believe it's worth taking up above-the-fold real estate, especially given this is an already released game. These about sections are more important for games that aren't yet out (especially since we usually need something to pad the page for those).


 * As for the 150x150 size, the design already shrinks them to 120x120 and then 100x100 on smaller displays. In fact, unless your browser has at least 2420 pixels of width, you're already seeing them at 120x120. Also, these images are pretty small in file size even at 150x150 (coming in at about 13kb each and will be cached by the browser anyway). If there do get to be too many heroes, we can shrink them later through the CSS styles, which is a task that would take only a matter of minutes. Right now, things seem to be balancing fairly well at different resolutions, so I think it's best to hold off for now. &mdash; oOeyes  [[Image:User-OOeyes-Sig.png|link=User talk:OOeyes]] 01:52, 9 March 2015 (UTC)


 * If you say so. The buttons look a bit off IMO, but it is still an improvement.--Malvodion (talk) 03:28, 9 March 2015 (UTC)


 * Yeah, that reminded me the image buttons were supposed to be staying to the image size; side borders were not intentional. Hadn't gotten to testing that on the other wiki yet. They're working as intended now. You should see it when your browser grabs the new styles. &mdash; oOeyes  [[Image:User-OOeyes-Sig.png|link=User talk:OOeyes]] 05:31, 9 March 2015 (UTC)


 * Ah. They look good now.--Malvodion (talk) 06:00, 9 March 2015 (UTC)