Page 6 of 12
Posted: Wed Dec 12, 2007 12:08 pm
by Commander McLane
Cmdr. Maegil wrote:Oh, my, didn't we woke up feeling slightly pedantic today?

Pedantic? Me??? Never!!!!!
"didn't we
woke up"????? I beg you!!!!!!!

Posted: Wed Dec 12, 2007 1:48 pm
by Cmdr. Maegil
A very well placed straw man argument, exploiting my lack of domain over english - it actually sentme back, reeling, in search of my verb tables...
But nevertheless, your correction was misplaced. Woke is a proper past tense and it sounds better (or at least more cultured) than "waked"; you'd have done better in nitpicking about the use of "didn't" and "haven't", to which I'd have no defenses...
Posted: Wed Dec 12, 2007 2:38 pm
by TGHC
Cmdr. Maegil wrote:about the use of "didn't" and "haven't", to which I'd have no defenses...
/me Tosses over a blunderbuss
Posted: Wed Dec 12, 2007 2:55 pm
by Cmdr. Maegil
Oh, my! What am I doing on our beautiful, most peaceful, friendiest board this side of Riedquat?!
Sorry, I'll try to behave and leave any flame(ish) trolling for the
E 
BBS...
EDIT: it must have been a bout of dislexia! That's why I behaved so atrociously on these Sacred Grounds!
Please grant forgiveness to this relapse penitent.
Posted: Wed Dec 12, 2007 3:02 pm
by Captain Hesperus
Cmdr. Maegil wrote:
Sorry, I'll try to behave and leave any flame(ish) trolling for the OBBS... oops:
I assume you mean the
EBBS....
Captain Hesperus
Posted: Wed Dec 12, 2007 5:35 pm
by matt634
Thanks for the responses but I figured out the problem. It wasn't where I put the set command but how setup my revisit conditions.

I should have Version 2.0 up later today! I still have to finish the planetinfo list.

Posted: Wed Dec 12, 2007 7:36 pm
by Roberto
But nevertheless, your correction was misplaced.
Er, no.
you'd have done better in nitpicking about the use of "didn't" and "haven't", to which I'd have no defenses...
Defen
ces, man! Defen
ces!

Posted: Thu Dec 13, 2007 12:38 pm
by Commander McLane
<finishing grammar nitpicking>
Cmdr. Maegil wrote:But nevertheless, your correction was misplaced. Woke is a proper past tense and it sounds better (or at least more cultured) than "waked"; you'd have done better in nitpicking about the use of "didn't" and "haven't", to which I'd have no defenses...
Actually, no. You had the choice of saying either "didn't we wake up" (past tense is in the "did", followed by an infinitive, which is "wake"; you would not say "I did
went home yesterday", but "I did
go home yesterday") or "haven't we woken up" (past participle). "Haven't we woke up" is completely impossible.
</end of grammar nitpicking, over and out>
Posted: Thu Dec 13, 2007 6:05 pm
by matt634
Version 2.0 is up on the Wiki!
-SecComs are now interactive with options to:
-Check the latest Navy News
-Buy Victory Bonds to support the war (benefits to patrons)
-And coming soon... signup for Reserve Navy Missions!
-Improved SecCom AI (now random shuttle launches)
-Improved MineSweeper AI (now respond to aggressors)
-Increased Thargoid vs Frigate ratio in interstellar space 3 to 1
-Relocated another SecCom in galaxy 3
WARNING!! I strongly caution against opening the included planetinfo.plist! While I'm not entirely sure of the risks associated, remember that scene from Raiders of the Lost Ark when the nazis opened the ark of the covenant... something like that.
A few teaser pics:

Posted: Thu Dec 13, 2007 6:56 pm
by Ark
Oh boy!!!!!
You guys create – update oxps with a faster rate than I can download them.
Bug with Oolite 1.70 & Galactic Navy 2.0 on my system
Posted: Fri Dec 14, 2007 12:10 pm
by Lestradae
-) see Testing & Bugs Forum
Posted: Tue Dec 18, 2007 11:37 am
by Commander McLane
Opening the planetinfo.plist (even against the author's advice

) it was easy to find out that it consistently uses
morethan as an operator in the conditions of the script_actions.
The correct operator, however, is
greaterthan (see
wiki). Therefore please simply replace all
morethan with
greaterthan.
That will be version 2.1, I guess.

Posted: Tue Dec 18, 2007 4:40 pm
by matt634
Excellent Work! I'm so glad you risked having your flesh melted off!
So, what you're saying is morethan is not equal to greaterthan

I'll do a quick update with the bug fix today. Interestingly, the morethan does work on my system (MacBook with Intel Core 2 running 10.4). What's more troublesome is that I copied "morethan" out of somebody else's script somewhere. I'm sure not clever enough to have come up with it on my own.
Posted: Tue Dec 18, 2007 5:02 pm
by another_commander
Hm, I think the problem has to be something else. Taken straight from the legacy script source code, scriptTestCondition method:
Code: Select all
else if (([comparisonString isEqual:@"greaterthan"])||([comparisonString isEqual:@"morethan"]))
comparator = COMPARISON_GREATERTHAN;
What the above means is that the
morethan operator should be recognizable and work just as well as
greaterthan.
Posted: Tue Dec 18, 2007 5:49 pm
by matt634
So morethan does equal greaterthan?