Author Topic: Overworld Event findings  (Read 3201 times)

Agent 12

  • Zurvan Surfer (+2500)
  • *
  • Posts: 2572
    • View Profile
Overworld Event findings
« on: January 12, 2006, 04:00:47 am »
7E0041
7E0042

When these memory addresses are set to 11 it makes Layer 3 invisible (atleast in one instance)

7E0045
7E0046  

These 2 memory addresses change either the color or the transperency of Layer 3.  by removing either one of them the clouds on the overworld become solid

Command 28(02, 1)  Removing this line causes it to crash....I think it may be in every overworlds code

SpriteMovement-SpriteDestination(F2, 77)--snow
SpriteMovement-SpriteDestination(C3, 75)--no snow

Put between first initmemory and first end

SpriteMovement seems to be "Layer 3" movement.  To simulate snow you can use the top line makes layer 3 go really fast.  The bottom one is the slow drifting clouds in 1000 AD.

Now we can make snow in any overworld IF we could edit Layer 3 of overworlds to 15.  Now our only problem is the color, i'm trying to make is snow on 65 MIL but it's reddish brown


--jp

mintman

  • Iokan (+1)
  • *
  • Posts: 5
    • View Profile
Overworld Event findings
« Reply #1 on: January 13, 2006, 01:02:42 pm »
Quote
Command 28(02, 1) Removing this line causes it to crash....I think it may be in every overworlds code


I believe that's a fade in routine, actually. The first variable is time over which to fade, and the second is whether to fade in/out. Note that this seems to bug up if you have more than one pair of fades (ie, fade in, fade out, move screen, fade in, fade out - the last fade doesn't work in my case).

Command38 is a pause function - It still processes other objects, it just pauses this one.

Command2E and Command31 are tricky. I know that they are used in combination to move the camera; Command2E aims, and 31 actually moves it for the time specified.

It's hard to tell what any value will do in Command2E, so I'll just show you the signature and give you a tip on how to use it.
Command2E(aimage, more aimage, horizontal or vertical)
The two "aimage" parts are how you aim the camera. There's some correlation, but its hard to tell - you think you have it and then... just no.
Here's a trick though: if you want to move left, set the second aimage to FFFF, and the first to something less than that. For moving right, set the second aimage to 0000, and the first to something more than that. Essentially, |aimage1 - aimage2| is how fast you move. Now, you won't get uber-insane speeds, but if you want that, just mess around with the code for a while.

To actually move the camera is much simpler, just call 31 with a number representing how long you want it to move for. Yup.

-mintman