Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Parzival

Pages: [1] 2 3 ... 45
1
General Discussion / Re: The Member's Guide to Topiclessness
« on: September 12, 2019, 09:20:59 pm »
when someone tries to wrap their MIDI in 3 layers of crypto to distribute it without allowing access but they used ZipCrypto on a headered file format where only 4 of 14 header bytes can change
2
A Pokédex entry is a relatively complicated object. A valid Pokédex entry looks like this:
Code: [Select]
; string: species name
; height in feet, inches
; weight in pounds
; text entry

RhydonDexEntry:
db "DRILL@"
db 6,3
dw 2650
TX_FAR _RhydonDexEntry
db "@"
Here "DRILL" means Rhydon is the Drill Pokémon. This string is the first to be printed to the screen, and with good reason: The game need to know where that string ends in order to find all the other data.

Consider a Pokédex entry at $AA00. Contrary to what I initially believed, the SRAM is actually unlocked during the battle. It is locked when the game finished loading the player's back sprite, but is then unlocked when the game loaded the back sprite of my first Pokémon and never locked again. I can't tell if this is intentional.

Well, on my save file for testing, SRA0:AA00 is a bunch of 0xFF anyway. (Probably because I have cleared the save file some time in the past.) Which is an awfully long string of "9". More "9"s than healthy for the game. For example, at some point it overwrites wOptions and then wLetterPrintingDelayFlags, which causes the game to wait 15 frames between characters. And that's terrible.

For some reason, beginning at SRA0:BBB7, my save data is no longer 0xFF. It begins with some bytes I don't understand ("E4 35 70 01 67 3E 8C 00 00 39 C3 BB 94 20 20 D3 01 8C 8C 8C 20 D3 38"), and then (starting at $BBCE) becomes "00 39 00 39 00 39 ...". I guess old crashes don't die that easily.

Anyway, the game mercy kills the PlaceString subroutine when it sees 0x00 at $BBBE. But it puts the pointer de at $19F3, which is... here. Starting from $19F4, the bytes "17 96 66 22" are interpreted as the height and weight data (23'150"/880.6 lb; the 150 displayed as " 0" when forced to be printed in two digits). Right after there happens to be a 0x50 terminator. Everything is fine!

Except that wJoyIgnore has also been overwritten to 0xFF, so I softlock. Oh well. At least I can soft reset.



It should be clear by now why this Pokédex entry behaves differently depending on the save file, especially after looking at glitch Pokémon sprites (which are known to trash SRAM Bank 0, also known as HOF data). Anyway... why don't you set a breakpoint at 10:435E and see for yourself?

Well that explains why I get random everything; I have never cleared the file. Also I haven’t got a clue how to set a breakpoint...
Breakpoints are only possible with a debugger. Like BGB's.
3
O-Ok sorry... :'(

Don't worry about it buddy ^^

Hmm I think SRAM can be locked at points; I wonder is there a point where all the data is read as FF FF FF (...) because it is locked? So 999 category max height/weight etc. Or is the region always unlocked for when the Pokédex entry is brought up.


I’m not sure.. There may be some points where it is locked and only (or mostly) reads FF FF FF (999...) when the game spams 9999 at the bottom. But it seems it’s unlocked, as the species description (normal example would be New Species for Mew) isn’t just mostly 9's, it varies from a few letters to complete garbage.
Sounds like VRAM, however. Might be pulling from multiple places...
4
Well I’m not sure, the Pokédex data is from VRAM AA00.
I’m using an android emulator (forgot the name) which means results could differ...
AA00 is SRAM...
5
RIP the game in that case. Here is what I’ve got so far:
52'71"/1946.8 lb: Some glitchy sounds, does end relatively quickly.
8'18"/1090.1 lb: Crazy mix of Pokémon cries and moves. Sounds stopped after awhile, assuming a 00 39 pattern crash, where it was stuck on the Pokédex with no sounds or buttons working.. (No hex viewer so can't know for sure)
47'74"/1180.6 lb: Brief chaotic glitch combo of music and sounds, large amounts of garbage text appeared at the bottom of the screen (glitch tiles and letters/numbers) with a 48 error, but it ended after.
1'3"/177.3 lb: Mostly spammed a sound effect like that of Defense Curl from gen 2. Gave up after about 2 minutes when nothing was happening.
34'71"/4437.0 lb: Quick burst of glitchy sounds, gave a 48 error and ended.
80'3"/6099.0 lb: We all know this one. Mess of sounds that repeat twice and eventually locks up.
You'd know if it was a 0039 crash (aka an RST 38h crash) as VRAM would get trashed. Also, it'd be great if we could figure out where it's pulling the data from.

Also, use BGB. It has a builtin fully-featured debugger.
6
>screen blanks with bar lines
That's called a RST 38h crash, as it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038. Then, at 0038, it jumps to 0038.

You get the point. Every time this happens, it writes 2 bytes to WRAM. Oh wait, we're in VRAM now. ...now we're in SRAM. ...now we're just writing to ROM. great. Oh look, we've wrapped around! Repeat ad infinitum.
7
Introductions / Re: don't entirely know what to call this thread
« on: September 05, 2019, 10:32:25 pm »
Any reason you're not just changing your username? Do you still have the email address for your old account?

Also, if I recall correctly, you did a lot. Empirical glitching (the Red/Green GlitchDex, possibly?), but still, a lot.

