Register - Login
Views: 99388705
Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies
04-24-22 07:28:43 AM
Jul - The Cutting Room Floor - Pokemon FireRed/LeafGreen pre-release differences and leftovers New poll - New thread - New reply
Next newer thread | Next older thread
Keitaro

Fire Snake
LOVELY ARRANGEMENT. VOLCANO BAKEMEAT
Level: 70


Posts: 840/1191
EXP: 2898912
For next: 116899

Since: 09-09-08

From: California

Since last post: 4.1 years
Last activity: 3.8 years

Posted on 05-30-11 11:42:52 PM (last edited by Keitaro at 05-30-11 10:11 PM) Link | Quote
I've hacked this ROM extensively, and anyone else who has for more than two seconds probably knows about the "unused" overworld sprites. In fact, these sprites are more than certainly already documented in the wiki already. What it does NOT state, however, is that the legendary dog sprites were at one time in use! I have absolutely no proof of this data-wise, at least not in the English rom (have not checked the Japanese), but I remember distinctively having seen Japanese pre-release screenshots (of which I cannot find...any help?) depicting said sprites on the overworld, on an island much like the one you'd find Deoxys on. I know I'm not crazy, and those pictures have to be out there somewhere they may have even been magazine shots for all I know, this was of course years ago. Perhaps in even earlier, unshown builds, the Mew and Celebi were also used for one purpose or another.

Now as far as unused overworld sprites go, it could also be noted that several unedited Ruby/Sapphire overworld entities, including Ty the camera man among some of the more curious ones, can be found within the sprite data as well. Perhaps they were at one point used as placeholders (maybe the game originally used the R/S style) and after their characters were not used in the game were just left unupdated. I could rip them for those interested, though the pallets would be wrong as the two games use different pallets (I could of course show a comparison with the original pallets applied)

Now for some pre-release stuff I can actually prove there are some graphics used during development that are different from the final version.


The Charmander pictured in the left screenshot is modified from its Ruby and Sapphire sprite, but also matches the updated style used by FireRed/LeafGreen's final Charmander sprite (most notably, the flame) ... unfortunately I couldn't find a non-artifacted version of this I was however able to find one of that Bulbasaur's behind.


It is also different from its final version, appearing to be some sort of hybrid between its Ruby/Sapphire sprite (which was itself was recolored from/based on its Gold/Silver sprite) and the final version.

Another very curious thing is the fonts used. In the picture with the Charmander, the font used is different from its final Japanese font, but also vastly different from the one used in Ruby and Sapphire.


You will also notice that in the picture I posted above with Bulbasaur vs. Pikachu, the font used there appears to be the final one. This means that the font was either changed very early in development, or that Bulbasaur's back sprite was used in its "beta" form until much later in development. Finally, here is a comparison between beta, final, and Ruby/Sapphire sprites for Charmander and Bulbasaur.


Unfortunately, it is much harder than I was hoping for me to find early Japanese pre-release screens, which is why any proof I have of the dog bit is lost in the internet right now still, hopefully this will be interesting to some people and can help us shed light on other unused things these games may have held at one point.

edit: wow, looking through the wiki, it looks like there's a lot of stuff not covered (lol, the "unused snowflakes" is actually just the soot from Lavaridge's volcano and is that a hack? why in the world is Red recolored..well, blue?) I guess I'm just surprised because its stuff that was known to me through my own research for years now xD the main thing I'm shocked no one covered is the surfing sprites.

The way the surfing sprites work in all gen. 3 games is they have an animation of the character "jumping" on the the black surfing blob, then a sprite of them sitting on it, which is overlayed on to the blob itself once they "land". These unused sprites, however, are already attached to a Pokemon (looks like Lapras, ala Gold/Silver) ... curiously, they are stored directly before each character's respective sprite for jumping on to the surf-blob. Even more curious is that these are the ONLY unused sprites to not even have data in the the sprite table, meaning they are not and cannot be accessed by the game even by means of hacking. I'm not sure if there is code in the game that would otherwise use the sprites. Strange that they decided to scrap this idea and go with the generic sitting-on-blob pose.



