:rydian:

Rydian · Dec 8, 2010

Code:

:rydian:

plz

EpicJungle · Dec 8, 2010

Rydian · Dec 8, 2010

Crazzy1 said:
no

plzplz?

ShadowSoldier · Dec 8, 2010

Just admit it, you hate ACEKARD YOU SUPERCARD FANBOY!

EpicJungle · Dec 8, 2010

no

Jolan · Dec 8, 2010

Warrior522 · Dec 8, 2010

ineap09 · Dec 8, 2010

Crazzy1 said:
no

I literally opened all of those...I can't believe I actually did that... O_O

Warrior522 · Dec 8, 2010

ineap09 said:
Crazzy1 said:

no

Click to expand...

I literally opened all of those...I can't believe I actually did that... O_O

I cheated. I did, however, play fair with Shlongs...

mameks · Dec 8, 2010

Warrior522 said:
ineap09 said:

Crazzy1 said:

no

Click to expand...

I literally opened all of those...I can't believe I actually did that... O_O

Click to expand...

I cheated. I did, however, play fair with shlong's...

Fix'd
...now it looks even worse

Warrior522 · Dec 8, 2010

shlong said:
Warrior522 said:

ineap09 said:

Crazzy1 said:

no

Click to expand...

I literally opened all of those...I can't believe I actually did that... O_O

Click to expand...

I cheated. I did, however, play fair with shlong's...

Click to expand...

Fix'd
...now it looks even worse

SUCESS!!

RiderLeangle · Dec 8, 2010

You do know you can just quote the post and see what's inside right?..

Warrior522 · Dec 8, 2010

's what I did...

RiderLeangle · Dec 8, 2010

Stop cheating....

Rydian · Dec 9, 2010

plzplz

ShadowSoldier · Dec 9, 2010

I don't know why you want that: Figured you would pick:

Code:

rydianctrlc+v

You have two choices for carts that have proper support/updates.[*]Acekard 2i

Price: $16 from shoptemp.com
Rank: Mid-range card for people that want to play lots of games on a DSi/XL with some extra features.

[*]Supercard DSTwo

Price: $35 from shoptemp.com
Rank: Pretty much the ultimate card right now.

DS / DS Lite
The card will work on an original (fat) DS or a DS Lite.
DSi / DSi XL
The card will work on a DSi or DSi XL as well.
Game Updates
Firmware updates are what let cards play newer games, these are the life-blood of the card.
SDHC
SDHC refers to SD cards larger than 2GB (gigabytes). If there's no SDHC support, you can only use SD cards up to 2GB.
WiFi Update
The Acekard 2i can update it's cheats (and get minor bug fixes) over WiFi without having to connect to a computer.
Clean Mode
The DSTwo has special features to ignore AP in most games, letting you play them without having to wait for a firmware update first.
RTS
The Real-Time Save (Save State) function lets you save and reload your game progress at any moment you wish.
In-Game Guide
You can pull up text files and images in-game, in order to check a walkthrough or map you downloaded at any time during a game.
Slow Motion
The card lets you slow down the game speed as you wish.
In-Game Cheats
The card lets you create and modify cheats while the game is running.
Special Homebrew
The card has multiple pieces of special homebrew, such as it's own GBA and SNES emulators, as well as text/PDF reader and video player.
Battery Life
Unfortunately the DSTwo's extra CPU and RAM (which give it the special features) eat into the battery life a bit.

Rydian · Dec 9, 2010

I've got more than that.

Arm73 Says...

