Avenger Posted February 3, 2018 Posted February 3, 2018 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. Quote
Roxanne Posted February 3, 2018 Posted February 3, 2018 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. Quote
Avenger Posted February 3, 2018 Author Posted February 3, 2018 (edited) 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 February 3, 2018 by Avenger Quote
Roxanne Posted February 3, 2018 Posted February 3, 2018 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.... Quote
Recommended Posts
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.