hmm proc may be the case.. so I just scrub where I had placed the earlier list and just duplicated it 4 times instead with Shipyard already in there. Problem solved.. but I would of thought I could of just added it in there without problems. DM is always coming back to bite me in my simple mind!!

LJR

If you are trying to add it into the default prototype's list (essentially, adding it at compiletime instead of runtime) then you will want to simply have it as part of the list to begin with.

var/list=list("text string")

There is a big difference between compiletime code and runtime code. All of your object types that you have defined are merely prototypes and are figured at compiletime, and they are all hard-coded and shall not change aftorwords. (Or constant, if you are familiar with that term. The compiler deals with constants to create the program.) At runtime the only thing you have control over are the functions (procs) that continually execute throughout the lifetime of your active program. These functions will access many of the constant settings that have been set at compiletime, and some of them (variables) are not even constant during runtime and can be changed.

In short, the compiler deals with constants. If you want something to be equal to something else at compile time then state that where you have it defined.

If you want to have extra control over the compiler, then use the compiler directives (those things that start with a '#'), such as #elif, #else, #endif, #if, #ifdef and #ifndef. Those can be handy for keeping code in your file and having the compiler ignore some areas while compiling others giving it more flexibility.

Yes someone mentioned that to me. I guess the ONLY place this can happen is inside a proc or a verb??? If so, I've learned something.

Yeah outside of verbs and procs things can only be initialized to constant values. Anything that does something other than that must happin within a verb or proc.