Is ADD_AREA_REGION_TRIGGER ok to use now?

[Lauriel]

I'm putting in a couple new travel triggers to an existing area.  There are half a dozen different examples to choose from, as well as the macro ADD_AREA_REGION_TRIGGER that is included with Weidu.  There are old posts (as well as the Weidu doc) that say don't use the v211 version of this macro.  The version we have was put in v212, so is it safe now?  Is it the preferred method?  This is the first time where I have TOO many ways of doing something. LOL

[Lauriel]

I believe my test has answered my own question.  I get an error with the Weidu ADD_AREA_REGION_TRIGGER (ERROR: illegal 4-byte read from offset 84 of 6-byte file).  Looks like a READ_LONG should have been used here.  Shouldn't someone fix that?  Someone smarter than me?  Or am I completely off my nut and have done something horrible to break an innocent piece of code?

EDIT: Thought it would be nice if I actually let folks see my code...

Spoiler

COPY_EXISTING ~BG0109.BCS~ ~override~
   LPF ADD_AREA_REGION_TRIGGER
      INT_VAR
         ab_RT_Type = 2 /* Type of trigger -- 0=proximity;1=info;2=travel */
         ab_RT_BbLX = 1092 /* Bounding Box - low x value - LEFT */
         ab_RT_BbLY = 681 /* Bounding Box - low y value - TOP */
         ab_RT_BbHX = 1263 /* Bounding Box - High x value - RIGHT */
         ab_RT_BbHY = 812 /* Bounding Box - High y value - BOTTOM */
         ab_RT_VxPr = 5 /* Number of Vertex Pairs for current region */
         ab_RT_CuId = 28 /* Cursor Index - points to a graphic in cursors.bam */
         ab_RT_LPoX = 1044 /* Launch Point X */
         ab_RT_LPoY = 596 /* Launch Point Y */
         ab_RT_Vx_X_0 = 1177 /* Point #0 X value */
         ab_RT_Vx_Y_0 = 681 /* Point #0 Y value */
         ab_RT_Vx_X_1 = 1116 /* Point #1 X value */
         ab_RT_Vx_Y_1 = 731 /* Point #1 Y value */
         ab_RT_Vx_X_2 = 1092 /* Point #2 X value */
         ab_RT_Vx_Y_2 = 761 /* Point #2 Y value */
         ab_RT_Vx_X_3 = 1163 /* Point #3 X value */
         ab_RT_Vx_Y_3 = 812 /* Point #3 Y value */
         ab_RT_Vx_X_4 = 1263 /* Point #4 X value */
         ab_RT_Vx_Y_4 = 735 /* Point #4 Y value */
      STR_VAR
         ab_RT_Name = ~Door#lbd0103a~ /* Name to assign to new region */
         ab_RT_Dest = ~#LBD0103~ /* Destination Area */
         ab_RT_EntN = ~ExitBD0100a~ /* Entrance Name */
   END
BUT_ONLY_IF_IT_CHANGES

 

Edited February 2, 2020 by Lauriel

[Mike1072]

You should be running the function on the .are file, not .bcs.

[Lauriel]

OMG that's hilarious!  Yes, silly woman, you did something horrible.  LOL  I just must have put BCS out of habit.  I knew I was modifying an ARE file.  Thank you, @Mike1072 for pointing out my missteps.  Shall I call you Gandalf?  Please don't call me Bilbo.

Edited February 2, 2020 by Lauriel

[Mike1072]

It's nice when the problems turn out to be easy fixes.