User talk:Trig Jegman

Welcome to StrategyWiki!
Hello Trig Jegman! Welcome to StrategyWiki. Thank you for your contributions. If you have any questions, just contact a sysop through their talk page or post on the staff lounge, and they'd be happy to help. If you need help editing, check the StrategyWiki Guide or visit the Discord server to chat. On the other hand, if you have ideas for StrategyWiki, bring them up on the staff lounge as well. To keep up-to-date with the goings on of the wiki, consider adding the noticeboard to your watchlist.

Please remember to sign your name when leaving comments on talk pages by clicking or using four tildes (    ); this will automatically produce your name and the date. Feel free to delete this message from your talk page if you like, or keep it for reference. Happy editing! —  Pro cyon  00:34, 21 September 2020 (UTC)

No-longer-unused image
A heads-up to you: the next time you update the list of unused images you have added to your "Project Clean-Up" page, you may wish to remove "File:DR Tako Purple.gif" from it, as I noticed that it was on there this morning, so I finally added it to the page for Dangerous Seed's second stage after six years (as when User:Notmyhandle moved that game's character listing to the stage pages when I was going through the process of correcting some of the names in 2014, he must have missed it, and nobody saw until today). Namcorules (talk) 18:00, 26 December 2020 (UTC)


 * Removed it, but that page is free for all people to edit. If you remove some of them, feel free to take em off yourself :) Trig - 22:43, 26 December 2020 (UTC)


 * Thank you both.-- 08:08, 20 January 2021 (UTC)

User talk:Trig Jegman/Project Clean-Up/Low-Priority Wanted Pages‎‎
Hi Trig. That 1.6M byte page User talk:Trig Jegman/Project Clean-Up/Low-Priority Wanted Pages‎‎ is kind of bringing the server to it's knees. I can't even really open it to patrol the edits. I appreciate the effort your putting into the site. Please just try to break pages up a bit into smaller pieces if you can. Thanks!  Pro cyon  14:36, 2 June 2021 (UTC)
 * Yeeeeah that's become an issue. If I can ever actually get it to open I'll try to split it up. Trig - 14:59, 2 June 2021 (UTC)

Whitespace edits
Hi Trig. I noticed that a lot of your edits lately have just been taking two spaces "__" and reducing it to just one space "_". I was curious why this was one of your focuses? I routinely add two spaces between sentences. It's so unconscious, I'm doing it right now as I type to you. And I find that, in a fixed width font editor, it makes it very easy for your eyes to scan a paragraph and determine where new sentences start. So I was just curious as to the rationale. Thanks very much.  Pro cyon  01:53, 17 June 2021 (UTC)
 * Primarily since it is no longer grammatically acceptable to do so. Even services like Microsoft Word will be flagging this as an error. Moving to the much more common and correct single space helps to establish uniformity in the site's formatting, similar to standardizing the use of color over colour spellings or the oxford comma. Trig - 01:57, 17 June 2021 (UTC)
 * Colour and favourite are acceptable spellings, as long as they're consistent within the guide. Are you removing or adding oxford commas? -- Prod (talk) 00:05, 18 June 2021 (UTC)
 * Neither since it has not been an issue but if I see a lack of oxford commas they will indeed be added. Trig - 00:08, 18 June 2021 (UTC)

Super Mario Land sprites
While I have been a big fan and huge supporter of all the cleanup work that you've done around the site (and still am), I'm afraid I have to disagree with you about the SML sprites. It is true that we prize accuracy in all of the information that we provide to readers. However, when it comes to images, it is sufficient for them to be representative enough for readers to recognize them and instantly connect the visual for an enemy in question with the text that concerns their description and any strategies concerning them. We are not a sprite resource center. There are many other sites that do that far better than we do, and they are the appropriate destination for people seeking that content.

To claim that the SML sprites on Super Mario Land/Enemies don't actually come from the game is strictly a matter of interpretation. Do they correlate 1:1 with the data contained in the ROM? No. Are they accurate enough to where a reader looking at them can instantly recognize the enemy in question and make the connection between what they see on the site and what they've experienced in the game? Undeniably. We have long had a tradition on SW to present graphics in a clear way that makes them easy enough for players to recognize. Attempting to present them in their 1:1 presentation in the game either requires players to squint in order to make them out (GB sprites are smaller than emojis at this point), or they get upscaled and filtered to the point where they are extremely poor representations of what they originally were.

