| 1 |
=head1 CFPlus Manual |
| 2 |
|
| 3 |
=head2 Features |
| 4 |
|
| 5 |
=over 4 |
| 6 |
|
| 7 |
=item Fullscreen Map |
| 8 |
|
| 9 |
PClient can uses a fullscreen map, which greatly enhances how much of the |
| 10 |
game world you can see. |
| 11 |
|
| 12 |
=item Persistent Map Cache (Crossfire+ only) |
| 13 |
|
| 14 |
PClient can persistently cache all map data it received from the |
| 15 |
server. This not only allows it to display an overview map, but also |
| 16 |
ensures that once-explored areas will be available the next time you want |
| 17 |
to explore more. |
| 18 |
|
| 19 |
=item Hardware acceleration |
| 20 |
|
| 21 |
Unlike most Crossfire clients, PClient take advantage of OpenGL hardware |
| 22 |
acceleration. Most modern graphics cards have difficulties with 2D |
| 23 |
acceleration, while 3D graphics is accelerated well. |
| 24 |
|
| 25 |
=item No arbitrary limits |
| 26 |
|
| 27 |
Unlike other Crossfire clients, pclient does not suffer from arbitrary |
| 28 |
limits (like a fixed amount of face numbers). There are still limits, but |
| 29 |
they are not arbitrarily low :) |
| 30 |
|
| 31 |
=back |
| 32 |
|
| 33 |
=head1 Usage |
| 34 |
|
| 35 |
=head2 The Map |
| 36 |
|
| 37 |
The map is always displayed in the background, behind all other windows and UI elements. |
| 38 |
|
| 39 |
#TODO# middle-click scrolls |
| 40 |
# |
| 41 |
# keys: |
| 42 |
# |
| 43 |
# a apply |
| 44 |
# keypad moves, kp_5 applies ranged attack to self |
| 45 |
|
| 46 |
Starting to type enters the I<completion mode>. In that mode, you can type |
| 47 |
abbreviations or commands and have them executed as soon as they match a |
| 48 |
valid command. This is best explained by a few examples: |
| 49 |
|
| 50 |
Typing B<climb> will display a list of commands with I<climb> in their |
| 51 |
name, such as I<ready_skill climbing> and I<use_skill climbing>. |
| 52 |
|
| 53 |
You can abbreviate commands by typing only the first character of every |
| 54 |
word (or even characters within the word - the client will try to make |
| 55 |
a good guess, as long as the characters are in order). For example, |
| 56 |
typing I<iwor> will likely select I<invoke word of recall>, while I<ccfo> |
| 57 |
will select I<cast create food>. Likewise, I<rscli> will likely select |
| 58 |
I<ready_skill climbing> and I<usl> will give you I<use_skill levitation>. |
| 59 |
|
| 60 |
You can enter space and other text as arguemnt to the command. For |
| 61 |
example, C<cfoo waybread> will expand to C<cast create food waybread>. |
| 62 |
|
| 63 |
=head2 The map overview |
| 64 |
|
| 65 |
#TODO# |
| 66 |
|
| 67 |
=head2 The Status area in the lower right corner |
| 68 |
|
| 69 |
#TODO# |
| 70 |
|
| 71 |
=head2 The I<Statistics>/I<Stats> window |
| 72 |
|
| 73 |
#TODO# |
| 74 |
|
| 75 |
=head1 FAQ |
| 76 |
|
| 77 |
=over 4 |
| 78 |
|
| 79 |
=item The client is very sluggish and slow, what can I do about this? |
| 80 |
|
| 81 |
Most likely, you don't have accelerated OpenGL support. Try to find a |
| 82 |
newer driver, or a driver from your hardware vendor, that features OpenGL |
| 83 |
support. |
| 84 |
|
| 85 |
If this is not an option, the following Setup options reduce the load and |
| 86 |
will likely make the client playable with software rendering (it will |
| 87 |
still be slow, though): |
| 88 |
|
| 89 |
=over 4 |
| 90 |
|
| 91 |
=item B<Video Mode> should be set as low as possible (e.g. 640x480) |
| 92 |
|
| 93 |
=item Enable B<Fast & Ugly> mode |
| 94 |
|
| 95 |
=item Disable B<Fog of War> |
| 96 |
|
| 97 |
=item Increase B<Map Scale> |
| 98 |
|
| 99 |
=back |
| 100 |
|
| 101 |
=back |
| 102 |
|
