User talk:Wookipan

boot camp disambig

i thought a disambig is only for 3 or more? Naleksuh (talk) 17:56, 7 August 2019 (UTC)

Claymore is one that I can remember off the top of my head. I made the disambig because (Like the disambignote template says) disambigs are used when 2 or more pages have the same or similar titles and I felt it was appropriate instead of just linking to the bootcamp map page.
GrampaSwood (talk) 18:07, 7 August 2019 (UTC)

Regardless of the number of similar subjects in question, as long as there's at least two subjects (titles) of the same kind but they differ in terms of content, it is eligible to be created as such. GrampaSwood did the right thing here, as a redirect would be insufficient in this case.  Wookipan (talk | contribs) 19:24, 7 August 2019 (UTC)

wouldn't it be best to automatically point to the most likely one in obvious cases like boot camp? Naleksuh (talk) 20:19, 7 August 2019 (UTC)

It would, but look at the Claymore one. People usually mean the Claidheamh Mòr (wrote that without lookg up how it is written btw, just flexing) instead of the sword that is actually a claymore. But for sake of consistency, disambugs are used.
GrampaSwood (talk) 20:24, 7 August 2019 (UTC)

Yeah i can understand in the case of claymore but with boot camp they are 99% likely to mean mvm, so a notice at the top would probably be sufficient. Naleksuh (talk) 20:27, 7 August 2019 (UTC)

Hey I need some real help fast!

I had lately happened to make 4 of Helltower Hell% 27s_spells-icon.png which would be of 96 x 96 because I was update my profile and needed a image for my Contributions like you have. So I would you be able to fix it because I have no idea how to do it... — The preceding unsigned comment was added by Doktorjan (talk) • (contribs)

You could just save the original file and upload it as your own user file, there's absolutely no need to overwrite it. That said, please do not alter and/or overwrite files that were extracted from the game as they must retain its original size format for consistency purposes.  Wookipan (talk | contribs) 19:19, 15 August 2019 (UTC)

Thank you for the help--Doktorjan 16:51, 18 August 2019 (UTC)

About that beer wikichievement I owe ya

Wikichievement	Awarded by	Reason
Helping Hand Help other users to improve the Team Fortress Wiki with constant tips and coordination.	Grampa Swood	Wikichievement unlocked! For helping me with the Davy Jones responses page.

It's me, wooki, Swood from the TF2 wiki.
GrampaSwood (talk) 17:33, 24 August 2019 (UTC)

black mesa is evil aperture science ftw Naleksuh (talk) 19:25, 24 August 2019 (UTC)

Did you submit your status report to the administrator today?  Wookipan (talk | contribs) 17:35, 28 August 2019 (UTC)

Use(r) image fix

Yeah, thanks for the move. I have been trying to upload and edit while riding in and out of phone data coverage on Iowa Interstates on marginal charging. I could wait until I get home tonight, but I wanted to do something with my time. I want to fix the rotation, but don't have a stable phone connection. M I K A D O 282 oOOOOo oo oo (talk) (Help Wanted!) 15:46, 22 September 2019 (UTC)

Yep, no problem! I'd advise you to avoid editing on phone, as some things can easily go unnoticed, or you may hit the 'save' button by accident while editing.  Wookipan (talk | contribs) 16:04, 22 September 2019 (UTC)

I acknowledge your point; but, since I started editing, I have edited on the phone a lot. Using preview, it generally works fine. But I haven't figured out how to preview the upload. I was wanting to realtime photojoural the trip, but, as you see, in this situation, it turned out impractical between connectivity and charge issues and family times, it could be hours before I could check on the result of the upload (and one upload got scrambled). M I K A D O 282 oOOOOo oo oo (talk) (Help Wanted!) 18:26, 22 September 2019 (UTC)

About Category:Developer commentary

Greetings, Wookipan. I noticed you redirected Category:Developer commentary to Category:Developer commentary media, which currently has no pages in it at the moment. So I removed the redirect. Please let me know if I shoudn't have done this.

07:39, 6 May 2020 (UTC)

Ah yeah, I completely forgot that. At first I thought the pages wouldn't show up due to cache issues, but it appears the redirect doesn't work on categorized content - so it would need to be changed manually. Either that or move-categorypages isn't working correctly. Thanks for removing it, for now.  Wookipan (talk | contribs) 17:27, 7 May 2020 (UTC)

Fire Fighter Ultra style rollback

When you moved the Ultra style images for the Fire Fighter with the Ultra style suffixes, you should've left a redirect. Both the standard "RED ___.png" image format and "RED ___ <style name>.png" format images are needed for team-colored style images to properly display in both paint variant tables and the infobox sidebar team color image sections. The sidebar uses "RED ___ <style name>.png" images even if they're representing default styles, when style headers are present in the sidebar; and the paint variant tables use the standard "RED ___.png" format for default styles. I've moved the Ultra images in particular again, and I think it's just a thumbnail cache thing to wait out now; but in the future, I'd like to ask that you leave redirects instead of just reverting a style suffix out. -ThatHatGuy (talk) 04:32, 9 September 2020 (UTC)

