Please post an example 'script', or the real one,
that includes all your 'PRAGMA' and '#include' calls.
And the actions you want WED to access is in one(or more)
of the includes? Have I get that right? I have a sneaking
suspicion this cant be done.
I'll look into it tomorrow...
EDIT... Hmmm, seems you can use actions from includes...
OK, this the verbatim top chunk of one of my current projects
#define PRAGMA_PATH "@Mixer";
//
#include <acknex.h>
#include <default.c>
//
#include "Ent_Panel.c"
//
My folders are arranged like so. (and no tricky setting in SED)
GameStudio lives in.....:- G:\GStudio7\..
My project lives in.......:- G:\@LightFixer\..
'Ent_Panel.c' lives in......:- G:\@LightFixer\@Mixer\..
I put an action into "Ent_Panel.c" and was able to use it happily from WED without tricky settings. Cool !
My guess is your problem is this,
- Whenever you ADD a new script to a level in WED, you NEED to save & exit & restart WED for all actions
to become available through WED. - Whenever you MODIFY a new script assigned a level in WED, you NEED to save & exit & restart WED for all actions
to become available through WED.
That damned WED caches the attached script, and doesnt autoupdate if it gets changed. AND
it doesnt always give you ALL the actions in a script you've just attached.
A simple Save and Restart of WED seems to bring it all back on track though.
PS Make sure your actions DONT expect parameters or WED wont touch them.
action Move_Object()
{ blah,blah,blah } /// All Cool
action Move_Object( ENTITY* me )
{ blah,blah,blah } /// BAD - will 'work' in script but WED will ignore.