stargates are not populated.....

[shanejfilomena]

in the shipping company orders i have based on the instruction to be sure they deliver to populated stations and not just any rock :

Code: Select all

; Get the list of all stations that we might visit
								(setq destList (sysFindObject gSource "TA:populated;F -occupation;"))

this works but the ships often go to stargates as well ( i added a "transfer point" guarded by the black market ID requirement to cover it up but it's a insane little buggy ).

this is going on in 1.01 and 1.05 : which are the versions I am testing Corporate Contracts in : at FIRST I thought it "good" because it shows the player the gates if they missed them or did not know where the other gate was, but now it's just annoying because I KNOW it is against the orders for the station and I am concerned about a shipping company revealing the gate to Huaramarca by this error.

Any ideas? like -uncharted; ?

[george moromisato]

in the shipping company orders i have based on the instruction to be sure they deliver to populated stations and not just any rock :

Code: Select all

; Get the list of all stations that we might visit
								(setq destList (sysFindObject gSource "TA:populated;F -occupation;"))

this works but the ships often go to stargates as well ( i added a "transfer point" guarded by the black market ID requirement to cover it up but it's a insane little buggy ).

this is going on in 1.01 and 1.05 : which are the versions I am testing Corporate Contracts in : at FIRST I thought it "good" because it shows the player the gates if they missed them or did not know where the other gate was, but now it's just annoying because I KNOW it is against the orders for the station and I am concerned about a shipping company revealing the gate to Huaramarca by this error.

Any ideas? like -uncharted; ?

I apologize. The criteria syntax is particularly convoluted (mostly because I've added so much to it over the years).

The syntax that you often see in the XML is:

Code: Select all

"T:populated;"

This T:something syntax is a completely equivalent to:

Code: Select all

"T    +populated;"

However, T:something works only with 'T'. It cannot be combined with other selectors. For instance:

Code: Select all

"AT:populated;"  <- this is correct; colon is after T
"TA:populated;"  <- INCORRECT: colon is after A

So your code should be changed to:

Code: Select all

; Get the list of all stations that we might visit
		(setq destList (sysFindObject gSource "TA +populated; F -occupation;"))

Moving forward I am trying to deprecate the "T:something" syntax in my code (since it is confusing). Instead I'll use the +something; syntax.

Good luck, and sorry for the confusion.

[shanejfilomena]

In other words: " no more shipping companies from Shane until the new code comes out "

However I have since used this for adding a screen and a treasure trove in the latest idea gone screwy : no shipping companies : but I extended the screen to dance several steps...one step is a big one ( about 1000 credits )....but I think I did well for a Space cadet