Jump to content

Photo

actuallyincombat and combatcounter


3 replies to this topic

#1 Avenger

Avenger
  • Modders
  • 3800 posts
  • Gender:Male
  • Location:Hungary

Posted 03 February 2018 - 07:11 AM

These triggers check on variables in the 'current area'.

 

If you noticed that these triggers work sometimes differently in baldur.bcs - it is because baldur.bcs calls the current master area to check on combat.

So if the combat occurs in a non-master area, baldur.bcs won't detect it.

 

 



#2 Roxanne

Roxanne

    Modder

  • Modders
  • 2041 posts
  • Gender:Female
  • Location:Auckland, NZ

Posted 03 February 2018 - 11:35 AM

Just to clarify - this behavior is for baldur,bcs, right?

If i use them in an NPC's file it will check for current area.


The Sandrah Saga!

another piece of *buggy, cheesy, unbalanced junk*

 

 

 


#3 Avenger

Avenger
  • Modders
  • 3800 posts
  • Gender:Male
  • Location:Hungary

Posted 03 February 2018 - 12:52 PM

Yes. This seems to affect only the global script. 

Areas check themselves, and other objects check their owner area.

 

There could be other cases where the 'current area' isn't exactly the one you would expect.


Edited by Avenger, 03 February 2018 - 12:52 PM.


#4 Roxanne

Roxanne

    Modder

  • Modders
  • 2041 posts
  • Gender:Female
  • Location:Auckland, NZ

Posted 03 February 2018 - 01:24 PM

Yes. This seems to affect only the global script. 

Areas check themselves, and other objects check their owner area.

 

There could be other cases where the 'current area' isn't exactly the one you would expect.

Maybe this prevents one or the other modder to litter everything into baldur.bcs....


The Sandrah Saga!

another piece of *buggy, cheesy, unbalanced junk*

 

 

 




Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users