It is common, if not essential, to use the exact same event name in several events.
It is a powerful tool, to save on text strings and to actually do a "poor man's OR" event.
Note one huge potential pitfall:
ALL of the events using a common name will have the "MaxOccurs" set to [color="Red"]the smallest value of ANY [/color]of the events.
Thus, if 5 events are named "evt_nam_test" with MaxOccurs at 999, and one event with "evt_nam_test" is set to MaxOccurs 1, then the MaxOccurs for all is 1 [this was bugging a MC event in RoP].
This is due to the way the engine keeps track of MaxOccurs and CuOccurs [you can see status of all events in the .hst files, near the end]
Using the same event name in multiple events
Always ask yourself: "Am I part of the Solution?" If you aren't, then you are part of the Problem!
[CENTER][/CENTER]
[CENTER]Visit AGEWiki - your increasingly comprehensive source for information about AGE games[/CENTER]
[CENTER]Rules for new members[/CENTER]
[CENTER]Forum Rules[/CENTER]
[CENTER]Help desk: support@slitherine.co.uk[/CENTER]
[CENTER][/CENTER]
[CENTER]Visit AGEWiki - your increasingly comprehensive source for information about AGE games[/CENTER]
[CENTER]Rules for new members[/CENTER]
[CENTER]Forum Rules[/CENTER]
[CENTER]Help desk: support@slitherine.co.uk[/CENTER]
Return to “Modding AGE engine games”
Who is online
Users browsing this forum: No registered users and 7 guests