Hi there SaberMaster (and everyone else)
First off, even if Daft_Vader doesn't say it ( ;p ), thanks for the revised COG, I had a suspicion that there would probably be a few things to iron out.
Next thing, about only having 10 posts (11 after I finish this one
) I've been frequenting Massassi for over four years now, but never had the confidence to post any replies to COG questions. For one thing I didn't have too much programming experience back then, so I thought I'd wait and stay silent until I knew enough of the language, before attempting to post answers
Nowadays, seeing not so much of GBK and _*Seifer*_ around to help young newbies in their COG endeavours (mercifully, you're still around to help "nurture" us budding coggers), after learning Java for two years at uni (and still learning, with a bit of C thrown in for good measure ;p ), I thought I finally had enough knowledge and *confidence* to start posting COG programming answers.
After reading through what you written, the thing that hits me first (and I'm surprised I didn't add it when I was writing the COG) was "DUH - no 'exited' declared in symbols" lol
Secondly, I had my doubts about the defining of msgSender and msgSource in "startup:" lol. It was a lapse of concentration - maybe I didn't notice it because the COG was working as I wanted it to (in terms of actually having an effect upon the player).
Thirdly - implementing a loop. Yes, I know that would have been more efficient code (and a more practical solution). I must confess that aspects of this COG were placed in sections, just so that I could follow the code's execution. Hence the pointless "Print" messages, due to poor variable definitions, as you mentioned lol Also, I've had problems with loops in COG - java's fine, but COG still seems to dislike me when I use them
We're not on speaking terms lol
I also fully concur with your mention of the player entering the trigger sector twice. I dwelt on that aspect for about a half hour or so, but thought that Daft_Vader would want a COG that was working rather than flawlessly perfect. That said, if people like yourself can quickly devise a flawless solution (even if you based it on my work ;p ), then lets, by all means, provide a quick, correct answer
In short (lol - sorry to labour the point - you can tell I'm English can't you), my version of the COG worked (if, as you pointed out, a little screwy lol). But if you don't object, I would like to use this COG in one of my own levels, having had a few ideas while I quickly drummed up the script - do I have your permission...
Thanks for going through the COG and ironing out the stray wrinkles - the ones that got through...
As I always say, you can never have enough constructive criticism. Thanks for the praise, you've given though
and the COG advice & improvement. It's much appreciated and I hope that I can continue to help all the "new" breed of COGgers. Let's face it - at the end of the day, we're all here to keep JK/MotS alive ... and we've been doing a dang good job so far ;p
-Jackpot
"You're never too old to stop learning"
------------------
"Life is mostly froth and bubble,
But two things stand in stone,
Kindness in another's trouble,
Courage in your own"
("Ye Wearie Wayfarer" - by Adam Lindsay Gordon)
[This message has been edited by lucky_jackpot (edited July 30, 2003).]