The method I employ in most cases is to take the 1:1 sprite, scale it to 200% with no filtering, and then scale it 200% once again with linear filtering, just to smooth out the edges a bit. This results in an image that is large enough for our readers to see and instantly understand which enemy we are referencing. That is the goal and the priority. Images are not useful to readers if they have to jump through hoops like zooming in just to make them out. People are viewing Strategy Wiki through devices that have substantially greater resolution than many of the games which they are reading about, originally presented with. For their benefit, we have to take that into account.  Pro cyon  15:08, 10 September 2021 (UTC)


 * Thank you for your input. I would have to disagree with parts of what you said, however. If the sprites used were relatively similar to what is found in the game, such as perhaps just being the wrong color, I would have not cared as much about the changes at play, however the sprites being used are absolutely not remotely similar to what would be found or expected in gameplay, and hence I couldn't feel good about leaving them as is. For many enemies it may have been acceptable but in many circumstances I feel like it was not representative of what would be encountered. Fortunately, there is now an acceptable solution to the issue with the class=pixelart to allow a drastically larger size for readability while still using authentic images to represent how enemies appear in the game. The previously used sprites do not bear resemblance to what appears in-game.


 * While [[File:SML Goombo Sprite.png]] is far too small for reading normally, and SML Goombo Sprite.png is too blurry, SML Goombo Sprite.png allows for a good upscaling and still understanding what is encountered. I think this a more appropriate solution. Trig - 18:03, 10 September 2021 (UTC)
 * I genuinely don't understand your position. How is [[File:SML Enemy Chibibo.gif]] so drastically dissimilar from SML Goombo Sprite.png that you can honestly make the claim that the first is "absolutely not remotely similar to what would be found or expected in gameplay"?  They are literally the same arrangement of pixels.  The only difference is the palette being used to represent them.  If that is the basis on which your entire argument is based, I'll remind that the Game Boy contained no actual palette data.  One could just as easily argue that your presentation of the Goombo is wrong because on the Game Boy he or she used, they look green and not black.


 * If you want to have an honest good-faith debate with me, avoid hyperbole. Because on it's face, the assertion that the original sprites are "absolutely not remotely similar to what would be found or expected in gameplay" is absurd.  If you instead made the claim that they are presented with a palette that is less accurate to what one might expect, I might actually concede that you have a point, and agree to work with you on a compromise.  But taking an almost religious stance about the matter will win you no points with me.   Pro  cyon  21:57, 10 September 2021 (UTC)


 * Very well. While the palette of the currently used sprites are entirely greyscale, in no instance through gameplay on the original GameBoy or The 3DS re-release do the sprites appear to use any palette form less than the darkest possible form. If I recall correctly, the GameBoy registers only four types of colors, for simplicity I would indicate as Black, Dark Gray, Light Gray, and White. While both versions contain these four-layered palatting, there is not a substantial difference in color from the black and dark gray used in the old sprite renditions and does not provide the same type of contrast as the newer versions. Furthermore, throughout the entire game, as far as I am able to tell there is not a single instance where this form of greyscale only palette is easily seen. All enemies, especially larger enemies like Yurarin Boo, King Totomesu, and Ganchan, will extensively stand out amongst their background due to the higher contrast. The same cannot be assumed of the old sprites with a less contrasted and brighter palette. Henceforth, since the old sprites would not be as easily recognizable when playing due to their extended contrast to the background of the gameplay, I do not find these sprites representative of what would be encountered. While in isolation they are somewhat visually similar, this is hindered by how they appear in contrast to the green or white backgrounds they would be found on in-game. Furthermore, because of the lack of contrast, certain enemies or details become drastically lost in the older sprites, especially for mostly black items. Batadon also does not appear to be colored correctly but I cannot be sure.


 * Sorry for the delayed response! My apartment complex had a small fire as soon as you messaged me, lmao. Trig - 22:36, 10 September 2021 (UTC)
 * It's taken me a while to get back to you because it takes a considerable amount of time to patrol the number of edits that you've been making to the site lately. I'm having a tough time keeping up with it.  I will never back a strict 100% insistence on 1:1 sprite renders for illustration purposes.  We've been running with enlarged/modified/enhanced sprites on the site for over a decade, and in truth, I think readers quite like them.  So I see no need to replace much of what we have with smaller instances for the sole sake of purity.  As long as  indicates that the pixelart class is working and rendering correctly across multiple platforms (I believe he mentioned that Firefox on Android still wasn't displaying properly), I am fine going that route with updated SML sprites.  I still don't think the black should be pure (0,0,0) black, but at this point there are a lot more important issues to deal with than to draw a line in the sand on this point and refuse to budge.   Pro  cyon  02:50, 13 September 2021 (UTC)

Image file sizes
Trig, a 13kb file isn't going to kill us. If it was over a meg, I'd be concerned, but going from 13kb to 5kb isn't actually saving us anything. Thanks to your update, we are now storing a total of 18kb since MediaWiki maintains the history of every upload, so if anything, our storage consumption went up, not down. Please don't inform users to monitor the size of their uploads. I'm happy someone is uploading images at all.  Pro cyon  20:55, 16 September 2021 (UTC)

Smart apostrophes
Why are we adding redirects for titles with apostrophes? The search function should be able to fuzzy match a smart apostrophe to a regular apostrophe. Are these needed?  Pro cyon  01:20, 22 September 2021 (UTC)
 * Update: I saw that portion of your clean up page (and heard from Prod). I guess it makes sense.  Not clear on why it makes such a big difference to Google, but Google does whatever it wants so... I guess it goes on.   Pro  cyon  01:30, 22 September 2021 (UTC)
 * Shockingly, the MediaWiki search function does not understand smart punctuation. Since a majority of mobile devices and apple products in general use smart punctuation--most people not even realizing it--and it needs to be manually changed off to use normal apostrophes, it becomes a difficult thing to manage. It's wacky. Trig - 02:12, 22 September 2021 (UTC)

Bomberman released in 1994
Yeah, they're basically the same root game, with a few difference here and there, but enough in common to be considered a single guide.  Pro cyon  21:12, 25 September 2021 (UTC)
 * Smells like a lot of stuff is to get moving then, at least for links. Trig - 22:00, 25 September 2021 (UTC)

Rollback
You can stop complaining about how long it's taken to resolve your request. I just granted you Rollback status. 🎉 😒  Pro cyon  03:43, 21 October 2021 (UTC)

Re: BSP
From what I recall of that guide, I took all the images myself. Arrow (talk) 05:38, 7 February 2022 (UTC)

Image sources
Most of the time when I would write up a guide for a game, I'd actively be playing that game in an emulator, and I'd take the appropriate screenshots as I was playing along. Like, "oh, hey, this would be a good for illustration purposes in the guide," and I'd capture the screen. So a huge ton of screenshots you find uploaded by me are original content. If I've taken them from other sites, it's so long now in the past, I don't remember the sources. Sometimes they were from Japanese GeoCities sites that I'd have to find on archive.org or something.  Pro cyon  01:41, 27 May 2022 (UTC)
 * Oh that, no I was just fixing a link that had moved from its original source. All of those are still normally being attributed to you! Sorry, should have clarified that change! Trig - 14:00, 27 May 2022 (UTC)

USA SNES scans
This may help you on your quest: https://archive.org/details/near-snes-scans-png

Click "show all" on the side and you can browse through them. -BrownDerby (talk) 03:50, 22 August 2022 (UTC)


 * If I could I would be happy dancing. Much thanks! This especially helps given that Cover Project appears to have shut down :( Trig - 03:51, 22 August 2022 (UTC)

Poke Pic Template
Yo, Trig.

For some reason, when I try to use the Poke Pic template for pictures of Generation VI Pokemon, it doesn't actually work, it just shows a red link. Could you fix this, please?