I suggest on the Item page to make sub-tabs for the weapon tab. Sub-tabs: Basic Weapons, Books, Guns, Misc Ranged Weapons, Legendary Weapons. Place the appropriate parts in these sub-tabs to quickly find the necessary things. (Example: )
That is, if someone knows the word that he wants to find, he goes to the Items page, presses ctrl+f and finds a link to the page? If he knows the word he needs in advance, why can't he use the search on the entire wiki on the main page? (huge line with a magnifying glass on the top right)
I did not understand anything from the second paragraph.
Still having issues. I think something in my personal JS might be causing an error. anyways; ~Fewfre
The align attribute is technically depreciated. Doesn't totally matter since browsers rarely remove html depreciated stuff if it has/had common usage, but the rule of thumb (from a web-dev point of view) is CSS should be used for formatting; align and other attribute are from the "olden days".
I don't use it since it's "bad practice" and switching between two ways is a pain for me, but I doubt it will break on anything in a good long time. Besides, technically using an inline style for this is also kinda bad practice (although they are depreciated).
That said, it should be fine. Even if some browser does actually stop supporting it (long time from now I assume), mediawiki might re-add the behavior behind the scenes. and even if they didn't, we could add some css to the site that made anything with that attribute left align.
On both pages. So that a person who visits the site not for the first time does not go far, but immediately finds the right one. And these are your resources, choose the design yourself. Just as a suggestion.
I generally prefer not to self-advertise on the front page; though in this case I think my tools are the only ones still actively used, so eh, why not.
I don't think they need anything that flashy drawing attention (especially over wiki content); added them to front page on the right side (or they could probably also go in the "Misc" section of main navigation table).
That box is meant only for the official game link. other links should either go in the navigation table, or on the right side. If the most popular page on the wiki only gets a normal link, I don't see a reason to make fan-made tools get more than that. I'm fine with adding links to the main page, just not as a green box.
Hi, I'm having difficulty using the Template:QualityRange. When I insert it into the table column, it is displayed in several lines. I can not find the reason. I would be grateful for the advice on the correction.
on the line below the template content, which counted as a new "paragraph", but only when used in a table (since in tables just one new line counts as a paragraph, but only the first time; not sure why, it's just a wierd rule).
I fixed it, but there's typically two ways to solve it; either put the noinclude on the same line the templates ends in, or use
html comments - nothing in them counts (including new lines), so it's a nice way to have newlines without the drawbacks.
Custom-common.less/links.less isn't in the MediaWiki: namespace
By default .less files don't do anything; you need to run a script to compile them
Hi, I’m having a little difficulty adding some .png images. When copying from the English version and writing to Russian, it shows an error: File extension ".png" does not match the detected MIME type of the file (image/webp). After I re-save the file in Paint program on my computer, it is written normally, but at the same time transparency is lost. Some images require transparency and I can’t find any information on how to record an image without losing transparency. For some reason, paint says that the extension of these files .heic
Unrelated; I noticed the wiki wordmark seem to have green in the background and seems a bit less crisp; just as a heads up, you can find wordmarks on wikis here: File:Wiki-wordmark.png (and thanks for reminding me to remove the dog head; probably should be removed now since dog update is so old; here's one without the head the person who made the wordmark made: https://i.imgur.com/5HC5ALH.png )
Sure there is; you just gotta use your imagination!... lots and lots and lots of imagination... =p
Fun fact: it was from one of thier really early pieces of concept art: Pre-alpha#Others (same with the top-right image currently used); just never bothered to change either since never found something that fit a whole ton better (to me).
Hi Fewfre, I'm wondering if you would be interested in having the Community Page activated on this wiki. It could possibly encourage some visitors to become new editors here, and therefore increase wiki activity. It can also direct user efforts to where their help is needed most. Let me know if you're interested in this feature, and I can arrange to have it set up. :) - Sitb(Message wall / Talk page) 11:14, June 15, 2019 (UTC)
Is there something about the community page that you don't like, and think Fandom could improve? I could pass along your feedback to staff and your recommendations could maybe have a positive impact on its development. :) - Sitb(Message wall / Talk page) 01:20, June 20, 2019 (UTC)
I thought I would reach out to you, since you are the only active administrator around here. I have recently been appointed as the Fandom Wiki Manager for this wiki. I am here to assist this community in an official capacity and act as a liaison between you, and full-time Fandom staff. If you, or any other users of this wiki ever have an issue or question related to the wiki (editing, templates, wiki design, or any other matters), please feel free to contact me on my message wall, and I will assist in any way I can.
I read the discord pages but there was no evidence to demonstrate that White(#FEFEFE ) does exist.
Over the past few months, I've noticed that many people mistake Light Gray(#EBEBEB) for White(#FEFEFE), and Light Peach(#FFD7C1) for Light Gray(#EBEBEB).
In addition, a lot of people do not know the correct way of dye color selection, resulting in distortion or error. (use PNG image format to preserve color values, and then sample the color of the horizontal line on the "e" of the dye's text)
Moreover, there are many sources of White dye on wiki Dye page, which indicates that many players should get it and means that the rarity of White(#FEFEFE) is illogical. In fact, we can only see Light Gray(#EBEBEB) instead of White(#FEFEFE).
As above reasons, I combined White(#FEFEFE) and Light Gray(#EBEBEB) rows on wiki Dye page days ago.
Finally, sorry about my bad English, I have done my best to express.
I think you're right that they are the same thing. I asked around a bit more and people can't seem to say for sure they are two seperate things. I also looked at every dye image I could find on discord (and even made a tool to see how dyes would look colored to make it easier), and EVERY one was light gray.
So for now I'm putting your edit back until there's proof a near pure white exists (and sorry for the trouble).
The dye page seems to be highly unreliable, with many sources that are incorrect or missing, and color values that are inaccurate or even nonexistent. I am at this moment unconvinced that the spring green dye exists at all, but I'm leaving it there for now.
I am currently making an effort to record every dye I come across, and correcting their colors and sources.
Anyone can check color values from screenshots of the dyes in PNG format as below page:
- English: color of the horizontal line on the "e" of the dye's text
- Chinese: any word https://imgur.com/a/yfS1ssP
I am aware of how the dye colors are obtained. Every edit I have made today has been based on screenshots I took myself, in PNG format, and I sampled the color of the horizontal line of the 'e' in Photoshop. The vertical line in 'D' works just as well by the way. I still have all the screenshots, and I can prove the edits I made were correct.
I have compared my screenshots with the ones posted above, and discovered a problem. It seems that the way the text is rendered is different based on the system or browser, and the color of the text is actually slightly different. As I mentioned above, the vertical line in 'D' is the same color as the horizontal line in 'e' in my screenshots, but not in the screenshots linked above. I also tried using the Chinese text, but for me it came out smoothed, and no better than the English text.
The page probably includes colors that look different on different systems or browsers, but actually represent the same dye.
A FANDOM user wrote: I have compared my screenshots with the ones posted above, and discovered a problem. It seems that the way the text is rendered is different based on the system or browser, and the color of the text is actually slightly different.
You're right, thank you for your test.
Different systems, browsers, or VGA Settings, such as resolution or DPI, can affect graphics and text rendering. But as far as I know, most people's Flash displays should be consistent or similar, and the big differences are relatively rare.
When I tested IE, Edge, and Chrome, I did see some differences in the text rendering, but the color values for the key areas were still the same.
My system environment: OS: Windows 10 v1803 Build 17134.648 IE: 11.648.17134.0 (Flash Player 32,0,0,156) Edge: 17.17134 (Flash Player 32,0,0,156) Chrome: 73.0.3683.86 (64bit) (Flash Player 32,0,0,156)
You can provide screenshots of your dyes and then add color values to the dye page so that there is more than one set of color values for a dye.
This is the better course of action I have in mind at present.
Fewfre's Dressroom is also a helpful tool for check dyes, I get a lot of help from it.
It is worth mentioning that dyes do not come only from food, there is a very low probability that they can be obtained from items, such as spring green dye from a fountain pen and white dye from a fire extinguisher.
Sorry for delayed response. Hmm, seems they messed up the linking a bit. Should work for now though.
So once you create a page on your wiki, you can link the pages between them by adding a language link at the bottom of the page on both. Not sure how to do this in the visual editor, but in source mode you would do [[en:English page name]] on the page on your wiki, and then add [[zh-tw:Tw page name]] on the English wiki's page. This will then redirect anyone visiting the wiki who speaks that language to the page on your wiki.