Personally , I am really mad at Nintendo for releasing the Game Boy Color.
In case you didn't know:<ul><li> 1 in 12 people have some sort of color deficiency. About 8% of men and 0.4% of women in the US.</li><li> 0.38% of women are deuteranomalous (around 95% of all color deficient women).</li><li> 0.005% of the population are totally colour blind.</li><li> 0.003% of the population have tritanopia.</li><li> Protanomaly occurs in about 1% of males.</li><li> Deuteranomaly occurs in about 5% of males. It's the most common color deficiency.</li><li> Protanopia occurs in about 1% of males.</li><li> Deuteranopia occurs in about 1% of males.</li></ul><div class='quotetop'>QUOTE</div><div class='quotemain'>Colour blindness is a condition, where the sufferer has diminished ability to perceive differences in colours. Colour blindness is almost never a complete absence of colour vision, where an individual is only able to see shades of grey. Red/green colour blindness is the most common form, attributing to 99 percent of the cases and it is most commonly an inherited condition. There is no treatment for colour blindness, nor is it usually the cause of any significant disability. However it can be frustrating to individuals affected by it. About 8 percent of males have some level of colour blindness and for female the corresponding percentage is 0.4. Colour blindness is diagnosed with the Ishihara colour test, which consists of a series of pictures of coloured spots. The test is most often used to diagnose red/green colour deficiencies. A figure of one or more Arabic digits is embedded in the picture as a number of spots in a slightly different colour and can bee seen with a normal colour vision, but not with a colour defect.</div>
The whole problem started in the 50's when movies began to be in color.
I mean how disrespectful is our society toward color blind people ?
Why does technology have to evolve all the time and bring advanced and more affordable electronics in our lives !
After all, 1 in 12 people have some sort of color deficiency, what did Nintendo do about them so far ! It's disgusting !
Oh yeah , I forgot, color blind people can't recognize colors in real life either, it doesn't make any difference........
Oh , yeah, people with bad vision in on eye have trouble with depth perception in real life as well.....but wait, just like you can turn off the colors on your fancy TV, it's been reported ( but not officially confirmed ) the those new 3D screens will have an option to be switched to 2D anytime.

AKAIO's Anti-Anti-Piracy (AAP) is NOT the same thing as the DSTwo's "clean mode".

DSTwo has Clean Mode. This enables new games at the cost of soft-reset and cheats and in-game menus.
AKAIO has AAP. This is just a new type of AP fixing, it will NOT work on all games, it's currently a little buggy, and it still allows soft-reset and cheats.

(Normmatt): Its an attempt at software emulating reads below 8000h which is used to detect flashcarts.
[...]
It will solve the standard read below 8000h checks that are coming out recently

The AP it bypasses is the new "generic AP we'll stick on games" that Nintendo came up with, that's why it's working on new titles. It's not something that can be done on "weaker" carts, it was mentioned the R4 is not capable of it properly, that's why Wood doesn't have that option and is patching the individual games as they come out.

The DSTwo's Clean Mode makes more games play because it's an all-around method, whereas AKAIO's AAP is focused on one specific type of AP, however it's focus is the AP that new games RIGHT NOW are coming out with, which is why it's playing the same new games as the DSTwo.

It can currently break single-cart download-play, that's why it's optional (so you can turn it off in order to use that feature), future AKAIO versions will not have the AAP option on the screen once it's fixed up properly.

Clean Mode (DSTwo) and AAP (AKAIO/Acekard) are not like Coke and Pepsi. They're like Coke and Iced Tea. They are not the same thing. I'm not saying "they're not the same" for some stupid pedantic political shit, I'm saying they're not the same thing because they're really not the same thing, outside of the fact that both are meant to allow new games to run.

I'm an ass when it comes to tech stuff.

And there's a reason.

IT'S ACTUALLY IMPORTANT.

Video games I'm chill about, because they don't really matter.
Computers, however... paypal accounts, ebay accounts, financing information, personal conversations, they're full of (and used for) all sorts of information and even people's jobs, shit you do NOT fuck with.

If somebody loses a life in New Super Mario Brothers Wii because a guy told him to take the wrong door in a ghost house... oops. Oh well.
If a guy loses his $56,000 savings because the pirated and modified OS he was using was keylogging him... that is not an "oops, oh well" situation.

I present to you: "DSi Encryption Put In Perspective", also known as "I Love Crushing People's Dreams".

The DSi uses 128-bit encryption (IIRC).
How do you break it? You find the correct encryption key.

How many encryption keys are there? 2 (binary, a bit) to the 128th power (number of bits), divided by 8 (8 bits in a byte).
That's so many that the calculator that comes with windows (at least XP) can't even display the number without reverting to scientific notation.

128-bits is...
340,282,366,920,938,463,463,374,607,431,768,211,456 possible values in binary.
However, Since there's 8 bits in a byte, you divide 128 by 8 and get 16. That's 16 bytes, 16 characters.
That's 18,446,744,073,709,552,000 possible values, ranging from 0x0000000000000000 to 0xFFFFFFFFFFFFFFFF. Eighteen quintillion possible keys.
The actual number is a bit less less since a key will be a certain number of digits and be designed to not have repeating segments, but this puts it in perspective.

Let's say that you have a computer program which can try 50,000 unique keys a second.
That's 3,000,000 keys a minute.
180,000,000 keys in an hour.
4,320,000,000 keys a day.
1,576,800,000,000 keys in one year.