Heyo, thanks for the explanation but I'm well aware of how it works, hence why I moved the files in the first place.

However, I regret to inform you that it's actually the other way around; you see, since you added a redirect from the RED/BLU variant to the styles variant, the paint table is now unable to tell whether the unpainted team-color variant is present, because the files are set to redirect to the styles variant instead, of which doesn't match with the rest of the file names in the paint table for the default style.

On a bit more technical level, the paint table sees the other paint variants as part of the default style collection because of the file name, but as a suffix is detected prior to the paint value, it creates inconsistency and thus are unable to display them as it's no longer a part of that collection, so it's actually not a cache issue. Purging the page will display the default styles in the infobox due to the images being suffixed with the style name, but the gallery (same with the styles table because of the file path) still can't (and won't) display the unpainted team-color variants because of the afforementioned issue.

What you merely should've done was to add a redirect on the default style files to the RED/BLU variant, and that would fix it. Now, I will kindly ask that you move the files back, which will add the redirects accordingly. Thanks!

And yes, I do tend to not leave redirects out of habit, so that was also a mistake on my part that I haven't had the time to fully look into. My bad.  Wookipan (talk | contribs) 19:26, 9 September 2020 (UTC)

So it's clear by now that it's not a thumbnail cache issue; among other reasons, that would've fixed itself by now. But I don't quite understand exactly what you want me to do, because it sort of got buried in all that; I thought moving things did create redirects, which is what I wanted to do in the first place. I wanted to move those images to their article's sidebars. I thought they would've redirected properly on their own, but they didn't -- so how exactly do I fix that, as a step-by-step thing? You want me to move the images back, I understand that far; then what do I do? -ThatHatGuy (talk) 10:56, 13 September 2020 (UTC)

Sorry if I made it sound too complex, but all you really had to do was move the files back to their original naming scheme, i.e. RED/BLU Fire Fighter.png and the redirects would be applied automatically. As it's been a couple of days now, it's about time this got fixed, so I went ahead and moved the files; but feel free to use this for future reference.

Simply put; the redirects should instead be on RED/BLU Fire Fighter Ultra.png and then point to RED/BLU Fire Fighter.png — it was doing the opposite of that.

The rule of thumb is, that the unpainted team-color variants must be named as RED/BLU ___.png for them to display in the paint table with the rest of its paint variants. We can then re-use said images for the default styles by adding a redirect from the style images (if the page/file exist) and then point it to the RED/BLU variants, and because the style images are being redirected instead, the style headers will be able to return the RED/BLU variants since it looks for the style name suffix, which is redirected to the RED/BLU variants. Now, we could also just upload the style images seperate from the RED/BLU variants, but that would result in duplicates, and overall, is a silly workaround. Hope that somewhat sums it up.  Wookipan (talk | contribs) 18:53, 13 September 2020 (UTC)

Okay, thank you for the clarification; I had also done that same thing to the Bird's Eye Viewer's Informant style, so I've moved those back to the standard team color images as well. They appear to have thumbnail issues at the minute after being moved, but that should clear up, I think? I don't really know anymore. This has shattered everything I thought I knew about this. -ThatHatGuy (talk) 23:24, 13 September 2020 (UTC)

Sure thing. And yes, it's just a cache issue and should resolve itself in a couple of days. You can also try purging the page by adding ?action=purge at the end of the URL. It may not always work though, and sometimes it's better to just open a private browser as it doesn't cache the session.  Wookipan (talk | contribs) 21:39, 14 September 2020 (UTC)

Thank you

Cheers for the Windows 95 effect, can’t thank you enough! Calcium fiend (talk) 13:00, 2 April 2021 (UTC)

Haha, you're very welcome! I'm just glad to know that I was able to bring a smile to people's faces. You can always visit the TF95 main page from here if you ever happen to get tired of the custom CSS that you've added to your common.css.  Wookipan (talk | contribs) 20:11, 2 April 2021 (UTC)

I am once again asking for the CSS implementation.

So um...I don't want to bother you anymore but have you done the CSS thing? I tried to reach you on the IRC but you were offline, so im resorting to this method. I would really like to improve my helpful overviews but I can't, so...could you please do it? Thank you in advance. Lolimsogreat21 (talk) 10:20, 3 July 2021 (UTC)Lolimsogreat21

I have not, no. I've simply been too busy outside the wiki, as evident by my lack of edits and IRC absence as of late. I've got some free time this week, though, so I'll try and get it done by then.  Wookipan (talk | contribs) 20:45, 3 July 2021 (UTC)