another thing I guess could be of interest, is that the e-Reader features were taken out from the English versions of the game (did the European ones do this too?), though its leftovers still exist in the game due to...well, laziness, I guess. This is really just a regional difference, but those count too right? One largely noticeable result of this is the presence of nearly all (if not all) of Ruby and Sapphire's trainer sprites being present in the game's code. This is to ensure compatibility with e-Reader cards intended for Ruby and Sapphire games. Even more curiously is that FireRed/LeafGreen's trainer sprites were not included in Emerald's data (other than Red's and Leaf's of course)...did Emerald have e-Reader support? Did FRLG's e-Cards also just use Ruby/Sapphire graphics? These are two things I have not yet looked in to.
krutomisi
2480
Level: 94


Posts: 1503/2481
EXP: 8257173
For next: 99484

Since: 02-01-10


Since last post: 232 days
Last activity: 172 days

Posted on 05-31-11 03:13:50 AM Link | Quote


Originally posted by Keitaro
...did Emerald have e-Reader support?

I'm really not sure and I can check later buuut


I don't think Emerald could actually hook up and get cards from the e-reader

but I think there was a way to connect with a R/S game that had a card active
and the trainer would become battleable in the emerald game.

____________________



1503 / 55 / 483
Keitaro

Fire Snake
LOVELY ARRANGEMENT. VOLCANO BAKEMEAT
Level: 70


Posts: 842/1191
EXP: 2898912
For next: 116899

Since: 09-09-08

From: California

Since last post: 4.1 years
Last activity: 3.8 years

Posted on 05-31-11 04:10:13 AM (last edited by Keitaro at 05-31-11 05:06 AM) Link | Quote
Ah yeah...I seem to recall something like that. I want to say it has something to do with Trainer Hill but I could be dead wrong something else I want to look in to is the effect of transferring over a Pokemon with an e-Berry to FRLG or Emerald, as I'm almost certain the icon graphics for those do not exist (one does exist for their placeholder, the Enigma berry, however) ... it would probably just turn in to an Enigma berry with no effect like when transferring to Gen 5 but it would be interesting to see if the functionality is retained in some way...though I think perhaps I'm getting slightly out of the scope of the wiki as that's more an e-Reader thing than an unused feature per-sayyyy...

edit: yep, Japanese Emerald could use its own set of e-Reader cards to change which trainers were encountered at Trainer Hill (similar to how FRLG's card system would change the trainers encountered at Trainer Tower)

Interestingly enough, many (if not all? I haven't completely checked) of the trainers encountered in the FRLG Trainer's Tower are ones you would have only been able to encounter via e-card. That is to say, they hardcoded them in to the game as a way of not completely screwing us of that content. This explains why a trainer early on has a shiny Seaking, and why other trainers with shiny Pokemon also exist in this area. I have no idea if Emerald did anything similar (hardcoding in trainers otherwise only found through cards) as I haven't really investigated yet. This could also count as a region difference of sorts, as in the Japanese games the trainers at these locations are generally only determined by what cards you scan, iirc (as for what shows up when no cards are scanned, I don't know, perhaps we lost the use of "default" trainers in exchange for the content we otherwise couldn't get)
Keitaro

Fire Snake
LOVELY ARRANGEMENT. VOLCANO BAKEMEAT
Level: 70


Posts: 845/1191
EXP: 2898912
For next: 116899

Since: 09-09-08

From: California

Since last post: 4.1 years
Last activity: 3.8 years

Posted on 05-31-11 04:01:33 PM (last edited by Keitaro at 06-01-11 08:23 PM) Link | Quote
Another update regarding the e-Reader berries, I decided the Enigma Berry itself in fact counts as unused content in all five games. It is not legally obtainable in any of the Generation 3 games. In fact, the only way to obtain it in any of these games is through hacking or cheats. It has its own item icon in FireRed/LeafGreen as well as Emerald, and even has its own growth cycle, as well as unique berry blending and powder crushing properties! The purpose of this item was to serve as a place-holder for e-Reader exclusive berries. When an e-Reader berry card would be scanned in, it would automatically show up in the player's bag and take the place of the Enigma berry. Pokemon which held the Enigma berry in addition to any of the e-Berries were not able to be used in trades, nor were they allowed to interact with any of the Gamecube games (as far as trades go, I imagine battles would be the same way but have no means of testing this...they also can't be sent to Pokemon Box)

Curiously enough, the item IS obtainable in Generation IV if a Pokemon holding an e-Berry is transferred to the game. Certain event Darkrai were also distributed holding the item. It now has an effect of recovering 1/4 of your HP if hit by a super-effective move.

My theory about the trainer sprites in FRLG can be thrown out the window. Having checked the list of available Ruby/Sapphire battle e-Cards, there only exist cards for a select few trainer classes, while the sprites found in FRLG are easily close to ALL of Ruby and Sapphire's, including such trainers as the Aqua and Magma teams. Cards for such trainer classes never existed, so my theory that these trainers were to allow compatibility with R/S cards (they aren't even compatible, to my knowledge) ... unless they have something to do with the Mystery Gift battles on Seven Island in the Japanese version, something I have absolutely no way of confirming, its safe to say they are completely unused and there for no reason. There is next to no information about that damn battle house, though I haven't had a chance to check out any Japanese sources yet...regardless, they more than certainly serve zero purpose in the English version of the game, at any rate.
Next newer thread | Next older thread
Jul - The Cutting Room Floor - Pokemon FireRed/LeafGreen pre-release differences and leftovers New poll - New thread - New reply