It would take 11,698,848 years to try all the keys at that speed.

So wait, how do they break other systems? If you can get a direct copy of the encrypted data and compare it to a copy of the unencrypted data (as well as view the data as it's transmitted around the DSi's internals), that goes a long way towards figuring out the key without having to try all possible combinations. You'll be able to find the key without all the guessing! The problem is you'd need to take a DSi apart and fuck with it's insides while it's on to try to get a copy of the data while it's unencrypted (since the DSi will unencrypt what it needs on the fly in order to use it), and usually when you're done with that the DSi's pretty broken and in no shape to game, or even to be experimented on a second time...
<img src="http://farm4.static.flickr.com/3441/3869187499_da1665050d.jpg" border="0" class="linked-image" />
<a href="http://www.flickr.com/photos/micahdowty/sets/72157621023570420/" target="_blank">http://www.flickr.com/photos/micahdowty/se...57621023570420/</a>

This process can be hampered by the internal design of the system, so you may need to take apart many systems before you even figure out how to read some of the data, let alone get a full copy of it, and last I checked DSi's don't cost $5...

A way to prove you have it early without any risk would be to generate an MD5 hash of the unpatched copy, and then when the actual dump is released and widespread we can generate it's MD5, and if they match it's the same thing and you'll have proved you had it early (since the dump posted on popular rom sites will also be the unpatched one).

