Crossfire Server, Trunk
_change_arch Struct Reference

#include <treasure.h>

+ Collaboration diagram for _change_arch:

Data Fields

const char * name
 
const char * slaying
 
const char * title
 

Detailed Description

when a treasure got cloned from archlist, we want perhaps change some default values. All values in this structure will override the default arch. TODO: It is a bad way to implement this with a special structure. Because the real arch list is a at runtime not changed, we can grap for example here a clone of the arch, store it in the treasure list and then run the original arch parser over this clone, using the treasure list as script until an END comes. This will allow ANY changes which is possible and we use ony one parser.

Todo:
is this still used somewhere in the maps/code??

Definition at line 51 of file treasure.h.

Field Documentation

◆ name

const char* _change_arch::name

If != NULL, copy this over the original arch name

Definition at line 52 of file treasure.h.

◆ slaying

const char* _change_arch::slaying

If != NULL, copy this over the original arch slaying

Definition at line 54 of file treasure.h.

◆ title

const char* _change_arch::title

If != NULL, copy this over the original arch title

Definition at line 53 of file treasure.h.


The documentation for this struct was generated from the following file: