Jump to content

actuallyincombat and combatcounter


Recommended Posts

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.

 

 

Link to comment

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
Link to comment

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....

Link to comment

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

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...