Re: [crossfire] Questions about archetype files

2019-04-16 Thread Mark Wedel 

On 04/16/2019 12:38 PM, Bob Tanner wrote:

Got another question.

Is the name attribute not required?

Just 1 example I found.

The Dragon Guild object does not have a name field?


 If name is not set, it uses the name from the Object field.  So it is not 
required.




construct/town/dragon_guild.arc

Object Dragon Guild
face dragon_guild.x11
type 66
no_pick 1
move_block all
client_type 25012
end
More
Object dragon_guild_2
name Dragon Guild
face dragon_guild.x11
type 66
no_pick 1
move_block all
x 1
end
More
Object dragon_guild_3
name Dragon Guild
face dragon_guild.x11
type 66
no_pick 1
y 1
end
More
Object dragon_guild_4
name Dragon Guild
face dragon_guild.x11
type 66
no_pick 1
x 1
y 1
end


---
Bob Tanner| 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

Re: [crossfire] Questions about archetype files

2019-04-16 Thread Bob Tanner 
Got another question. 

Is the name attribute not required?

Just 1 example I found.

The Dragon Guild object does not have a name field?

construct/town/dragon_guild.arc

Object Dragon Guild
face dragon_guild.x11
type 66
no_pick 1
move_block all
client_type 25012
end
More
Object dragon_guild_2
name Dragon Guild
face dragon_guild.x11
type 66
no_pick 1
move_block all
x 1
end
More
Object dragon_guild_3
name Dragon Guild
face dragon_guild.x11
type 66
no_pick 1
y 1
end
More
Object dragon_guild_4
name Dragon Guild
face dragon_guild.x11
type 66
no_pick 1
x 1
y 1
end


---
Bob Tanner| 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

Re: [crossfire] Questions about archetype files

2019-04-09 Thread Andreas Kirschbaum 
Bob Tanner wrote:
> 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

This line ends "arch altar_valkyrie_pray_event". This allows to
customize the inventory object. Or one could even create recursive
inventories by nesting "arch xyz...end" blocks.


> end <— What does this end?

This line ends "Object altar_valkyrie".
___
crossfire mailing list
crossfire@metalforge.org
http://mailman.metalforge.org/mailman/listinfo/crossfire

Re: [crossfire] Questions about archetype files

2019-04-09 Thread Nathaniel Kipps 
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  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  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| 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

Re: [crossfire] Questions about archetype files

2019-04-08 Thread Bob Tanner 
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 
mailto: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 mailto: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

Re: [crossfire] Questions about archetype files

2019-04-08 Thread Kevin Zheng 
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.

Hope that helps,
Kevin

On 4/8/19 9:19 AM, Bob Tanner wrote:
> Working on a project and I’m parsing the .arc files for crossfire and I
> finding some files with entries I cannot understand. 
> 
> I’d like to know if there’s a reason for these entries or if I need to
> change the code that is parsing the entries to handle these side cases.
> 
> Couple examples.
> 
> gods/altars/altarvalk.arc
> 
> 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
> end
> Object altar_valkyrie_pray_event
> title Python
> slaying /python/gods/altar_valkyrie.py
> type 116
> subtype 1
> end
> 
> Is the double “end” necessary? Bug? Typo?
> 
> Another example
> 
> ground/temp_summon_fog.arc
> 
> Object temp_summon_fog
> name fog
> face fog.111
> animation temp_fog
> type 67
> move_type fly_low
> no_pick 1
> is_used_up 1
> resist_fire 100
> resist_electricity 100
> resist_confusion 100
> resist_acid 100
> resist_drain 100
> resist_weaponmagic 100
> resist_ghosthit 100
> resist_poison 100
> resist_slow 100
> resist_paralyze 100
> resist_turn_undead 100
> resist_fear 100
> resist_cancellation 100
> resist_deplete 100
> resist_death 100
> material 1
> changing 1
> blocksview 1
> weight 10
> value 1
> speed 0.5
> arch event_destroy
> name GenerateFog
> title Python
> slaying /python/Moving_Fog.py
> end
> end
> 
> The double ends seems to happen with the “title Python”.
> 
> Any help would be appreciated.
> ---
> Bob Tanner mailto: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
> 


-- 
Kevin Zheng
kevinz5...@gmail.com | kev...@berkeley.edu | PGP: 0xC22E1090
___
crossfire mailing list
crossfire@metalforge.org
http://mailman.metalforge.org/mailman/listinfo/crossfire

[crossfire] Questions about archetype files

2019-04-08 Thread Bob Tanner 
Working on a project and I’m parsing the .arc files for crossfire and I finding 
some files with entries I cannot understand.

I’d like to know if there’s a reason for these entries or if I need to change 
the code that is parsing the entries to handle these side cases.

Couple examples.

gods/altars/altarvalk.arc

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
end
Object altar_valkyrie_pray_event
title Python
slaying /python/gods/altar_valkyrie.py
type 116
subtype 1
end

Is the double “end” necessary? Bug? Typo?

Another example

ground/temp_summon_fog.arc

Object temp_summon_fog
name fog
face fog.111
animation temp_fog
type 67
move_type fly_low
no_pick 1
is_used_up 1
resist_fire 100
resist_electricity 100
resist_confusion 100
resist_acid 100
resist_drain 100
resist_weaponmagic 100
resist_ghosthit 100
resist_poison 100
resist_slow 100
resist_paralyze 100
resist_turn_undead 100
resist_fear 100
resist_cancellation 100
resist_deplete 100
resist_death 100
material 1
changing 1
blocksview 1
weight 10
value 1
speed 0.5
arch event_destroy
name GenerateFog
title Python
slaying /python/Moving_Fog.py
end
end

The double ends seems to happen with the “title Python”.

Any help would be appreciated.
---
Bob Tanner mailto: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