The CN9, Abort display on keys, setting allows for either space or All Keys. I have noticed that some scripts will not run on one setting, but will on the other. Since this seems to be used to "abort display" I was wondering what the different settings might do other than that. K, this is somewhat of a script question (or how it affects scripts), but it is a setting in Twars that I do not fully understand.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

quote:Originally posted by Promethius

The CN9, Abort display on keys, setting allows for either space or All Keys. I have noticed that some scripts will not run on one setting, but will on the other. Since this seems to be used to "abort display" I was wondering what the different settings might do other than that. K, this is somewhat of a script question (or how it affects scripts), but it is a setting in Twars that I do not fully understand.



It depends on how poorly the script is written to be honest.. Or probably more to say it depends on the level that the script was written.

CN9 supported scripts are easy to make because when you halt on all keys then there are key lines that are not deleted. Some things still cant be check'd but MOST things can.

Other things that can booger scripts -
Psy Probe
Planet Scanner
TwarpDrive
NoTwarpDrive
More than 1 planet in sector
Type of Scanner (none/Dens/Holo)
CN2 (animation display err I think)
and err .. If I remember these correctly
CNA - Compact/Long msg's
CNB - Screen Pauses
CN1 (ansi on/off).. <-- scripts should still work with this BUT it might not.. This could be for several reasons and some of them would be verry good. Monitoring for the correct escape ansi color sequences to prevent spoofing for example.. Works great but it halts the script when U turn color off. Also when color is off you get Long msg's by default and a few other differences..

Is that what you wanted to know?

With the 'all keys', most output during scripts is eliminated. If a script not designed for all keys needs a certain prompt, but 'all keys' aborted the prompt's output, the script will hang.

not just scripts but swath macro's will hang too. the macro's I use to furb when using swath will only work with cn9

If you leave CN9 set to SPACE, then you can build blank spaces into your scripts and / or macro's to achieve the same speed results as CN9 ALL KEYS. The same text can be aborted when absolute speed is needed but you can also have the script selectively wait for the information you want.

Lewd, there is probably a pause prompt that is getting skipped by your ALL KEYS setting. You should be able to have the same macro work for both settings if you add in either spaces or ^M's in the proper places.

A quick point to clarify something RammaR said. While spaces and CN9 being set to Space can do the same as CN9 set to All Keys, you need to check the server settings. I have seen some settings with Max Key Strokes of 4. So if you were to send a long string with spaces, it can really slow down execution. For example, if you were to send a string of 30 characters, and 8 were spaces to abort displays, with only 4 characters per second, you just added 2 seconds to your line. CN9 settings are really up to the scripters taste in game. I usually never use CN9, but I know some people do.

Hope that is some help,

Jhereg

hmm, being a non-scripter and liking to know wtf i am aborting, i use cn9 space almost religiously (as when i use cn9, **** happens and i die) heh, however u bring up a point of max commands.. hmm, i guess i will have to change my ways.

Slim

Are you sure it counts a space as a command? I wouldn't have thought it did, but I've never tested it. The settings is max commands/cycle, not max characters/cycle. For example, typing 9999 figs to send takes the same time as 10000, because the command is the figs to send, not each character in the number.

I dont use Zoc so this reply might be incorrect. I think that Zoc does not read spacebar asc(032) as a "whitespace" and actually uses it as a transmitted character.

quote:Originally posted by Harley Nuss (teamEIS)

Are you sure it counts a space as a command? I wouldn't have thought it did, but I've never tested it. The settings is max commands/cycle, not max characters/cycle. For example, typing 9999 figs to send takes the same time as 10000, because the command is the figs to send, not each character in the number.

ooo, kemp shows us the light (as usual) ok, someone get on testing

Slim

quote:Originally posted by Kavanagh

I dont use Zoc so this reply might be incorrect. I think that Zoc does not read spacebar asc(032) as a "whitespace" and actually uses it as a transmitted character.

quote:Originally posted by Harley Nuss (teamEIS)

Are you sure it counts a space as a command? I wouldn't have thought it did, but I've never tested it. The settings is max commands/cycle, not max characters/cycle. For example, typing 9999 figs to send takes the same time as 10000, because the command is the figs to send, not each character in the number.



What U smoking Kav..
We are talking about what the TWGS Reads..
Max Commands/Cycle = an issued command
Example
Making an announcement with 200 chars counts as 3 commands
vs attacking 50 times (spot 1) Ay1(^M) (that's 200 chars) would mean 150 commands