Download <a href="http://www.softpedia.com/progDownload/Dimsoft-MD5-Hasher-Download-141177.html" target="_blank">this</a> free program (it's a very small download and needs no install), run it, click the button with the ellipses (three periods), select the rom, and then wait a few minutes as it reads it all and does the math to generate a hash. When it's done copy the hash (which will be a long string like 470b32dbedce3a129e90b30f25e29507) and post it here.

If, when the actual dump is released, it has the same hash, then it's the exact same rom file and you'll be proven right. If it's a mismatch, however, then what you have is a fake (or bad dump), one way or another.

This costs you no money, takes barely any time, and has no personal info associated with it, so give it a go if you really do have it.

<div class='quotetop'>QUOTE(FAST6191 @ Nov 26 2010, 10:25 AM) <a href="index.php?act=findpost&pid=3289684"><{POST_SNAPBACK}></a></div><div class='quotemain'>AP and you

For whatever reason developers of the newer DS games include methods to try and detect if their code is running on a flash cart or the real cart. Cart makers and other people will usually try to bypass this but if they are not quick enough for you then you could always try your hand at it yourself.
Before going on this is an advanced technique and you will find yourself getting into assembly level coding, while it is not necessarily advised you can skate by with a level of knowledge on/appreciation for how DS roms work (covered in this thread), how to make cheats ( <a href="http://cheats.gbatemp.net/forum/general-hacking-discussion/" target="_blank">http://cheats.gbatemp.net/forum/general-hacking-discussion/</a> ) and how to hack roms ( <a href="http://gbatemp.net/t73394-gbatemp-rom-hacking-documentation-project-wip" target="_blank">http://gbatemp.net/t73394-gbatemp-rom-hack...ion-project-wip</a> ).

What a game does when it detects a flash cart varies- saves can get wiped, a "thanks for trying the demo" screen can be loaded, the game can lock up (either right at the start or further into the game), the game can move in circles (unbeatable level/boss or something) or something more subtle (phantasy star changed drop rates of certain items) so while you can see a working game do not assume all is well. This the author leaves to you to determine although usually a mix of user observations, your own observations and machine level checks (it locks at level 2 but you check for similar instructions/sections and see that it would also lock at level 7) are what is called for. You should always assume developers/AP makers are creative people in this regard when hacking a rom.
This guide will not cover the more advanced things like making downloadable content work and fixing it for a given cart (saves and the like) but that should not bother too many people.

There have been many different ways to try and detect if a game is running on a flash cart or not [this is where I am going to fall down a bit as I have not paid as much attention as I might like] but in general to do things like have saving, cheats and soft reset the developers will alter the game code (this is also part of the reason why clean mode/stealth mode can often run a game that has yet to be patched) and these alterations can be detected.
The simplest way to check if a change has been made is to do a checksum of the binary (or section thereof) in memory,.
A simple checksum might be to add the values of the binary up and a change should change this result- change detected. Some of the more modern games can have well over 100 of these checks (occasionally even to the point where it induces a bit of a slowdown in the game even). While checksums are a method there are other options (a nice example relayed a few weeks back concerns Houkago Shounen (a Japanese game from early 2008) that timed how long it took for a save to occur vs the same thing on an original.) while others make use of a peculiarity with DS flash carts reading below 8000 hex in the memory (indeed if you disassemble a game and see a read to below 8000h this is probably what is happening also the debug output of an emulator will often have this) compared to what happens on an original cart.

The DS can receive code (and thus perform checks) via 4 methods
ARM9 binary (this is the arm9.bin you will see if you pull a rom apart)
ARM7 binary (this is the arm7.bin you will see if you pull a rom apart)
ARM9 overlay (usually stashed in the overlay directory)
ARM7 overlay (does not usually exist beyond 0k files).

In commercial DS roms the ARM7 is usually very similar from game to game (to the point where you can swap them without issue for many games which is a quite a feat for a system like the DS) and ARM7 overlays are quite rare. As the ARM7 controls saving for many games this gave birth to the ARM7 swap fix but as the last few paragraphs should have shown just trying an ARM7 fix is probably not going to solve your problem.

The ARM9 is what does the bulk of the work in commercial DS roms as far as calculating damage from an enemy, fiddling with text, shuffling things in memory and the like. While the translation process will usually involve editing the game data the binary is almost always changed as well (indeed it is not unknown for the text to be in the binary along the with the game code but from a more pragmatic stance the Japanese game might use a fixed width font while the US release will want a variable width one) and this is why swapping it with the already patched Japanese release or trying to use is also a bad/pointless idea. Most hacker translations will avoid changing the binary to the point of changing locations as it means everything after it is now wrong (why having a file system vs something like the GBA or SNES with everything piled into one big file is awesome for hackers) but as the commercial translations will have source code all bets are off here as far as assuming things will stay the same between regions (of course there are several examples of things remaining near enough the same but never assume it will).

Overlays are blank patches of memory that a game can add a section of code to (overlay if you will) for temporary use for whatever reason and then overwrite it with another one later but still keeping the core of the game loaded- a crude somewhat outdated method of expanding the capabilities on limited memory but about the only one that is available to programmers of commercial DS games (they do not have a nice ?SD card to play with and pull data from/write data to). Checks can be in here as well (quite troublesome too as they may not be loaded for several hours after starting a new game).

In addition to the two processors the DS versions of the ARM7 and 9 have an additional instruction set/mode called THUMB ( <a href="http://nocash.emubase.de/gbatek.htm#thumbinstructionset" target="_blank">http://nocash.emubase.de/gbatek.htm#thumbinstructionset</a> ) which broadly speaking is a 16 bit instruction set that can run on a 32 bit system (it gets a bit more complex that than but it makes for smaller code and helps if you are limited in bus size if used correctly). Developers will occasionally hide checksums in THUMB code- your disassembler is a dumb tool and will blindly disassemble everything you feed it in the manner you tell it (with the exception of some of the more automated functions of emulators) so in your haste you might skip over one buried in THUMB code.

It should also be noted that the binaries as found in a DS rom might be compressed (or worse sections of them might be compressed). You can usually snatch these from the ram viewer of an emulator

So you have read all this, understood it, ploughed into your rom and found an instruction you now know causes your headaches. Chances are if you have this is redundant but ultimately one thing happens at the end of a check and that is a branch depending on the outcome of the check, if you are feeling nice (or better a game runs slow courtesy of checks- always nice to know you not only made a rom work but work better) you can catch it before it ever checks but assuming you did not then the main course of action is to change the branch from well branching to a straight jump to the "good" outcome.

Cheat bypasses- not so viable for the many hundreds of checks option but still possible for some games. Here rather than targeting the rom image you target the binary in memory with a cheat (the payload of the cheat being the opcode(s) to bypass the AP). Most of the same ideas regarding locations apply so simply trying Japanese cheats on a US release is not likely to work either (although it may well just be a shift so if you redirect some of the locations then you can fix the game sometimes).

Tools of the trade vary from hacker to hacker but in general you will want
A method of pulling DS roms apart- ndstool (frontend in DSbuff and DSlazy) will do but something like NDSTS (which also includes some choice info on the binaries/header as well) is well worth having around <a href="http://www.no-intro.org/tools.htm" target="_blank">http://www.no-intro.org/tools.htm</a> . Your standard rom hacking tools for this sort of thing are all that is really needed.

A disassembler- even if it is only in the emulator the last thing you need to be messing with is raw machine code.
Several exist including
ndsdis2- the oldest one still in common circulation. Not favoured by some in the hacking community but works well enough most of the time.
<a href="http://hp.vector.co.jp/authors/VA018359/ndsdis/" target="_blank">http://hp.vector.co.jp/authors/VA018359/ndsdis/</a>
crystaltile2- while the actual tool is a great general purpose hacking tool it does feature a simple editor
<a href="http://gbatemp.net/t73394-gbatemp-rom-hacking-documentation-project-wip?view=findpost&p=2641950" target="_blank">http://gbatemp.net/t73394-gbatemp-rom-hack...t&p=2641950</a>
IDA pro- a commercial disassembler used by many top flight hackers of all systems. <a href="http://www.openrce.org/downloads/browse/IDA_Plugins" target="_blank">http://www.openrce.org/downloads/browse/IDA_Plugins</a> has plugins.

Both desmume and no$gba (developers version) feature a level of "live" disassembly which can be very useful. They are also the two chosen emulators for most ASM level hacking work.

An assembler can be useful but more often than not you can boil it down to a single instruction which you can inject/modify by hand in a rom ( <a href="http://nocash.emubase.de/gbatek.htm#thumbinstructionset" target="_blank">http://nocash.emubase.de/gbatek.htm#thumbinstructionset</a> has the encodings for the ARM and THUMB instructions- it can be as simple as changing one bit in the entire rom but the trick is knowing how to get to that point). Still <a href="http://crackerscrap.com/" target="_blank">http://crackerscrap.com/</a> has some documentation you might want to read and in the tools section there is ARM ASM kit (originally made for cheats but works very well for things like this). Devkitarm has an assembler though.

Hex editor- there are hundreds of these and most hackers will have several on standby.
XVI32: <a href="http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm" target="_blank">http://www.chmaas.handshake.de/delphi/free...xvi32/xvi32.htm</a>
<a href="http://mh-nexus.de/en/hxd/" target="_blank">http://mh-nexus.de/en/hxd/</a>
naturally crystaltile2 has one.
<a href="http://www.romhacking.net/" target="_blank">http://www.romhacking.net/</a> has many in the tools section.

On the commercial side of things
hex workshop: <a href="http://www.hexworkshop.com/" target="_blank">http://www.hexworkshop.com/</a>
winhex: <a href="http://www.x-ways.net/winhex/index-m.html" target="_blank">http://www.x-ways.net/winhex/index-m.html</a>

If you fancy a few examples of patching try reverse engineering patches (say some of the rudolph's patches).</div>

<div class='quotetop'>QUOTE(popius @ Mar 30 2010, 09:23 PM) <a href="index.php?act=findpost&pid=2716936"><{POST_SNAPBACK}></a></div><div class='quotemain'>I'm sort of confused. Why do some games like Pokemon have a version that is 128 mb and another that is like 45mb. is there a difference?</div>The actual game carts have set sizes.
16/32/64/128/256/512 megabytes.

If a game is 15 megabytes, it goes onto a 16 meg cart. It will be 15 megabytes of game space, and 1 megabyte of empty space.
If it's 17 megabytes, then it has to go onto a 32 meg cart. Then it'll be 17 megs of game space and 15 megs of empty space.
So on and so forth. A game goes into the smallest cart size it fits in, with the rest being empty space.

All the empty space "goes away" when it's compressed, so usually a ZIP or RAR of a game will be a lot smaller than the original, and it will return to full size when you take the ROM out.

All the empty space is left in because a ROM is a direct copy of what's on the game cart, and it originally includes the empty space.

Some people "trim" their ROMs, removing all the empty space from the ROMs themselves. You can use a tool such as TinyTrimmer or TokyoTrim to trim your ROMs. This can save you a lot of space, but can sometimes break games, so not everybody does it.

If you want newer games to run, here's what you should try, in order.<ol type='1'><li>Latest official firmware.
Go to the site printed on your cart, download and set up the latest firmware, see if that fixes it. If there's no site printed or the site is down, <a href="http://www.linfoxdomain.com/nintendo/ds/" target="_blank">this</a> is a good resource for finding firmwares.

</li><li>AP-bypassing options.
Some carts have a setting or mode that will disable AP in games (to get them all running), but it may also disable extra features such as cheating and soft-reset, so these options tend to be turned off by default.

</li><li>A clean ROM.
If the ROM you're using has been modified in some way there's a chance it might not work on certain carts. In addition sometimes when transferring ROMs between carts small amounts of damage to the data can occur, so while the ROM may appear to be fine, it's actually been modified on accident and may not run.

Download and run <a href="http://tinyurl.com/lavrko" target="_blank">this program</a>, then go to Update -> DSFCC. This should update you to the most recent version. After that, browse around the folders in the upper-left to find where your ROMs are, when you click the folder the filenames should show up below the folder area. Select the ROM(s) you want to check, then click the health/heart button below the list, that will check to see if it's clean or not. Beware, trimmed ROMs will always show as having been modified! While trimming a ROM is generally regarded as safe, there's always the possibility of something going wrong.

If you find that the ROM you're having trouble with doesn't match the known clean ROM, then you'll want to redownload it (preferably from a site other than the one you used originally as their copy may be bad/damaged in the first place).

</li><li>Format your MicroSD card.
If the filesystem on your MicroSD card is damaged it can cause all sorts of trouble with running games. First copy everything off of your MicroSD, then run <a href="http://panasonic.jp/support/global/cs/sd/download/sd_formatter20.html" target="_blank">this program</a> to format it properly. After that copy everything back, and see if the game runs properly.

</li><li>YSmenu or other alternate firmware.
If there's no official support you can try an alternate firmware. If you have an original R4 or clone of the original (hardware-wise, not neccessarily name-wise) you can try <a href="http://filetrip.net/g25123666-Wood-R4.html" target="_blank">Wood R4</a>, which updates for new games often. If you have something else you'll have to see if you can run <a href="http://gbatemp.net/t267899-list-cards-which-can-use-ysmenu-dstt" target="_blank">YSmenu</a>, it's got <a href="http://gbatemp.net/t267243-retrogamefan-updates-releases" target="_blank">updates to the data files</a> to run new games.

</li><li>Game patches.
If there's no way to run better firmware on your cart, you'll have to hunt out patches for the games and apply them to your ROM. While this used to be very common, it's increasingly rare for patches to be made because there's multiple carts that can run new games without patches now, and multiple alternate firmwares for other carts that add support for new games. Rudolph makes and updates a <a href="http://gbatemp.net/t217811-rudolph-s-universal-child-s-play-patch" target="_blank">ROM patcher</a> that will automatically patch many games, but this doesn't support everything. For individual games that patcher doesn't support, you'll need to hunt out the patches yourself via google.

</li><li>A new cart.
If you can't run any decent firmware and there's no patches for the games you want to play, your cart's a piece of shit and you should buy a decent one, to put it bluntly. While many sites may tout R4 clones as amazing stuff and charge $65 for them, in reality even the best flash cart is only about $40, and mainstream ones with less features (that can still play all the latest games) can be had for $25 or less.</li></ol>

<div class='quotetop'>QUOTE(Rydian @ Mar 23 2010, 02:34 AM) <a href="index.php?act=findpost&pid=2694419"><{POST_SNAPBACK}></a></div><div class='quotemain'>Here's my take on what's most likely happening in most of these vanishing patch scenarios.
What they think is in red, what's they post is in green, and the amount of actual patch progress is in blue.

Oh it can't be that hard to make a patch, I think I'll try!
"I'm working on a patch!"
0%

I have no clue where to start, I need advice!
"Still working on the patch with my team!"
0%

Okay, I figured out when and where the freezes happened...
"I found the problem and will be applying the fix shortly!"
0%

Wait, how do I look at a ROM's code?
"Ran into some technical difficulties, no worry, it'll be out soon!"
0%

If only I could figure out how to convert this ROM hex into english...
"Debugging / Final testing!"
0%

Wait, you mean I have to actually learn how to program? Fuck that!
~
0%</div>

I also have two legal ones, but I really need to clean those up and trim them down to just the required parts.

narutofan777 · Dec 9, 2010

i'm 12 years old and what is this?

monkat · Dec 9, 2010

i'm 19 years old and i still dont know what is this?

ProtoKun7 · Dec 9, 2010

Why the hell didn't I think of some useful copypasta? I've just typed all the time.

:rydian:

Resident Furvert™

stop browbeating me can't you see i'm sexy

Resident Furvert™

Well-Known Member

stop browbeating me can't you see i'm sexy

Unlimited Bear Works

"In all things, balance."

Well-Known Member

"In all things, balance."

in memoriam of gravitas

"In all things, balance."

Well-Known Member

"In all things, balance."

Well-Known Member

Resident Furvert™

Well-Known Member

Resident Furvert™

Well-Known Member

I'd like to see you TRY to ban me. (Should I try?.

GBAtemp Time Lord Regenerations: 4

Similar threads

Popular threads in this forum