Talk:Seabreak Path

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to: navigation, search


If a cheater use's the walk through walls cheat, they can see a shaymin on the front of seabreak path which seems to connect to route 224, however if a player walks up to seabreak path and a sign on the top says 'Seabreak Path', the shaymin dissapears(LOL, cant spell). --[[Image:Ani492MS.gif Zakuro]] 09:52, 10 February 2008 (UTC)


Is 256 tiles the longest a route can be, or is there a longer route in another generation? TTEchidna 20:19, 12 September 2008 (UTC)

It's Already On The Map

It says that when you have Oak's Letter and express your thanks at the stone, Seabreak Path 'appears';but, it's already there it just extends (and connects) towards Route 224 by about 8-14 tiles. With the walkthrough code on you could walk out a little bit and see Seabreak Path. Also if you use the code to walk out a bit, you will see a little Shaymin sprite there (on the R224 end), it probs not there in Pt though (the sprite). --Sivart345 00:50, 18 March 2009 (UTC)

8192 square units?

The article says, the route is 8192 square units. I've been trying to calculate the length of the path, dividing 8192 by the width of the route (which seems to be 3 tiles, as the player is standing in the middle, and there's an equal amount of space on both of his sides, which is just as wide as one tile. Therefore, 3 tiles wide). However, 8192, being a power of 2, (2^13), isn't divisible by 3. So, this leaves three variants:

  • The length of the route is 8192 tiles. Which gives it an effective area of 8192 x 3 = 24 576 square units/tiles.
  • I am seeing things, and the route is 4 tiles wide. Which gives it a length of 8912 / 4 = 2048 tiles.
  • The 8192-tile area includes something else other than the path itself. However, the total becoming a perfect power of 2 by an accident (route length x 3 + whatever the extra bit is = 8192) seems unlikely.

So... Which one would that be? --[email protected]$_ /usr/bin/apache2 -k restart 23:51, 17 July 2010 (UTC)

Oh, and, of course, the fourth possibility: the area listed is the area of the whole map block the route is located on (as in, "A chunk of data loaded by the engine which contains the route and other stuff like events/music/weather data/whatever"), so the dimensions of the whole map block would be probably 128x256, route stretching along the longer side. --[email protected]$_ /usr/bin/apache2 -k restart 23:56, 17 July 2010 (UTC)
Given the Echidna's comment above, I think it's the fourth. But I haven't got the route, so IDK. —darklordtrom 00:43, 18 July 2010 (UTC)

Platinum Full Map image link

The "full map" image of Platinum posted July 8, 2014 instead links to an image from 2010.

Gamescook (talk) 04:00, 13 July 2014 (UTC)

Mistake about Generation III?

I hack Generation III games. When I read the part in the article which says that "it would be impossible for a game from Generation III or before to support this path without dividing it into several segments", I immediately went to test that and I concluded it's false: the image in the article is 3176 pixels, which works out to be about 198 tiles. Pokémon Emerald was completely able to load a 7x255 map (this is what it looks like). As you can see, the map is way bigger than the actual Seabreak Path, and yet the game supports it. Did I misunderstand what that part means, or is it, in fact, a mistake? I don't want to edit it out just yet, though. --Telinc1 (talk) 12:21, 4 March 2016 (UTC)

Main pic

The illustration used as the main image looks more like Flower Paradise than Seabreak Path to me, seeing how it has stairs and Shaymin. Shouldn't it be moved to that article? --Golden Trainer (talk) 01:25, 8 February 2019 (UTC)

I'm not sure if Oak follows you out that far, though I may be mistaken. --Spriteit (talk) 12:44, 10 February 2019 (UTC)
Oh, you're right. The fact Oak and the white rock are present means it must be the beginning of Seabreak Path at Route 224. Sorry, it has been a while since I played DPP. --Golden Trainer (talk) 11:36, 12 February 2019 (UTC)