Automatic Ego Motion Problem (SCI0)

[WD-40]

I, for one, recommend getting used to Sierra Script. It's just better.

I have always used Sierra script, just because it's always been the default in my installations

I finally solved the problem of the ego not stopping for the first keypress during a setMotion. Something in SetUpEgo() was causing the problem, I'm too lazy to pinpoint exactly what it is. My updated grabber script is tiny and dare I say even better than sierras.

[troflip]

I have always used Sierra script, just because it's always been the default in my installations

I'm confused... all the code you posted is SCI Studio script. But when you create a new project, SCI Companion should default to Sierra script.

[WD-40]

I'm confused... all the code you posted is SCI Studio script. But when you create a new project, SCI Companion should default to Sierra script.

Well darn, I have been learning SCI Studio script all this time. Is there anything wrong with that? are there any advantages other than being "a hardcore sierra programmer"?

I find both scripting languages ugly, but I find Sierra script even uglier than SCI studio script. 




Would it be so wrong for these scripts to have "x = 1" rather than "= x 1"? My brain crashes every time I see this backwards style. 

[Kawa]

It's not ugly, it's Lisp.

[troflip]

Would it be so wrong for these scripts to have "x = 1" rather than "= x 1"? My brain crashes every time I see this backwards style. 

It's called prefix notation, and like Kawa said, LISP uses it. It feels weird to you because you're not used to it.

It's also fairly easy to write a parser for it for the compiler, so I'm guessing maybe that's why Sierra used it?

[MusicallyInspired]

It's easier if you read it a different way in your head. "= x 1" can be read "assign x the value of '1'". That's how I wrapped my head around it anyway.

[WD-40]

Not that anyone cares, but I nailed down exactly what was causing the ego to ignore my keyboard input to stop.

When calling a setMotion the ego will walk just like you pressed a key to make him/her/it walk. However, when asked to stop with keyboard input the ego will ignore your first key press.

When calling a setMotion on the ego it's also necessary to notify it that it's moving in that direction: "(User:prevDir(RIGHT))". This way when you press a key to stop, it will know to stop with a single key press.

[MusicallyInspired]

I care! Always nice to see someone solve their problems for posterity. There were so many cases of this on the mega-tokyo boards that are now simply lost to time.

[troflip]

When calling a setMotion on the ego it's also necessary to notify it that it's moving in that direction: "(User:prevDir(RIGHT))". This way when you press a key to stop, it will know to stop with a single key press.

Another option is to disable input until they've completed the entrance animation.

[WD-40]

When calling a setMotion on the ego it's also necessary to notify it that it's moving in that direction: "(User:prevDir(RIGHT))". This way when you press a key to stop, it will know to stop with a single key press.

Another option is to disable input until they've completed the entrance animation.

I'm not talking about an entrance animation. In some games the ego will enter a room and walk clear across that room and into the next room without any keyboard input. You can stop the ego in its tracks at anytime to explore that room by taking control with the keyboard. To make the ego respond normally to keyboard control you have to tell it what its direction is with "(User:prevDir(RIGHT))". I hope that clears things up.

[MusicallyInspired]

Yes, that's how AGI egos always behaved from screen to screen.