Rusted Logic

Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

29 database queries, 2 query cache hits.
Query execution time:  0.639033 seconds
Script execution time:  0.010855 seconds
Total render time:  0.649888 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 2 column 301 - Warning: unescaped & or unknown entity "&page"
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 234 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 91 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 177 column 102 - Warning: unescaped & or unknown entity "&postid"
line 208 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 210 column 9 - Warning: missing <tr>
line 228 column 13 - Warning: missing <tr>
line 229 column 102 - Warning: unescaped & or unknown entity "&postid"
line 231 column 100 - Warning: missing </font> before <blockquote>
line 233 column 133 - Warning: inserting implicit <font>
line 233 column 133 - Warning: missing </font> before <hr>
line 233 column 197 - Warning: inserting implicit <font>
line 233 column 197 - Warning: missing </font> before <hr>
line 234 column 1 - Warning: inserting implicit <font>
line 243 column 597 - Warning: missing </font> before <center>
line 243 column 618 - Warning: inserting implicit <font>
line 243 column 642 - Warning: discarding unexpected </font>
line 246 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 248 column 9 - Warning: missing <tr>
line 266 column 13 - Warning: missing <tr>
line 267 column 102 - Warning: unescaped & or unknown entity "&postid"
line 276 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 278 column 9 - Warning: missing <tr>
line 296 column 13 - Warning: missing <tr>
line 297 column 102 - Warning: unescaped & or unknown entity "&postid"
line 306 column 17 - Warning: missing <tr>
line 306 column 17 - Warning: discarding unexpected <table>
line 309 column 35 - Warning: missing <tr>
line 309 column 50 - Warning: missing </font> before </td>
line 309 column 91 - Warning: missing </font> before </table>
line 311 column 35 - Warning: missing <tr>
line 311 column 50 - Warning: missing </font> before </td>
line 312 column 37 - Warning: unescaped & or unknown entity "&id"
line 311 column 234 - Warning: missing </font> before </table>
line 313 column 17 - Warning: discarding unexpected </textarea>
line 313 column 28 - Warning: discarding unexpected </form>
line 313 column 35 - Warning: discarding unexpected </embed>
line 313 column 43 - Warning: discarding unexpected </noembed>
line 313 column 53 - Warning: discarding unexpected </noscript>
line 313 column 64 - Warning: discarding unexpected </noembed>
line 313 column 74 - Warning: discarding unexpected </embed>
line 313 column 82 - Warning: discarding unexpected </table>
line 313 column 90 - Warning: discarding unexpected </table>
line 315 column 9 - Warning: missing </font> before <table>
line 327 column 25 - Warning: discarding unexpected </font>
line 336 column 57 - Warning: discarding unexpected </font>
line 314 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 160 column 11 - Warning: <img> lacks "alt" attribute
line 161 column 22 - Warning: <img> lacks "alt" attribute
line 161 column 63 - Warning: <img> lacks "alt" attribute
line 161 column 112 - Warning: <img> lacks "alt" attribute
line 161 column 162 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 179 column 778 - Warning: <img> proprietary attribute value "absmiddle"
line 179 column 778 - Warning: <img> lacks "alt" attribute
line 183 column 1682 - Warning: <img> proprietary attribute value "absmiddle"
line 183 column 1682 - Warning: <img> lacks "alt" attribute
line 185 column 1836 - Warning: <img> lacks "alt" attribute
line 186 column 2195 - Warning: <img> proprietary attribute value "absmiddle"
line 186 column 2195 - Warning: <img> lacks "alt" attribute
line 188 column 2312 - Warning: <img> lacks "alt" attribute
line 192 column 2817 - Warning: <img> lacks "alt" attribute
line 195 column 3317 - Warning: <img> lacks "alt" attribute
line 197 column 3592 - Warning: <img> proprietary attribute value "absmiddle"
line 197 column 3592 - Warning: <img> lacks "alt" attribute
line 199 column 3883 - Warning: <img> proprietary attribute value "absmiddle"
line 199 column 3883 - Warning: <img> lacks "alt" attribute
line 199 column 4020 - Warning: <img> proprietary attribute value "absmiddle"
line 199 column 4020 - Warning: <img> lacks "alt" attribute
line 203 column 5137 - Warning: <img> lacks "alt" attribute
line 212 column 16 - Warning: <img> proprietary attribute value "absmiddle"
line 212 column 16 - Warning: <img> lacks "alt" attribute
line 212 column 59 - Warning: <img> proprietary attribute value "absmiddle"
line 212 column 59 - Warning: <img> lacks "alt" attribute
line 212 column 102 - Warning: <img> proprietary attribute value "absmiddle"
line 212 column 102 - Warning: <img> lacks "alt" attribute
line 212 column 145 - Warning: <img> proprietary attribute value "absmiddle"
line 212 column 145 - Warning: <img> lacks "alt" attribute
line 212 column 188 - Warning: <img> proprietary attribute value "absmiddle"
line 212 column 188 - Warning: <img> lacks "alt" attribute
line 212 column 231 - Warning: <img> proprietary attribute value "absmiddle"
line 212 column 231 - Warning: <img> lacks "alt" attribute
line 212 column 274 - Warning: <img> proprietary attribute value "absmiddle"
line 212 column 274 - Warning: <img> lacks "alt" attribute
line 212 column 317 - Warning: <img> proprietary attribute value "absmiddle"
line 212 column 317 - Warning: <img> lacks "alt" attribute
line 212 column 360 - Warning: <img> proprietary attribute value "absmiddle"
line 212 column 360 - Warning: <img> lacks "alt" attribute
line 212 column 403 - Warning: <img> proprietary attribute value "absmiddle"
line 212 column 403 - Warning: <img> lacks "alt" attribute
line 213 column 22 - Warning: <img> lacks "alt" attribute
line 213 column 63 - Warning: <img> lacks "alt" attribute
line 213 column 112 - Warning: <img> lacks "alt" attribute
line 213 column 162 - Warning: <img> lacks "alt" attribute
line 214 column 11 - Warning: <img> lacks "alt" attribute
line 224 column 15 - Warning: <img> lacks "alt" attribute
line 250 column 11 - Warning: <img> lacks "alt" attribute
line 251 column 22 - Warning: <img> lacks "alt" attribute
line 251 column 63 - Warning: <img> lacks "alt" attribute
line 251 column 112 - Warning: <img> lacks "alt" attribute
line 251 column 162 - Warning: <img> lacks "alt" attribute
line 262 column 15 - Warning: <img> lacks "alt" attribute
line 269 column 203 - Warning: <img> proprietary attribute value "absmiddle"
line 269 column 203 - Warning: <img> lacks "alt" attribute
line 269 column 606 - Warning: <img> proprietary attribute value "absmiddle"
line 269 column 606 - Warning: <img> lacks "alt" attribute
line 280 column 11 - Warning: <img> lacks "alt" attribute
line 281 column 22 - Warning: <img> lacks "alt" attribute
line 281 column 63 - Warning: <img> lacks "alt" attribute
line 281 column 112 - Warning: <img> lacks "alt" attribute
line 281 column 162 - Warning: <img> lacks "alt" attribute
line 292 column 15 - Warning: <img> lacks "alt" attribute
line 312 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 312 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 312 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 321 column 25 - Warning: <img> lacks "alt" attribute
line 326 column 267 - Warning: <img> lacks "alt" attribute
line 149 column 50 - Warning: trimming empty <font>
line 243 column 597 - Warning: trimming empty <font>
line 306 column 17 - Warning: trimming empty <tr>
line 309 column 50 - Warning: trimming empty <font>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
line 229 column 27 - Warning: <nobr> is not approved by W3C
line 267 column 27 - Warning: <nobr> is not approved by W3C
line 297 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 150 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md