Primary Zelda Hacking
April 21, 2014, 09:25:30 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Current Zelda Oracles Hacking Suite beta version: 0.05
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: On "Time Holes"  (Read 408 times)
Marky
Newcomer
*
Offline Offline

Posts: 20


View Profile
« on: January 27, 2012, 04:27:02 AM »

I've been playing around a little with making Time Hole tiles, and I just thought I should share, in case nobody else has discovered the distinction yet, the interaction addresses for different types of Time Holes - the ones activated by your 'Tune of Echoes'.

E100 creates a standard time hole that is activated by the harp.
E101 creates a permanently open time hole, which will stay active even if you leave the map.

I've been studying the start event where Veran attacks Nayru, trying to figure out how the game then turns off the permanently active portal that Veran opens on the ridge.  I do know that exactly as the time hole is activated, the map's memory address goes from D0 to D8.  This seems to be significant in some way because whenever the 'Tune of Echoes' is played to activate an 'E100' type time hole, the map's value changes from x0 to x8.  If anyone else has done much work on these interactions, I'd be interested to know if there was a way to change the ID of a type 2 interaction, in this case to change it from 'E101' to 'E100', making a portal that is opened by an event and then becomes one that the player can activate with the harp.

Edit:  Or, alternatively, if anyone knows how to 'despawn' a type 2 interaction via a script, if either are possible.
Logged
Lin
ZOLE Creator
Administrator
Hero Member
*****
Online Online

Posts: 580



View Profile
« Reply #1 on: January 27, 2012, 06:00:04 AM »

This can be achieved using a script and a fixed-address set. Interactions are stored in Dx40-Dx7F. Dx40 is 00 or 01 (disabled/enabled), Dx41-Dx42 being the interaction ID. Dx44 is the state of the interaction, which is probably what you're look for. You can try to use VBA's memory viewer and see if the x for the portal is always the same (as in the interaction index). If it is, a script can use the setmemory function and change either the Dx44 to 00 (likely) or the Dx40 to 00. Hope this helps!
Logged
Marky
Newcomer
*
Offline Offline

Posts: 20


View Profile
« Reply #2 on: January 29, 2012, 02:51:31 AM »

Thanks for the reply, Lin, I'll start to look into that, I'm just hoping you could explain something else to me, if you don't mind, because I'm not very experienced with the coding side of this.  How exactly do I find the Dx40-Dx7F addresses in the VBA memory viewer?  Is it 0xD000 WRAM?

Nevermind that, I figured out what you meant and I understand how that part works with interactions now.

I noticed that all the "time hole" interactions have '81' in the 'Dx40' address.  Is this unusual?
« Last Edit: January 29, 2012, 02:58:49 AM by Marky » Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!