Scriptproblem/Bug (?) with counters in ACS.

[Lanie]

Dear Doomers,

 

i have a problem. I made a barrier that should open by pushing three separate buttons. For this i used a script in ACS. Map is in UDMF/GZDOOM.

 

Here is one example for one the three buttons:

 

script (31) (void) {

a = a +1;

if(a == 3)
    {
        SetLineTexture(10, SIDE_BACK, TEXTURE_BOTTOM, "Red");
        Floor_LowerToNearest(21,100);

        }

}

 

Of course the map/script starts with global int 0:a;

 

So far so good. So where is the problem? Well, if i start my map right in the room where the buttons are, there is no problem and everything works fine. But if i start my map from the beginning and fight my way to the part with the three buttons, the script does not seem to work.

 

Can you help me out? Got any ideas?

 

Have a good day,

Lanie.

Edited June 8 by Lanie

[redEYE]

6 hours ago, Lanie said:

Of course the map/script starts with global int 0:a;

 

Global varables aren't reset even in between hubs. If you really need one make sure you aren't using it elsewhere.

 

You could do self diagnostics tests :P Either add an this extra line in all your switch scripts to show the value after triggering one:

 

script (31) (void) {

a = a +1;
print(d:a);

if(a == 3)
...

Or monitor the value all the time:

 

global int 0:a;

 

script 200 OPEN {
print(d:a); delay(35);

restart;
}

Edited June 8 by redEYE
typo

[Lanie]

On 6/8/2024 at 3:42 PM, redEYE said:

 

Global varables aren't reset even in between hubs. If you really need one make sure you aren't using it elsewhere.

  

You could do self diagnostics tests :P Either add an this extra line in all your switch scripts to show the value after triggering one:

 

script (31) (void) {

a = a +1;
print(d:a);

if(a == 3)
...

Or monitor the value all the time:

 

global int 0:a;

 

script 200 OPEN {
print(d:a); delay(35);

restart;
}

 

Hey! I will try this at the weekend! Thank you.

[Lanie]

On 6/8/2024 at 3:42 PM, redEYE said:

 

Global varables aren't reset even in between hubs. If you really need one make sure you aren't using it elsewhere.

 

You could do self diagnostics tests :P Either add an this extra line in all your switch scripts to show the value after triggering one:

 

script (31) (void) {

a = a +1;
print(d:a);

if(a == 3)
...

Or monitor the value all the time:

 

global int 0:a;

 

script 200 OPEN {
print(d:a); delay(35);

restart;
}

 

What would be the alternative to a global value in this case?

 

Anyway, i used your method and i found out that the numbers are going up after the first 5 or 10 seconds of the map. This is odd.

Edited June 15 by Lanie

[Lanie]

I got clue - and another mistery! The global value >a< is raised when the player is crossing a linedef that does raise the global value of >b<. But...why is this so? Is this a topic for another thread? I need some help. :(

Edited June 15 by Lanie

[Lanie]

Solved! I changed the global values to int a = 0.

Edited June 15 by Lanie