-
Notifications
You must be signed in to change notification settings - Fork 12
/
COW.DOC
1829 lines (1370 loc) · 68 KB
/
COW.DOC
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
0.0 Table of Contents
*******************************************************************************
* *
* General Documentation for the Client Of Win (COW) *
* *
* Comments, suggestions and bug reports to cow@netrek.org *
* *
* *
*******************************************************************************
Table of Contents
1.0 Overview
2.0 Acknowledgements
3.0 Features
3.1 Command Line Options
3.2 Pixmaps (Full Color COW)
3.3 Other features
4.0 Xtrekrc
4.1 Windows, fonts, cursors, and colors
4.2 Startup options
4.3 Combat options
4.4 Messaging options
4.5 Net options
4.6 Galactic/tactical map options
4.7 Keymap (and buttonmap) options
4.8 Playerlist options
5.0 Connection Types: UDP, TCP. Short packets.
6.0 Macros, RCD, RCM:
7.0 MetaServer Options
8.0 Compiling
9.0 Beeplite
1.0 Overview
This document describes the COW client, its capabilities, and the client's
features. COW started as the successor of the BRM client after release 3.
BRM started as a merger of the Berkeley client with Rick's Moo
client. Since then, all three clients have developed fairly independent of one
other. Familiarity with netrek is presumed throughout this document. Please
consult the newbie manual for information on the game itself.
COW has an expire function which insures that players obtain new copies
regularly. This alleviates the client's caretakers from having to support
ancient clients. Generally, a client will expire one year after its compile
date.
2.0 Acknowledgements
Many people have contributed to COW and many many others contributed
to its ancestor clients. Here is an undoubtedly incomplete list of credits
presented in no particular order. Where possible their typical netrek name is
provided in the hope that you will ogg them:
Scott Silvey
Kevin Smith
Rick Weinstein Videodrome
J. Mark Noworolski Passing Wind
Tedd Hadley pteroducktyl
Heiko Wengler Musashi
Andy McFadden ShadowSpawn
Chris Guthrie
Ed James
Eric Mehlhaff
Nick Trown Netherworld
Lars Bernhardsson lab
Sam Shen Buster
Jeff Nelson Miles Teg
Jeff Waller
Robert Kenney Zhi'Gau
Steve Sheldon Ceasar
Dave Gosselin Tom Servo
Kurt Siegl 007
Kevin Powell seurat
Alec Habig Entropy
Jonathan Shekter KillThemAll!
James Cameron
Michael Kellen
3.0 Features
The COW client has many features that make it stand out from earlier
clients. This section will attempt to describe all of its features, including
those that are common to all clients.
3.1 Command Line Options
This section will describe COW features that are selected from the command
line when the client is invoked. Selecting "-u" for usage or any invalid
option will provide a brief summary of this section (-help will work too).
3.1.1 SERVER SELECTION
The "-h server_address" option will allow the user to select a specific
server. The client will look to the .xtrekrc file for a default server should
this option be absent. Examples of server addresses would be 136.165.1.12 or
starbase.louisville.edu.
3.1.2 PORT SPECIFICATION
The "-p port_number" option will allow the user to select a specific port
address. An example of a port_number would be 1111, 2222, or 2592.
3.1.3 DEFAULTS FILE SPECIFICATION
The "-r defaultsfile" option will allow the user to select a defaults file
other than .xtrekrc. The defaults file contains all of the user selectable
defaults (please see Section 4.0 for more information on .xtrekrc). Using
this option, two users can run netrek from the same userid / account and still
have unique defaults files.
3.1.4 VERIFICATION OPTIONS
[deleted]
3.1.5 RECORD GAME OPTION
The "-f record_file" will record the game into record_file.
The "-F record_file" will play the recorded game from record_file.
3.1.6 METASERVER OPTION
The "-m" option will instruct the client to search the Meta Server at
metaserver.ecst.csuchico.edu, port 3521 and present the user with a list of
available servers. The user may then select the most desirable server
directly from the client.
Alternatively, the "-k" option may be used to show the "known servers",
using the same format as the Meta Server list. The client generates
a list of "known servers" after each call to the meta server but only if
the "metaCache" option is set in your .xtrekrc.
To find out about customising the meta-server, set the Chapter
"MetaServer Options", later in this document.
t
3.1.7 AUTOLOGIN OPTION
The "-A password" allows the client to automatically enter the specified
character password without having to prompt the user. This option is normally
used with the "-C character_name" option, which automatically enters the
character name. The "-C" option must be followed by a character name string.
3.1.8 NEAREST COLOR OPTION
The "-n" option allows the client to accept the "closest match" to the
colors requested for drawing. How good the match is is up to your windowing
software.
3.1.9 NO PIXMAPS OPTION
The "-b" option disables the use of color pixmaps by the client.
3.1.10 GHOST START
After a client dies, or even if you kill the client on purpose,
you can recover the game and continue playing. In fact the
server won't have any idea that anything but bad lag (called
a ghostbust) has occurred.
The benefits of this feature include the ability to change
displays, recompile code (if you happen to be a code hack),
or simply recover from a core dump.
In order to use it, you have to pay attention to two numbers
which are displayed when you connect to the server. A line
like this appears:
*** socket 11323, player 0 ***
This indicates which player slot you have been assigned, and
which socket number has been chosen as your ghostbust socket.
Now in order to restart, just do:
cow -G 0 -s 11323
The important options are -G followed by the player slot you
occupy, and -s followed by the ghostbust socket. Notice that
you don't even specify a server!
This feature may NOT work on all servers. Many server gods use
server code which is too old to support this feature. Also,
keep an eye out for small details that are off. It is NOT
logically possible to account for everything with this feature.
Such things as the motd are not resent by the server when you
connect, so you won't have that around anymore. Further, the
client won't know who it is even connected to (see above), thus
don't be shocked if the client claims you are connected to a
bogus server.
WARNING: Some servers have *very* short ghostbust timeout
periods. You must reconnect before this timeout expires or
your slot will be given to someone else, you won't be able
to reconnect. On most servers it is around 6 minutes long.
3.1.11 ESOTERIC OPTIONS
-c this will check server_port-1 and spew out
a list of all players currently playing on that server - not all
servers are intelligent enough to do this
-s (integer) passive port to use, generally only server gods would ever
use this option and even they can get by without it
-l (filename) file to log messages
-d (string of chars) display name
-H (string of chars) Gateway name
-P log packets: generally don't want to use this
-t (string of chars) title - the name of the window the client makes
-D debug mode
-v display version/expiration info and exit
-i ignore signals (SIGSEGV and SIGBUS)
3.2 Pixmaps (Full Color COW)
With the release of COW 3.00, dynamic color images are available. No
color images have been compiled into the client, so without the additional
files (described below) the client will behave as before.
3.2.1 Setup
The xpm files should be available at the same site from which you got
the client, in a file named pixmaps.tgz (PIXMAPS.ZIP for windows users).
>>> YOU MUST DOWNLOAD AND UNPACK THIS FILE TO USE THE COLOR FEATURES. <<<
It should create a subdirectory named "pixmaps" which should have several
(obviously named) subdirectories. There should be several XPM files in each
(except for Planets, which has a further subdirectory). UNIX users will see
that they are gzipped to save space. You do NOT need to ungzip them unless
you do not have gzip on your machine.
>>> DO NOT REARRANGE OR RENAME THESE FILES IF YOU WANT TO USE THEM. <<<
You need to add a line to your .xtrekrc telling the client where to look
for the pixmaps. If you do not, it will assume that they are in a subdirectory
of the directory you are in when you start the client. The option is called
"pixmapDir". Tilde and environment variables WILL NOT WORK. Relative paths
will only work if you always start netrek from the same directory.
You should be ready to rock and roll. Fire it up. You may see some
warnings about not being able to read some pixmaps. Some of the pixmaps
that the client looks for haven't been drawn yet. Feel free to make your
own set. OTOH, if you see any lines which read
"TYPE <type> PIXMAPS NOT AVAILABLE"
it means that none of a certain type of pixmap were found. Check to make sure
that the pixmaps are where you told it to look. If they are, and you are on
a UNIX system, you may not have gzip installed. Go get it from any GNU mirror
and either install it or use it to ungzip the XPM files.
3.2.2 Configuration
In addition to simply creating your own XPMs with a paint program, you
may want greater control over the pictures used. For example, you may find
the explosions are too pretty, and you are dying because you forgot to dodge.
The crude approach is to just remove that pixmap. The client will default back
to the standard bitmaps in this case.
The more elegant approach is to turn off just those pixmaps you don't
like and keep the rest. This also allows you to switch back and forth WITHOUT
having to exit and restart. So if the machine you are playing on is busy
today, you can turn off the pixmaps until things improve, then switch back to
full color without losing your 5 kills.
Pixmaps can be turned on or off in groups on the new "Pixmap Menu" in the
options window (shift-O). Each line in the window also corresponds to an
.xtrekrc resource which you can use to set the initial values. If one type
of pixmaps is not available, you will be unable to turn on that option.
resource name default description
indPix on \
fedPix on | Control whether or not the XPMs
romPix on | for the ships of a given team
kliPix on | should be used
oriPix on /
weaponPix on Torps and plasmatorps & their clouds
explosionPix on ship and starbase explosions
cloakPix on fade-in/-out and cloak icon
mapPix on Color Planet icons on galactic
(replaces the "colorgalactic" option)
backgroundPix on Background stars & genocide/gb images
(replaces the "babes" option)
ownerhalo off Draws a colored ring around each
planet on the galactic
as a convenience, the option "shipPix" may be used to control all of the
ship XPMs in one line.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ POWER USERS +
+ +
+ The MegaResource "pixFlags" can be used in your .xtrekrc +
+ to save a bit of typing. Simply bitwise OR together the +
+ things you want turned off: +
+ +
+ 0x0001 IND pixmaps +
+ 0x0002 FED pixmaps +
+ 0x0004 ROM pixmaps +
+ 0x0008 KLI pixmaps +
+ 0x0010 ORI pixmaps +
+ +
+ 0x0020 Weapons +
+ 0x0040 Explosions +
+ 0x0080 Cloaking +
+ 0x0100 Galactic Map Planet Icons +
+ +
+ 0x0400 Backgrounds +
+ +
+ 0x1000 Halos +
+ +
+ so, for exaple, no halos and no explosions would be +
+ specified as: (0x1040=4160) +
+ +
+ pixFlags: 4160 +
+ +
+ +
+ (Note that this OVERRIDES all the other resources) +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
If you hate them all, you can either set the "pixmapDir" to "None" or
start the client with the -b (bitmap only) command line option. Then go ahead
and delete all of the XPMS. Go ahead. We don't mind at all. It's not like
we put any WORK into this ... :,-(
3.2.3 Babes/M31 and Generalized Backgrounds
Gone. You can put up any picture you like when you GENO, GB, or just
enter or hit shift-K. Just specify the genocide.xpm, ghostbust.xpm and/or
hello.xpm. It's really none of my business what you look at in your off time.
Absolutely no picture will be shown if you do not have an XPM in the
specified place. It didn't belong in the client in the first place.
DEAL WITH IT.
And BTW, the ' key (quote) has the default action of retiling your local
and galactic windows with the normal background (either black or your specified
pixmap) to repair the damage done by the other possible pix.
3.2.4 AGRI pixmaps and FEATURE_PACKETS
The client shows a different pixmap for AGRI planets than all others.
This was announced, voted on and overwhelmingly adopted (80%+ in favor). But
JUST IN CASE, this option can be disabled at the server by use of the
feature packet "AGRI_PIXMAP".
Users can choose to remove the AGRI.xpm file. The client will default
to using the regular planet pixmap if it is missing.
3.3 Other features
*** Hockey Lines
Due to popular demand, hockey lines have been added.
For those of you who want to see a hockey rink on the tactical,
just use the features menu (shift-O) and toggle them on.
You get:
Blue lines (blue)
Center line (red)
Side lines, i.e. the rink edges (grey)
Goal lines (red)
Goal boxes (the color of the team)
They are a little awkward at first, but once you get used to them,
you'll wonder how you lived without them.
Since this is a first pass, I'm looking for more input on what
would make them better. Here are some of my comments:
1) Lines are hardcoded into the software. They should be
based upon planet location, so the hockey gods can move the
planets around.
2) You either have them all or none. Perhaps the set of
desired lines should be configurable from the xtrekrc. Also,
you cannot change the colors.
3) Lines on the galactic would look pretty
If you have any comments, mail them to kantner@hot.caltech.edu
*** Shell escape tool
You may execute any Unix shell command within the client. Read your mail
now within the client. To do so, just send a message to the destination
"!" and you get a shell prompt. Enter the command and its output will
be displayed in the tools window. Works also with macros to "!".
You may disable it in the .xtrekrc for security reasons with shellTools: off
CAUTION: The client will be blocked for the time the command is executed.
Also some programs suspend the client if it is started in the background.
*** Fast quit
Hitting 'q' will quit the client without ever going back to the
team selection window, the normal 'Q' still goes back to the team
selection window.
*** Reread defaults file
You can reread your netrek default file by hitting '&', it is also
possible to enter a new default file name at any time by sending
a message to 'M' which contains the file name.
*** Galactic rotation
For those who like to fight with some specific orientation, the
galaxy is now rotate-able. This can be done in the options window.
This works now also with short packages.
*** Gateway
Lots of cool gateway code in this client, unfortunately I don't
use nor do I know what it does other than get past firewalls.
*** Observer support
Many servers allow you to *observe* a game instead of playing, sort of
like watching football. COW supports this feature. Currently in order
to be an observer, all you have to do is connect to the observer port
for a server. A good guess at the observer ports for a pickup server is
2593; for INL, 4000 and 5000.
*** Lagmeter
This is pretty pointless: a continuously updated bar graph of how bad
your lag is. Perfect for the whiny player who needs an excuse. ;)
This can be turned on with the '\' key, from the options menu, or from
the .xtrekrc. (lagmeter.parent, lagmeter.mapped, lagmeter.geometry)
Requres netstats to be on.
*** Pingstats
In a similar vein, the pingstats window can be turned on from the .xtrekrc,
the options menu, or the key ','.
*** The Pig call
COW supports sending five spaces to a player as the de facto method of
requesting info on the client. (So called because it was used by the Pig
borg, AFAIK.) For instance:
COW 3.00pl0, linux, 03/03/98, RMCSE365AmTsr
The letters in the fourth field indicate which #ifdefs were specified
at compile time. Possibilities are:
M: Macros
D: Debugging information
C: Corrupted packet handling
S: Short packets
E%d: Expiration date, in days after compilation
A: Stat window contains a slider showing armies carried
(does not affect the newdashboard code)
m: Metaserver support
T: "Various tools, like shell escape, ..."
s: Sound
r: RCD support
*** Improved help window:
Basically, this was done to show what keys were
actually mapped to what functions. Every key function has a line in
the help window. Here's a sample line:
s gb Toggle shields
||\\_ The 'b' key has been mapped to toggle shields
|| \_ The 'g' key has also been mapped to toggle shields
|\____This space is always there, as a separator.
\_____This is the default key for this function, and the hook that you
use when defining things to this function. I.e. to set the 'g'
and 'b' mappings mentioned here, you'd have to put 'gsbs' in
your .xtrekrc or your keymap options.
NOTE: This character will appear here, even if it is mapped
to something else.
*** Message-Warp: The non-warp version.
Hit the 'm' key and start typing. Your cursor changes to the
'text' cursor, and all keystrokes go to the message window. Sending
the mesage or the ESC key ends this. Again, the mouse pointer is not
moved.
*** Documentation Window
The documentation window is used to view documentation while actually
playing. In order to do this you must either have the COW.DOC file in
the directory you are running the client from or you must set the
documentation resource value to the full path to the file with the
documentation. Control-y brings this window up. Also available via
shift-O option menu under "info."
The 'f', 'b' keys scroll forward and back by 28 lines, like the motd
window. While 'F' and 'B' keys scroll by 4 lines.
In .xtrekrc:
documentation: /home/kensho/powell/misc/netrek/brm3002/myCOW.DOC
*** Xtrekrc File Window
The xtrekrc file window is used to view your current xtrekrc file online.
It is currently very stupid in that if you used the command line
option '-r' to specify your xtrekrc file, this viewer will not find
it (it's currently hardwired for $HOME/.xtrekrc:( Control-X (that
is control-shift-x) will bring up this window, or shift-O under "info."
The 'f', 'b' keys scroll forward and back by 28 lines, like the motd
window. While 'F' and 'B' keys scroll by 4 lines.
*** Auto torp aiming and dodge
Get outa here...
***************************************************************
4.0 Xtrekrc:
***************************************************************
COW looks for a .xtrekrc file in your home directory. Alternatively
this file may be called home, and it may be in whatever directory
the client is executed from.
A file called "SAMPLE.xtrekrc" should have been included with this
client. Below is an attempt to explain the many, many options you
can include in a .xtrekrc file. Some of this was borrowed from
various other documentation such as MOO documentation.
For other options, see MACROs and Receiver Configurable Distress Calls.
4.1 Windows, fonts, and colors
rank.mapped: (on/off)
rank.parent: (window name) ie root, review_all, netrek, etc
rank.geometry: (geometry specification) ie 80x26+554+624
Every window may have these three defaults set for it.
Some windows are resizeable, others are not.
font: fixed
bigfont: lucidasans-24
italicfont: -schumacher-clean-medium-i-normal--10-*-*-*-c-80-iso8859-1
boldfont: -schumacher-clean-bold-r-normal--10-100-*-*-c-60-iso8859-1
Specifies which fonts you want to use,
not sure that all of these are still used in COW
The personalized cursor extensions allows the user to specify their own
cursors for the map, local, text, menus and info list windows.
localCursorDef: /usr/me/.local.xbm
mapCursorDef: /usr/me/.map.xbm
infoCursorDef: /usr/me/.info.xbm
textCursorDef: /usr/me/.text.xbm # the mask would be called /usr/me/.text.xbm.mask
arrowCursorDef: /usr/me/.arrow.xbm
For infoCursorDef, textCursorDef, arrowCursorDef an optional mask may
be specified. To specify a mask, first create your new cursor, say called
mycursor, then create the mask and call it mycursor.mask. They both need to
be on the same path. Cursor and mask *must* be the same size, if not the
cursor cannot be used (why anybody would want to do this makes no sense,
but...:)
color.white: white
color.black: black
color.red: #ffa0ff
color.green: green
color.yellow: yellow
color.cyan: cyan
color.light grey: light grey
Specify what colors should be used by the client.
This is generic X color specification (right?).
All the possible left hand sides are listed I think.
color.Ind: light grey
color.Fed: yellow
color.Rom: tomato
color.Kli: green2
color.Ori: light steel blue
Race Colors may be set separately.
4.2 Startup options
name: (string of chars) default name
password: (string of chars) default password; if both name and password
are included in your .xtrekrc, COW will attempt to do
an autologin for you.
server: bronco.ece.cmu.edu
default server that is called when no -h argument is
specified. Leave this blank to have cow call the
metaserver by default.
port: 2596
default port that gets called. The compiled default is 2592.
server.rio: riovista.berkeley.edu
Allows you to specify a server abbreviation. Thus instead of
using "-h riovista.berkeley.edu" you now use only "-h rio"
port.rio: 4566
default port that gets called for the server abbreviation.
showmotd: (on/off) display motd if in wait queue
autoquit: (integer) length of time to wait on team selection screen
before Auto-quit exits for you.
ignoreSignals: (on/off) ignore SIGSEGV and SIGBUS. COW will try to reset
the game so you can continue.
4.3 Combat options
warnShields: (on/off) In color, you can have your shield be color of your
alert status (red, yellow, green)
varyShields: (on/off) Shield color and bitmap depends on shield strength.
varyHull: (on/off) graphical indication of your hull condition. Kinda
like varyShields. When varyHull is on your ship looks like it
has small spikes sticking out of the shields, each spike
representing 12.5% of your hull strength.
cloakChars: (string of one or two chars) what to use for cloakers on
galactic instead of '??'.
enemyPhasers: (integer 0-10) enemy phasers thickness at starting point.
phaserShrink: (integer 0-16) Don't draw the first "phaserShrink"/16th of
your phaser. This makes it easier to see incomming torps.
theirPhaserShrink: (integer 0-16) "phaserShrink" for other players' ships.
shrinkPhaserOnMiss: (on/off) Use "phaserShrink" and "theirPhaserShrink" even
if a phaser misses.
highlightFriendlyPhasers: (on/off) phaser hits by your team are solid white
(instead of the default "rainbow" a la COW-lite.
showtractorpressor: (on/off) toggle showing tractor/pressor beams
continueTractors: (on/off) off = turns off the visible t/p after 2 updates.
showstats: (on/off) show stats window
4.4 Messaging options
newDistress: (on/off) right-justified distress call or not, default value
is to right-justify (on)
reportkills: (on/off) display kill messages or ignore these
censorMessages: (on/off) attempts to remove profanity from messages sent.
They'll look like this: "F0->FED @$%# you twink"
logging: (on/off) displays messages to stdout if set.
logfile: (filename) alternatively saves messages to a text file
PhaserMsg: [0, 1, 2, 3, 4, 5]
0 = Don't log phaser hits
1 = Log phasers on all window
2 = Log phasers on team window
3 = Log phasers on indiv window
4 = Log phasers on kill window
5 = Log phasers on review window
the additional phaser window is controlled just like the other
review windows. e.g.:
review_phaser.mapped: on
review_phaser.parent: netrek
review_phaser.geometry: 81x2+0+555
4.5 Net options
netstats: (on/off) collect network statistics for measuring lag
netstatfreq: (integer) how often to update the network statistics
tryShort: (on/off) default setting for whether to use short packets.
tryUdp: (on/off) try to automatically connect with UDP
udpDebug: 0 = OFF 1 = ON (conect msgs only) 2 = ON (verbose output)
udpClientSend: 0 = TCP only, 1 = simple UDP
2 = enforced UDP--"state", including the following flags:
SPEED
DIRECTION
SHIELD (up or down)
ORBIT
REPAIR
CLOAK
BOMB
DOCKingPERMission
PLAYerLOCK and PLANetLOCK
BEAMing of armies
3 = enforced UDP--"state & weapons" all of the above plus
PHASER commands
PLASMA commands
Note that TORP commands are not included.
udpClientRecv: 0 = TCP, 1 = simple, 2 = fat,
3 = double (not currently supported)
udpSequenceChk: ?
4.6 Galactic/tactical map options
useTNGBitmaps: (on/off) Different bitmaps for fed. Not the new pixmaps.
ROMVLVS: (on/off) Replacement for dorky Rom CA bitmap. Not a pixmap.
showIND: (on/off) mark independent planets with a X drawn over it.
newPlanetBitmaps: removed. Use showlocal/showgalactic instead.
whichNewPlanetBitmaps: ditto.
newDashboard: (integer 0-3) Uses sliding bars instead of numbers to display
speed, shield/hull status, etc, on the dashboard. 1 is
'vanilla'; just like the old stat graph. When set at 2,
besides defaulting to green, displays how much hull/shield
you have LEFT, not how much you have lost (i.e. this is an
optimistic dashboard, it sees the cup as half full ;). At 3,
uses triangle sliders AND numbers.
keepInfo: (integer) number of updates to keep info windows on the
screen before automatically removing them
extraAlertBorder: Draws border in internal netrek windows, as well
as external ones (which get ignored in X11 with window-managers)
forcemono: if on, the client windows are set to be monochrome
redrawDelay: if >0 synchron screen refresh every n/10 sec
(useful for slow X-terms and high lag).
showgalactic: 0 = nothing, 1 = ownership, 2 = standard resources,
3 = MOO/ZZ resources, 4 = rabbit ear resources
Determines what kind of information will be shown on planets
displayed on the galactic. With option 2, the planet bitmap
has symbolic icons for armies > 4, repair, and fuel resources.
With option 3, the planet has a dot in its center to represent
fuel and four tickmarks in the corners to represent repair.
With option 4, an ear on the left indicates repair and an
ear on the right fuel.
showlocal: 0 = nothing, 1 = ownership, 2 = standard resources,
3 = MOO/ZZ resources, 4 = rabbit ear resources
Determines what kind of information will be shown on planets
displayed on the local map.
showLock: 0 = none, 1 = galactic, 2 = local, 3 = both
Where to display the locked-on triangle.
showplanetnames: (on/off) turn on planet names by default.
colorgalactic: Use color pixmaps instead of bitmaps on galactic.
(Obsolete -- see section 3.2.2)
showstars: Use starry background on galactic map.
(Obsolete -- see section 3.2.2)
Color pixmap controls. (See section 3.2.2)
resource-- indPix: (on/off) default on
resource-- fedPix: (on/off) default on
resource-- romPix: (on/off) default on
resource-- kliPix: (on/off) default on
resource-- oriPix: (on/off) default on
resource-- weaponPix: (on/off) default on
resource-- ex:plosionPix (on/off) default on
resource-- cloakPix: (on/off) default on
resource-- mapPix: (on/off) default on
resource-- backgroundPix: (on/off) default on
resource-- pixFlags: (int) default 0 (== all on)
ownerhalo: (on/off) default off
Draw a circle around the planet pixmap in the color of the
owning team. (pixmaps only)
4.7 Keymap (and mouse) options
keymap: (string of chars) remaps the keyboard, syntax is simply the
key to map onto, followed by the key to map, repeated.
Thus to map the "fire torps" key 't' onto 'f', use
keymap: ft
(See also the sections on control keymaps and ship
dependent keymaps below.)
ignoreCaps: (on/off) ignore the Capslock key.
buttonmap: map the mouse buttons to something else.
i.e. the default mapping is:
1t2p3k
shiftedMouse: (on/off)
The shift and control keys can be used to modify the default function
assigned to a button. The shift key acts as a switch which brings an
alternate mapping to the mouse buttons. In a similar way control and
shift + control act to switch mappings again.
Breakdown of values:
Normal buttons 1, 2, 3,
<shift + button 1, 2, or 3> maps to 4, 5, 6,
<control + button 1, 2, or 3> maps to 7, 8, 9,
<shift + control + button 1, 2, or 3> maps to a, b, and c.
This remaps all the possible mouse buttons:
buttonmap: 1t2p3k4c5s6y7E8z9xaFbdcD
mouseAsShift: (on/off) Not to be confused with "shiftedMouse." ;)
Makes the mouse buttons 1-3 act like shift keys. Each button
"shifts" or causes a new set of key mappings to come into
effect: Instead of the keyboard remapping the mouse, the
mouse now remaps the keyboard. Each key on the keyboard now
has several possible mappings. Use the b[123]keymap
option to specify commands. For example, to have the 'a'
key fire a torpedo while button1 is pressed, and a phaser
while button2 is pressed, add the lines:
b1keymap: at
b2keymap: ap
continuousMouse: (on/off) allows you to cause multiple commands to be issued
to the server when dragging the mouse with a button down.
For instance you can drag the mouse while pressing button 3
(which defaults to set_course). Saves on button wear and
tear. ;)
4.7.1 Ship dependent keymaps, buttonmaps and .xtrekrc files
You can add one of: sc, dd, ca, bb, as, sb, ga, att, default to the
following default options to override them based on ship type:
rcfile-??: ship specific .xtrekrc file,
keymap-??: ship dependent keymap,
ckeymap-??: ship dependent CTRL keymap,
buttonmap-??: ship dependent buttonmap.
It will automatically reload the specified defaults if you change the
shiptype. If a ship-specific option is not specified, the default
option is used for that ship. For e.g., keymap-sc: will be used
instead of keymap: whenever you switch to an SC.
Used well, this is a very powerful feature. For instance, you might
bind a key to your prefered cruising speed, with a different speed for
each ship type.
Here's part of my keymap as an example.
# default: q = warp 2, w = 1/2 maxwarp, e = maxwarp
ckeymap: q2w#e%
# override some of the above, based on ship type
ckeymap-ca: w4
ckeymap-bb: w3
ckeymap-sb: q1w2
4.7.2 Control keymaps
Control keymaps (ckeymap) handle the remapping of keys in an
analoguous manner to the normal keymap (keymap). The control keymap
also allows the user to map both *upper* and *lower* case letters keys
when pressed with the control key. This means that ^u and ^U are
*different* keys when it come to mapping them.
Any combination of normal keys and control keys can be mapped to one
another. In other words, you can map from control key to control key,
control key to normal key, normal key to normal key, and normal key
to control key.
New format for ckeymap is:
c = any printable ascii character.
^ = introduce control mapping (the key '^' not control + key.)
Each entry is a pair, like:
cc # regular format
c^c # regular->control
^cc # control->regular
^c^c # control->control
Example ckeymap:
ckeymap: ^a%r^b^m^ca%d5 tfDFf^^E
Special case:
The '^' must be mapped with a double ^ ("^^") in either the bound or
binding key position.
Notes:
* If you experience difficulties (you shouldn't) you might wish to use
a normal keymap and a new ckeymap in combination. Both are read in,
the keymap first then the ckeymap. This means that if a key is
defined in both the keymap and ckeymap, the ckeymap's definition
will be the one used.
* If you wish to use ckeymaps in conjunction with keymaps based on
ship type (keymap-??, etc.), note that ckeymap still overrides
keymap-??. For e.g., if you define a key in ckeymap and in
keymap-bb, the ckeymap binding hides the other binding. You should
use ckeymap-bb instead.
* Since ckeymaps are a superset of keymaps, you might consider using
ckeymaps in all situations where you would use keymaps. This will
make things a lot simpler for you. (But keep in mind that `^' has a
special meaning in ckeymaps!)
Analogously, control keys may be used for buttonmap, singleMacro and
all macro and RCD definitions.
4.8 Playerlist options
newPlist: (on/off) new playerlist, instead of total kills, deaths
offense and defense it shows login and stats (off+bomb+planet).
Provided for backwards compatibility; use playerListStyle
instead.
sortPlayers: (on/off) Sort the playerlist with the enemy team players
first, then your team and then the neutral players.
sortMyTeamFirst: (on/off) Modifies "sortPlayers" so that your team is sorted
immediately before the enemy teams.
partitionPlist: Add blank lines to a sorted player list to separate the
different teams. This is useful in mono where the teams
can not be distinguished by their color.
playerListStyle: (0-4) The style for the player list. The options are:
(0) Custom player list as defined by the
playerlist variable above,
(1) Old player list,
(2) Traditional COW player list,
(3) Kill watch player list,
(4) BRMH Player list.
If "playerListStyle" is set, newPlist is ignored.
Use the options menu (shift-O) to try the different styles.
If no options are specified, defaults to (1).
playerlist: (string) The layout for the player list. What it allows
you to do is specify which columns of the player list you want to show
and in what order. The following is a table of the available columns.
Spc Let Name Header
--- --- -------------------- -------------------
3 'n' Ship Number " No"
3 'T' Ship Type " Ty"
11 'R' Rank " Rank "
17 'N' Name " Name "
6 'K' Kills " Kills"
17 'l' Login Name " Login "
6 'O' Offense " Offse"
6 'W' Wins " Wins"
6 'D' Defense " Defse"
6 'L' Losses " Loss"
6 'S' Total Rating (stats) " Stats"
6 'r' Ratio " Ratio"
8 'd' Damage Inflicted(DI) " DI"
1 ' ' White Space " "
options available when compiled with PLIST1
6 'B' Bombing " Bmbng"
6 'b' Armies Bombed " Bmbed"
6 'P' Planets " Plnts"
6 'p' Planets Taken " Plnts"
17 'M' Display/Host Machine " Host Machine "
7 'H' Hours Played " Hours "
6 'k' Max Kills " Max K"
6 'V' Kills per Hour " KPH"
6 'v' Deaths per Hour " DPH"
options available when compiled with PLIST2
9 'w' War staus " War Stat"
3 's' Speed " Sp"
So for example if you just wanted to see names and rank you'd add this
line to your .xtrekrc:
playerlist: NR
The styles defined by "playerListStyle" are
1: Old style = "nTRNKWLr O D d "
2: COW style = "nTR N K lrSd"
3: Kill watch style = "nTK RNlr Sd"
4: BRMH style = "nTR N K l M"
In order for this mod to be in effect you must compile with PLIST
defined. The things shown after PLIST1 are only available if you
have PLIST1 defined, the same goes for the things after PLIST2, but
you must have PLIST defined or neither of these will do anything.
NOTE FROM SOURCE KEEPER:
PLIST2 is not active in COW currently. Some players feel that placing
speed on the playerlist gives a strategic advantage.
NOTE ON SB STATS :
On servers which support the SBHOURS .feature, you will see slightly
different things when you info a SB, or show the SB player on the
playerlist. The usual offense and defense lines are replaced with SB