There's a problem with the way the direction is set...
The direction "left" is relative to the player, while the direction 1 is absolute. If the camera yaw is 90°, choosing "left" will point the entity away from the player. (This is why I didn't implement named directions myself.)
Is there a way to get the camera yaw with Cubescript?

EDIT: Have something all ready, now I just have to figure out where to put it... >_<
// Adds $yaw, which returns the current camera yaw
s_sprintfd(yawalias)("yaw = [%s]",camera1->yaw);
execute(yawalias);
// end $yaw
(It's adapted from someone's /reconnect hack.)

Mmmh. Yeah - that's probably confusing for newcomers,
but it's the same issue you have with rotated mapmodels, jumppad properties etc. etc.
And I really see now big deal in setting up the most of the entity via the GUI,
then if it's not pointing the right way to mark it, press the dot-key (".") and entset it the way it should be ;)

re:code
Try something more along these lines (in fpsgame/client.h)

// this could go directly below the getname/getteam definitions
extern void intret (int v);
CCOMMAND(getyaw, "", (clientcom *self), intret(self->player1->yaw));


Then you could do the following inside CubeScript:

cpy = (getyaw)
fd = $cpy
if (= 0 $cpy) [ fd = "North" ] [ ]
if (= 90 $cpy) [ fd = "East" ] [ ]
if (= 180 $cpy) [ fd = "South" ] [ ]
if (= 270 $cpy) [ fd = "West" ] [ ]
echo You are facing $fd


Yeah, that did it, but it'd be more convenient to just have a $yaw... though any script wanting a $yaw could just do "yaw = (getyaw); ...".

Anyway, I'll whip something up for the GUI tomorrow (unless you want to race me to it).

EDIT: Here it is. Kind of hackish. I'm sure the yaw figuring could be done better. (The directions could also be done with variables added to make offsets, but I thought that'd be too complicated.)

Oh, and just to get it out of the way: you need to modify fpsgame/client.h as mentioned by MeatROme in the previous post (and recompile).

newgui "EB-dir" [
if (|| (< (getyaw) 45) (> (getyaw) 315)) [
guibutton [up] [ _EBbo = 0; _docm ]
guibutton [down] [ _EBbo = 3; _docm ]
guibutton [left] [ _EBbo = 4; _docm ]
guibutton [right] [ _EBbo = 1; _docm ]
guibutton [forward] [ _EBbo = 5; _docm ]
guibutton [backward] [ _EBbo = 2; _docm ]
]
if (&& (< (getyaw) 135) (> (getyaw) 45)) [
guibutton [up] [ _EBbo = 0; _docm ]
guibutton [down] [ _EBbo = 3; _docm ]
guibutton [left] [ _EBbo = 5; _docm ]
guibutton [right] [ _EBbo = 2; _docm ]
guibutton [forward] [ _EBbo = 1; _docm ]
guibutton [backward] [ _EBbo = 4; _docm ]
]
if (&& (< (getyaw) 225) (> (getyaw) 135)) [
guibutton [up] [ _EBbo = 0; _docm ]
guibutton [down] [ _EBbo = 3; _docm ]
guibutton [left] [ _EBbo = 1; _docm ]
guibutton [right] [ _EBbo = 4; _docm ]
guibutton [forward] [ _EBbo = 2; _docm ]
guibutton [backward] [ _EBbo = 5; _docm ]
]
if (&& (< (getyaw) 315) (> (getyaw) 225)) [
guibutton [up] [ _EBbo = 0; _docm ]
guibutton [down] [ _EBbo = 3; _docm ]
guibutton [left] [ _EBbo = 2; _docm ]
guibutton [right] [ _EBbo = 5; _docm ]
guibutton [forward] [ _EBbo = 4; _docm ]
guibutton [backward] [ _EBbo = 1; _docm ]
]
]

I'm relatively sure it works correctly, I tested the forward and left directions in eight positions with smoke and they all worked correctly. If something doesn't, let me know.

All the tab-spacing is there, but you'll have to go into the source and strip the HTML or redo it yourself.

I wasn't too good with the spatial stuff in my head, so I drew up this little aid consisting of a pair of two axes, labeled F-R-B-L and 5-1-2-4 respectively (N-E-S-W) to help me out. Very useful.

EDIT: Oops. Forgot to turn the greater-than and less-than signs into &lt;s and &gt;s. (Changed ampersands to &amp;s just for the heck of it as well).)

did you add exec entfogcol.cfg to your autoexec.cfg?
guifields need to be commited to the new value by hitting RETURN.

Yeah, that little red cube 'n all.
The point is, the directions are absolute, while "left" and "right" are relative... If you face a direction other than 0°, if you choose "left", it won't point left. Left of 0°, sure, but not left of the player/camera.

(And please use the "reply" link, it makes things much easier.)

I know what you mean, but absolute directions are difficult to write. And relative directions aren't possible to write into a gui. Perhaps you've a better idea how to name the directions.

(used the "reply" link :) don't know why i didn't use it the last time)

It's not possible... yet.
I have a little snippet of code (see lower post), but I can't figure out where to put it... Everywhere I've tried in engine/rendergl.cpp causes a segfault when it's executed. Maybe I'll ask on the forums.

I need help getting the particle guide on sauerbraten can you give me the steps??