Perhaps what makes this more confusing is that in this particular format, the primary arch appears to be using the "Object" header, instead of a more typical "arch" header, like you'd see in a map or inventory.
So it might look like this: Object chest weight 10 value 1 arch sword weight 10 value 100 end <- (ends the "sword" arch, which is nested inside the chest) end <- (ends the "chest" arch, which in this case is identified as an "Object") If you saw this on a map, it would be almost identical, except the very first "Object" line would be "arch". Maybe this helps? --DraugTheWhopper On Mon, Apr 8, 2019 at 12:27 PM Bob Tanner <tan...@real-time.com> wrote: > > Doing some spacing for readability > > Object altar_valkyrie > name Altar of Valkyrie > other_arch Valkyrie > type 56 > face altarvalk.111 > no_pick 1 > level 100 > arch altar_valkyrie_pray_event > end <— ends Object altar_valkyrie > end <— What does this end? > > Object altar_valkyrie_pray_event > title Python > slaying /python/gods/altar_valkyrie.py > type 116 > subtype 1 > end <— ends Object altar_valkyrie_pray_event > > > On Apr 8, 2019, at 11:21 AM, Kevin Zheng <kevinz5...@gmail.com> wrote: > > Yes. Here, there are nested objects. Every "Object" has a matching > "end", and so the first example is an "Altar of Valkyrie" containing a > Python "pray_event" that gets triggered when a player prays. > > > > --- > Bob Tanner <tan...@real-time.com> | Phone : 952-943-8700 > http://www.real-time.com, Linux, macOS | Fax : 952-943-8500 > Key fingerprint = F785 DDFC CF94 7CE8 AA87 3A9D 3895 26F1 0DDB E378 > > _______________________________________________ > crossfire mailing list > crossfire@metalforge.org > http://mailman.metalforge.org/mailman/listinfo/crossfire _______________________________________________ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire