Jump to content

Talk:Trapped at burgled house oversight: Difference between revisions

no edit summary
>Sherkel
No edit summary
>Sherkel
No edit summary
 
(One intermediate revision by one other user not shown)
Line 9:
:  
: This glitch is taken from Legendary Star Blob, and they got the report from someone called おくとろん. All credits should go to them. --[[User:Bbbbbbbbba|Bbbbbbbbba]] ([[User talk:Bbbbbbbbba|talk]]) 15:46, 23 February 2019 (-06)
::  
::While you're correct about the "boundary", I'm not sure it matters in the way you're implying it does. What in particular makes you say it should be such a big focus? The site's about everything past the boundary, regardless of how arguably close or beyond it a particular exploit or result might be.
::  
::Sure, there are a handful of glitches that require crossing that boundary before beginning. Take any variant of the LOL glitch or Text pointer manipulation, for instance. The issue is that when it comes to ''procedures'' that need to follow another, there are a lot fewer that have their own pages. ''Results'' such as GlitchDex entries are completely separate from this. We could have a huge category for natural glitches that includes most pages that have procedures outlined, or even group all sub-glitches of a given one on the same page...but as you said, it can be nebulous which is which. The first option was an organizational mess, and the same would go for the other. I suggested a possible separate category for non-natural glitches at one point; would you be in favor of that?
::  
::Not to worry, I understand what this is. The possibility the player has a full bag after trading Cut over isn't too much of a stretch.
::Thanks for the thoughtful response, anyhow! Editors like you are invaluable to the site. I'll add the attribution to Legendary Star Blob. [[User:Sherkel|Sherkel]] ([[User talk:Sherkel|talk]]) 21:23, 23 February 2019 (-06)
::  
::: To put it in other words, natural glitches are where the program actually goes wrong. Non-natural glitches are just ways to exploit an already inconsistent game state. If I want to fix all the glitches in a problem, I only need to go for the natural glitches. Same if I want to learn a lesson as a programmer. (Although to be frank, most Gen I glitches are stupid human errors from which there's no real lesson to learn.)
:::  
::: I'm not sure most pages with procedures would fall under natural glitches. It seems to me that a significant portion of those procedures begin with "get a 8F", "have 255 Pokémon in your party", or something like that. Maybe my observation is biased? The "Generation I glitches" category had 314 pages, compared to the 104 on the [[list of natural glitches in Generation I]], but as you said, some of those 314 pages are just results, others are terminologies or redirection pages, and maybe some of them are natural glitches documented after you stopped to maintain the list. Still, the list definitely saved me a lot of time in finding glitches that interest me, and I would hate to see it disappear/go out of date. --[[User:Bbbbbbbbba|Bbbbbbbbba]] ([[User talk:Bbbbbbbbba|talk]]) 02:30, 24 February 2019 (-06)
::::  
:::: Again, though, why is it important to know "where the program actually goes wrong"? The focus here was never reporting bugs, whether they're in the games' code or in their logic; instead, it's simply been about warping the reality of these games without external devices in whatever ways possible, some useful, some not.
::::  
:::: As for most not being natural glitches, maybe I'm biased too. Begs the question of what defines a "majority" here, I guess...I noticed when clearing the category that there were many that should have been there but were missing, on account of most of the wiki's work being done on a single editor's part. I can kind of see why natural glitches could be a particular area of interest...but to me, they're ultimately defined just by having less steps. I'm gonna start a forum thread about this so more people can weigh in. [[User:Sherkel|Sherkel]] ([[User talk:Sherkel|talk]]) 11:50, 24 February 2019 (-06)
Anonymous user
Cookies help us deliver our services. By using our services, you agree to our use of cookies.