Replies: 1 comment
-
|
hi harris! hmmm, this one's hard for me to wrap the old brain around - but seeming to get the general idea:) all the way back from 83 always expected odd stuff in the game and with dec10 in general - that was a 'hand me down' setup in san marcos donated by austin (or least that's the legend/myth) and by no means 'top notch' hahaha. so basically have never really dug into details - will be super curious to see what others think!:) off topic - hi flavio are ya around? would love to learn more about where you and everyone else played 'back in the day'!:) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When scanning, the documentation says "SCAN defaults to a square scan range of ten sectors from
the present ship location", and for SRSCAN "Equivalent to SCAN, but with a default scan range of 7 sectors". Here is the rub: when set scan short is true, scan and srscan seemingly scans a different range of columns. For example (ship is in column 20):
set scan long
scan
Header is: 10 12 14 16 18 20 22 24 26 28 30
srscan
Header is: 13 15 17 19 21 23 25 27
this output seems to match the documentation.
Now:
set scan short
scan
Header is: 11 14 17 20 23 26 29
srscan
Header is: 14 17 20 23 26
I would have thought that the headers would be the same, just condensed (set out short doc: "Use 1 character symbols instead of 2").
So is this a bug, why does scan and srscan output a different range when set output short is true?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions