User talk:Markfeh


 * Past Discussions
 * 1

About moving Hero descriptions
Based on your edits, I think you don't know how to do that properly. Your edits deleted some rows from  table, and some pages that depend on it might be broken. Here are what you should do:
 * Edit Hero Infobox so that it stores descriptions to the  table (you already did).
 * Ask an admin to recreate the table.
 * Copy descriptions from HeroPageText to  parameter in all Hero pages, but DO NOT remove HeroPageText (this task can be done by a bot).
 * After all pages were edited, ask an admin again to replace the old  table with the new one.
 * Check all pages that query  table, and fix them so that they query to the new Heroes table.
 * Remove HeroPageText in all Hero pages (this task can be done by a bot).
 * Ask an admin again to delete  table. --RainThunder0 (talk) 14:05, 12 February 2019 (UTC)
 * Thanks for all of the information. I have done this before with MoveType Infobox and WeaponType Infobox, but it is a bit more complicated since there are still 327 heroes that need their descriptions moved from HeroPageText to the  parameter. That's too much for me to do manually. My plan was to ask someone to use a bot (I don't know how to use bots.) to move descriptions from HeroPageText to the   parameter in all Hero pages, and remove HeroPageText at the same time. Then I was going to ask an admin to delete  and replace  and . After that is done, then HeroPage needs to be modified to query for descriptions in  and . Markfeh (talk) 16:35, 12 February 2019 (UTC)

Unnecessary parameter removal
Please don't remove parameters from templates for no reason. Regarding your recent Hero page edits, whoever added the parameters like,   probably had a reason for doing so. They are parameters with possibilities, and there is no downside to them being there. They can potentially be used in the future, and also happens to be the only place this data is stored. Please do not remove parameters for no other reason besides just that you think that they do nothing. should not be removed. Unknown type information and empty, N/A, 0 or other information of similar nature are not the same thing. Endilyn (talk) 01:56, 21 February 2019 (UTC)
 * and  are not defined in Hero Infobox or .   already adds what they probably did originally. If there are more rarity demotions in the future another property can always be added. Markfeh (talk) 02:38, 21 February 2019 (UTC)
 * It does not matter whether it is implemented in the template or described in the documentation or not. This is why I called them parameters with possibilities.  in Heroic Ordeals map layouts is not implemented or documented but that does not mean there is a reason to remove it. A lack of a perceived reason to keep something does not automatically equate to a reason to remove something. If you are removing information you should remove it because of a reason to remove it and not a lack of reason to keep it, especially is there is a possible, however minor, benefit, to keeping it, but no downsides.  I overlooked the demoted_240 when posting, and your reasoning that demoted_240 already contains all the possible data these parameters could have is sufficient reasoning. I just checked and since the old demotion date and old rarities are constant and exactly the same for each Hero, the single property can be expanded to all of the needed information (if Intelligent Systems had not demoted everyone based on a single pattern with no exceptions, or had demoted more than one rarity tier, demoted_240 alone would not be able to contain the equivalent amount of information). Endilyn (talk) 01:37, 22 February 2019 (UTC)

Move pages, don't paste to a new page
If you need to move a page but lack the rights to do so then you can ask an admin and wait. It's not particularly time vital that all skill pages be moved this instant. You have effectively erased page history for all of those skill pages you moved. Endilyn (talk) 04:00, 1 March 2019 (UTC)

Also, moving skill pages was in the to-do list's larger more involved tasks for a reason. Actions should be carefully reviewed before performing them, as there may be additional requirements/consequences that are not obvious at first glance. You cannot simply only rename the skill and make an edit to the Hero page to complete the task. It is involved because you need to replace all instances where the page name was used. This is also listed in the requirements for this task. This includes, but is not limited to, map pages, and Children of the Shadow for example has a broken display for Soleil now. The next time you do a task in this list you should test your changes as you go along. If you do not know the extent of your changes, you should have tested and moved only one skill page, and verified the extent of any damage that may have caused with that change if any, before doing the page moves for the rest. Endilyn (talk) 04:10, 1 March 2019 (UTC)

WikiName
It seems that you may not know the purpose of the WikiName fields judging from some of your interactions involving the field, such as removing it from some templates, setting Berserk Armads's WikiName to "Armads", or using "Firesweep Lance+" as a WikiName. You can read more about the field at Project:Tutorials/Cargo. Endilyn (talk) 07:33, 2 March 2019 (UTC)

UserProfile
I sometimes comment because I want to say something quick/short/simple/whatever. If you don't like gamepedia's UserProfile system, then that's fine, you are not obligated to respond to anything posted on your profile. That message telling others to use your talk page is fine as well. However, removing comments of others for no reason is extremely discourteous (and basically amounts to censorship). Users have the freedom to use any system of communication they want, be it talk page or UserProfile. Endilyn (talk) 02:00, 6 March 2019 (UTC)

