Jump to content

Recommended Posts

Posted

It turns out the run_special function passes a location of the special being called (special location, item user location, monster that triggered special location) as one of its arguments. I've noticed that in a few places, the engine simply passes a null location (0,0), but really this field is not used.

 

I'm wondering if we should make use of this feature, and what the best way to be to use it would be. I've come up with a few options:

 

1) A new node that puts the x and y coordinates into two different flags which can be referenced with a pointer. Somewhat cumbersome but highly flexible.

2) Reserved "pointers", say -10 and -11 that when the field has this value, it replaces it with the x and y coordinates respectively.

3) Node specific defaults. Whereever a location is requested, -1,-1 will be replaced by the appropriate location of the special.

 

What are people's thoughts on this matter?

  • 3 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...