Thank you very much for the effort.

Lolimsogreat21 (talk) 21:22, 3 July 2021 (UTC)Lolimsogreat21

Suggested touchup to map overview icons

Hi,

The map overview project looks sick. I wanted to make some little touchups to the marker icons used on it so they look consistent and display better on all different types of devices and monitors. It's small, but I feel like any sort of improvement could be nice.

You can view that here (and the css here) and let me know what you think. ~ Boba 04:39, 12 July 2021 (UTC)

EDIT: I also made it highlight the markers when hovered over for extra visibility. There's still a version without this commented out in the css. Again, let me know what you think. ~ Boba 21:57, 12 July 2021 (UTC)

Nice, thank you! I wasn't too happy with the border thickness on the map markers myself and wanted to change them at a later time. Neat idea with the highlight effect, I'll be sure to add it.  Wookipan (talk | contribs) 20:07, 13 July 2021 (UTC)

 Done.  Wookipan (talk | contribs) 20:48, 13 July 2021 (UTC)

Thank you!

I would like to present you the following award for your selfless work on the map overview template.

Wikichievement	Awarded by	Reason
Helping Hand Help other users to improve the Team Fortress Wiki with constant tips and coordination.	Lolimsogreat21	Wikichievement unlocked! For mingling with the CSS code just to implement the changes I (Alongside some other people) wanted so much.

And I would just like to ask you one more question please. I am currently in the process of updating all of the old Helpful overviews and the process of guessing and trying to estimate the position of the marker is quit tedious. Now, if this is the way I have to do things, then so be it. I'll happily updated all of the Helpful overviews even if it isn't quit convenient, but in your template you mention something about copying then map image, and then using the image of the marker to get the exact X and Y coordinates. I'm not quit sure what do you mean by that and would like you to elaborate further, please.

Lolimsogreat21 (talk) 20:30, 12 July 2021 (UTC)Lolimsogreat21

Thanks for the Wikichievement, appreciate it. That part wasn't written by me and just part of the original documentation and was left in temporarily, hence why I mentioned that I'd improve the documentation. You seem to have figured it out, though.

If you're somewhat technical advanced, then I'd highly recommend you to use Chrome's devtools, also widely known as 'inspect element'. Once open, click on the top icon to the far left, then select the marker icon element. Make sure it's the whole element (div.marker). After doing that, make sure you're in the right tab, labelled 'Elements'. In the right side there should be a window divided into sections, with the first being 'element.style' which contains the coordinate values. Simply click on the value and use the up/down arrow keys to rapidly increase/decrease the pixel values.  Wookipan (talk | contribs) 20:07, 13 July 2021 (UTC)

MediaWiki:Common.css suggested changes

Currently, all forms of Main Page hide the firstHeading (the page's title at the top of the article). I think we should do that for Main Page (Classic) as well. ~ Boba 20:25, 10 October 2021 (UTC)

 Done — Tarkipan lm(pt-br) 22:19, 10 October 2021 (UTC)

Curse you, Tarkipan! Staaahp stealing my job! >:(  Wookipan (talk | contribs) 19:28, 13 October 2021 (UTC)

Suggested change to Team Fortress Wiki:Wiki Cap#Eligibility factors

Hi,

I was recently nominated for a Wiki Cap and it has come to my attention that outside sources are able to affect staff votes. I think this can be better clarified in the Eligibility factors page. Currently, the only factor even relatively pointing towards that is "Are helpful, cooperative and community-minded attitude at all times.", which I think is very vague and doesn't clearly outline that fact. The page was, after all, written in the context of the wiki itself, and not everywhere on the internet as a whole. I think another eligibility factor should be added to clarify this, though editing the current one to make it more specific works as well.

Thanks. ~ Boba 22:49, 6 November 2021 (UTC)

I can understand why you find this upsetting. This is all a rather atypical case, and as such it really does not need to be elaborated on any further.

The factor in question is a clause which outlines the fact that you, as a candidate or future cap holder, are expected to treat fellow community members with respect as well as being cooperative on the wiki. While it is indeed written in the context of the wiki, the Wiki Staff are not obligated to tell people how to act outside of the wiki - either before or after receiving the cap - but the voting staff members are free to choose whether or not they want for the nominee to receive a cap, even if it's based solely on attitude/behavior, and whether said behavior took place outside of the wiki or not still makes it valid.

Given some past incidents on the wiki, we have reason to believe those outside sources to be true, and as mentioned earlier it is entirely up to the voting staff members to reach a verdict. If declined, the verdict still isn't permanent, but it means that we cannot endorse your actions at this time.  Wookipan (talk | contribs) 23:26, 27 November 2021 (UTC)