Template editing
It seems that recently when you edit a template you publish an edit for every minor test made, sometimes resulting in no net change being made. When making complicated edits to live templates used around the wiki, if you can please try to preview your edits before publishing them, especially for very important templates used in many places. This might be helpful to know: anything in the noinclude section of a template allows you to preview unsaved changes. This means that for example, if you edited a template named foo and put in noinclude, when you hit preview your changes affect what  shows in the preview, even if it hasn't been saved yet. Alternatively, if a template cannot easily be tested because it depends on the page name or something like that, you can try using or creating various test templates like Template:Hero Infobox Test or Module:Test3, then copy the source to the real template afterwards. Endilyn (talk) 04:03, 13 March 2019 (UTC)
 * Usually when I'm testing changes to a template the changes don't show at all (unless the template does not have any and/or in it). This happens even when I add something like between the  tags and then hit preview. I don't know if it is a problem with the devices I use, the browser I use, or the wiki editor, but changes to a template never show up for me until after I've saved the change. Markfeh (talk) 04:37, 13 March 2019 (UTC)
 * I've just tested with stock Google Chrome and Firefox (no cookies, cache etc., logged out) and it seems to work fine and is enabled by default. It doesn't appear to be a browser issue. Are you using the source editor? Have you accidentally turned it this feature off in preferences somehow? I'll let you know if I ever figure this out since this feature is immensely helpful. Endilyn (talk) 04:54, 13 March 2019 (UTC)
 * I have tested tested with the same things, and it just doesn't seem to work for me. I have been using the source editor, the only thing I disabled in in the editing tab of my prefrences was the visual editor, because it is too cumbersome to use. Markfeh (talk) 05:09, 13 March 2019 (UTC)
 * I think the issue is that the "Show previews without reloading the page" must be unchecked for this to work, since it doesn't work for me if checked. See if unchecking it works for you. Endilyn (talk) 22:08, 23 April 2020 (UTC)

So, what warranted the Builds pages for Valor and Experience passives being removed (according to me)?
First, as I mentioned in the Delete template, these passive skills provide no benefit for use in the majority of gamemodes if you discount the opportunities where SP can be gained (because experience points can only be gained until you hit Lvl. 40). And yeah, my method clashes with the idea for consistency on this Wiki which makes quite a difference compared to me simplifying the daily Hero Battle maps rotation, but it still stands that for serious play and Chain maps you should (when you can) swap out the Exp/Valor passives for a desired one. --TheBreakingBenny (talk) 10:25, 9 April 2019 (UTC)

Low quality images
It appears the image you've uploaded for Ardent Durandal is lower quality than one directly from the game files. Please upload the highest quality images. If there is an issue, I am not sure what the cause is but when handling game files please verify that your image editor and webp converter are lossless and adjust settings when necessary. Endilyn (talk) 20:52, 28 June 2019 (UTC)
 * I found the image here. Does uploading files to Imgur cause them to lose quality? I'm unable to root my phone so I can view the internal files directly, so I rely on datamines from gamepress or Kaz Kirigiri. However, Kaz Kirigiri tends to bundle the legendary/mythic hero files with the files for the next new Heroes banner, so I'm stuck with using the files on Imgur. Markfeh (talk) 00:14, 29 June 2019 (UTC)
 * Then please avoid doing that. There is no rush or deadline to upload files on the wiki and it is better to do things correctly rather than hastily. There is no point in a game resource if all it does is take from another existing resource. It also becomes [ clear info is copied] when the same errors in GamePress are reproduced on this wiki as well. Please verify your information before adding to the wiki. If you still are uploading files that does not come from you, you should at least note the source in the description. Endilyn (talk) 06:53, 3 July 2019 (UTC)
 * I set up the emulator and I can access all the files if you want them. --Ale1991 (talk) 01:26, 5 July 2019 (UTC)
 * I would greatly appreciate you sharing them with me. Thanks in advance. Markfeh (talk) 00:04, 8 July 2019 (UTC)
 * I have to find a convenient way to do this. I was thinking about an FTP server on my display-less EEEPC but recently it won't stay connect to wifi. Maybe you can try to set up an emulator. --Ale1991 (talk) 06:28, 23 July 2019 (UTC)

2019-12: Despite being told this before you seem to have done it again with Triandra's unit artwork. The differences this time are more visible than with Durandal. There wasn't even a re-upload template so you weren't intending it as a temporary replacement either. Once again, do not upload files from sites like gamepress or archives online unless you can verify they came unmodified directly from the game files. It looks like you downloaded a .png file and then converted it into WebP, which is a file format that has problems with generation loss. There is no guarantee the .png file you downloaded either was lossless, because GamePress compresses images (in a lossy manner) to save traffic. There are also lots of online .webp to .png converters that convert .webp to .png incorrectly, in that they do not produce the exact same output as dwebp. The WebP files are on the wiki because that is what the files in the game are, not because WebP is some sort of preferred format. Endilyn (talk) 01:43, 7 December 2019 (UTC)

About Template:Passive
Sorry for reverting your edits. They do work on skills that have tier 4 like Steady Stance, but seem broken on everything else. --RainThunder0 (talk) 23:26, 20 June 2020 (UTC)
 * It should work now, I forgot few sets of closing braces for some of the if statements. Markfeh (talk) 00:47, 21 June 2020 (UTC)

Whitespace help
Endilyn (talk) 07:26, 21 June 2020 (UTC)
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }
 * }

Infobox actors
If it's not too much trouble, for the time being could you revert the changes of merging actorJP parameters into a single parameter? Module:Unit Infobox has planned functionality to allow an infinite amount of actor arguments (actorJP, actor#JP). This method does not use a comma delimiter and thus would be able to handle potential artists that have commas in their names or usernames. Endilyn (talk) 01:44, 26 October 2020 (UTC)
 * Can it wait until Module:Unit Infobox is used in ? For now I feel it's easier to have one parameter for all English voice actors, and one parameter for all Japanese voice actors. If the comma delimiter is the issue could change the delimiter to another symbol that is unlikely to be used in names or usernames. Markfeh (talk) 17:29, 26 October 2020 (UTC)