scripting

Just ask yourself,

Does this need to be easily changeable?

The simple answer is that anything that would be considered data would fall under what you're calling scripting everything else would be part of the game engine.

The more complex answer is that your are really combinging scripting and entity data. You might consider seperating the two. For instance a weapon would be data, and a monster would be data, a monster may also include an action script that details its actions.

yeah- I was thinking about separating the two.

The reason I am asking about what to separate and what to leave to core is because my scripting engine will probably not be very fast because it loads the scripting files (essentially txt files) into arrays where each entry is a word (command, variable, operator, etc). Every loop, the array is evalutated, which I assume will be very slow. I'm going to try to limit the number of scripts by making certain specific but solid things made into core components. Is doing this bad for future versatility?

Anyway, I will hopefully speed up my script evaluation loop and solidify the language and syntax.

I don't know what else to ask you until I plan the game further.

I HIGHLY RECOMMEND WATCHING THIS LECTURE about game design and production. It is applicable to almost everyone either in indie, commercial, or recreational game production. It separates the myths between preproduction and actual production. If you find the time I HIGHLY recommend this. It changed my life. (in the sense of production) (60 min) http://www.gamasutra.com/features/slides/cerny/index.htm