autorun_e(ID)

[Lx Xzit]

This function would let us know when the conditions to execute an autorun event are met, without having to make an autorun event and adding a flag or make it trigger an script. The main advantage of this is that scripts would require less user-intervention, plus it would help to our scripts to be more organized.

It should be read-only and the only parameter is the ID of the auto-run event (starting from "P Switch - Start"):

Spoiler

Here's an example of an usage.

Code: Select all

do
   if autorun_e(3)
      call showmsg("The level has ended!")
   end if
   call sleep(1)
loop

This would open a lot of possibilities, like executing a script when an NPC dies/gets killed, when the player gets a power-up or gets hurt, etc.. All without having to do messy autorun events triggering.

[Victor ManuelMR]

This function would let us know when the conditions to execute an autorun event are met, without having to make an autorun event and adding a flag or make it trigger an script. The main advantage of this is that scripts would require less user-intervention, plus it would help to our scripts to be more organized.

It should be read-only and the only parameter is the ID of the auto-run event (starting from "P Switch - Start"):

Spoiler

Here's an example of an usage.

Code: Select all

do
 if autorun_e(3)
 call showmsg("The level has ended!")
 end if
 call sleep(1)
loop

This would open a lot of possibilities, like executing a script when an NPC dies/gets killed, when the player gets a power-up or gets hurt, etc.. All without having to do messy autorun events triggering.

For example, how could I activate a death event if the second or first player dies?
and another, was the script supposed to repeat this sample message several times?

[NESTED ERNEST]

I am sorry to disappoint you, but the truth is that this suggestion was not added (ie it doesn't work), you can put autorun_e(3) or autorun(3) or autorublablablamm(3) or asujkdhsiuak and this will continue to run.

[Lx Xzit]

I am sorry to disappoint you, but the truth is that this suggestion was not added (ie it doesn't work), you can put autorun_e(3) or autorun(3) or autorublablablamm(3) or asujkdhsiuak and this will continue to run.

I just noticed that

[NESTED ERNEST]

1.4.5 path 29 does can detect the error.

[NESTED ERNEST]

A more serious answer(Although it is a possible information for other readers) (I can be right) (this is hypothetical)

If this were added I think this would not be 100% as you think: that script (that he put above) you would not have to put it in a loop and that script would have to be executed within an event "called" "the last event to execute all events "and that function called autorun would only work in the execution of that particular script in that particular event(Well an autorun with a higher index if you could read a previous one within an autorun original event)(you would not have to put that script in the Level - Start event, that hypothetical function would always return 0 and you would interpret it as an error). And the original event would be executed first and then this one, since it is executed in the "last event of all", so be careful.

Added after 16 hours 46 minutes:
I forgot.

For example, how could I activate a death event if the second or first player dies?

That "problem" you raise, we actually already have them(without this suggestion): they can be solved with programming.

In this script, on Death Event, execute each player's kill once:

Spoiler

(This scritp doesn't take into account the resurrection of the player so if the player revives you have to do v(death1)=0 and v(death2)=0)

Code: Select all

if v(death1)=0 then
   if char(1).alive=0 then
   'scripts
   v(death1)=1
   end if
end if

if sysval(gamemode)>0 then   
   if v(death2)=0 then
      if char(2).alive=0 then
      'scripts      
      v(death2)=1
      end if
   end if
end if

was the script supposed to repeat this sample message several times?

It is the same as normal, this would reset the value of the "autorun ()".