You're always welcome anyhow, whether you'd prefer this account or your old one. :)
yeah, i still have the old Discord server where him and a couple others collaborated on the Green GD.
8
Forum Discussion / Re: Uploading problems.
« on: September 05, 2019, 10:30:46 pm »
According to the Admin CP, the individual file limit is indeed 8000 KB (in addition to the per-post limit). The only thing that stood out as odd was that the size limit for the attachments folder (where all attachments in the history of this forum, or at least the ones still accessible) was set to 2147483647 KB instead of having no limit, but we're obviously nowhere close to that. There is clearly a bug, though, if this happened the way you said.
it's been pretty busted for a while now, i remember some similar threads well.
9
Forum Discussion / Re: Uploading problems.
« on: September 05, 2019, 06:56:07 pm »
Damn... If has it been 2MB for awhile? Or is it a recent problem...? :-\
No real consensus on how big, 2MB is my observation but it's been busted for a while.
10
Forum Discussion / Re: Uploading problems.
« on: September 05, 2019, 06:09:17 pm »
the upload limit's more like 2MB iirc, plus it's pretty fuckin' busted.
11
General Discussion / Re: The Glitchy Thread of Topiclessness (#3)
« on: September 04, 2019, 08:37:38 pm »
did they really just

release Team Rocket fighter skins

then IMMEDIATELY fucking steamroll it with FUCKING SANS
12
General Discussion / Re: The Glitchy Thread of Topiclessness (#3)
« on: September 04, 2019, 06:26:04 pm »
Generated and published a PGP key for myself.

However:

GPG's bad at it...?

I set it to expire in a year, and it wasn't detected as such on any keyserver, some keyservers didn't see an email address embedded in it, and it ended up being 3Kbit and not 4Kbit like I asked it to generate.
13
I also think having a dashboard with colapsable folders sounds like a very nice idea, it would be good so a person has a good concept which category a page is part of and what other pages are on the same level.
Can you elaborate on what you mean by a "dashboard"? Do you mean just like what is going on with the "major glitches" template (go to a page using that template to see it in action)? That could be nice if it is used on every page, but as of now, I think it may have too low a visibility.

(Honestly speaking, the "major glitches" template is currently a little of a mess, with some pages it links to (in the "'Core' glitch" column) not linking to it, but that's mainly because of an inherent problem with the category "major glitch": While many ways of categorizing a glitch is subjective, the definition of "major glitch" turns the subjectivity up to eleven. It can even be self-fulfilling because of the "well-known" clause.)

Actually, I have considered adding (multiple) navigation bars to every page, just like what is going on at the bottom of any random TVTropes page. Of course the order would have to be arbitrary (e.g. alphabetical order), but the point is just to give the reader a "tour" through pages in the same category. It would be more eye-catching than the collapsed "major glitches" template because it would have two page names to pique interest.

Collapsible folders sound good!

I haven't read all of this properly yet sorry, but regarding the scope of the wiki, I relate with that how we cover not just glitches, but also data, terms, unused content, recently a little speedrunning content. If it was focused on just glitches/data with terms etc. in like an appendix page then I suppose that would organise the wiki better as most pages would be examples of glitches with a method or the database pages. At the same time (though no one has said it), it feels a shame to let them go, and it's a double-edged sword as you said.

The style has a lot of inconsistency yeah. A lot of it is my fault. Sometimes while perfection is overrated, it would be good to have a style convention not just for the Dex articles, so that most instances of hex: hex 0x $ etc. are kept under one notation.

I agree with cutting down on very similar pages and merging them (ItemDexES/RB:094 and ItemDex/RB:094), though otherwise disagree personally with "interesting" as it's subjective and there are various small but unique glitches (e.g. https://glitchcity.info/wiki/Ragon_Pok%C3%A9dex_entry ). However, these could be merged somewhere as well (like Bulbapedia's 'list of glitches in Generation I', we have list of natural glitches, and Ragon could be under a list in a different article list for non-natural glitches (I'm unsure though, I don't know how we would organise everything together?))  and we could set some criteria of which glitches get their own article) and we've had a pattern of keeping articles for very small glitches without any (known) additional uses (e.g. https://glitchcity.info/wiki/Stand_on_a_tree ), while Bulbapedia would just include them on a list of glitches page. However, some of Bulbapedia's list of glitches pages are quite long as well.


Actually, I suppose MediaWiki has multiple ways to separate "primary" content and "secondary" content, such as subpages and namespaces. I haven't studied those mechanisms in detail, but I think it's likely that there exists a good way to move the "secondary" contents out of the way without actually letting them go. (Although it might be necessary to let them fall behind for a while, when we first sort out the organization for our "Project Glitch").

I agree that "interesting" is very subjective. There is another criteria that is still subjective, but maybe less so: On a page level (i.e. not considering the navigation problem), do we lose anything by merging those pages? Or maybe in contrary, we gain something by presenting the contents together? I strongly believe that ItemDexES/RB:094 and ItemDex/RB:094 are the latter case (we gain something by emphasizing the fact that international versions are generally similar to each other, including in terms of memory layouts, etc.).

Kinda like the one at the bottom of this page, maybe?
14
I'd love to see TVT-style/AR-styke folders here, tbh.
15
Post any useful or cool glitch text you find here.

In Pokemon Yellow, glitch textbox 0x22 in the player's house causes a potentially useful buffer overflow. It prints as a textbox that wraps around the screen, so if you mentally divide the screen into thirds, it takes up the first and third thirds of the screen after a second it prints a bit of cool glitch text and after it's done you can close it. It corrupts your party to have more than 6 Pokemon (I don't know exactly how many), but it does not crash when opening the party menu and does not corrupt box data, so it might be a useful way to get more than 6 party pokemon without ACE or the SRAM glitch.
Hpw would you trigger it, without ACE, though?
(also number of party Pokemon is at D162 or so)
Pages: [1] 2 3 ... 45