diff --git a/.gitignore b/.gitignore index 0266c39f6fc..59f38c9b4ed 100644 --- a/.gitignore +++ b/.gitignore @@ -91,6 +91,10 @@ win32/__BUILD_CONFIG.USER /doc/quickstartguide.html /doc/quickstartguide.pdf /doc/warzone2100.6 +/doc/events.tex +/doc/functions.tex +/doc/globals.tex +/doc/objects.tex # Generated executables: /build_tools/autorevision/autorevision diff --git a/macosx/Resources/.gitignore b/macosx/Resources/.gitignore new file mode 100644 index 00000000000..13f0a162b72 --- /dev/null +++ b/macosx/Resources/.gitignore @@ -0,0 +1 @@ +!*.pdf diff --git a/macosx/Resources/WarzoneHelp/WarzoneHelp.helpindex b/macosx/Resources/WarzoneHelp/WarzoneHelp.helpindex new file mode 100644 index 00000000000..1b9fd837460 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/WarzoneHelp.helpindex differ diff --git a/macosx/Resources/WarzoneHelp/ar01s01.html b/macosx/Resources/WarzoneHelp/ar01s01.html new file mode 100644 index 00000000000..2969a0477c3 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s01.html @@ -0,0 +1,9 @@ + + +1. Introduction

1. Introduction

This guide will help you get started playing Warzone 2100.

The Warzone 2100 Project has its website at URL +http://wz2100.net.

If you want to talk to other Warzone 2100 players, visit the forum at +URL http://forums.wz2100.net

Or you can fire up an IRC client and connect to the channels #warzone2100 and +#warzone2100-games on the Freenode network.

If you’re interested in developing Warzone 2100, the Project is always looking +for help. Go to URL http://developer.wz2100.net

If you want more information about Warzone 2100, including mod information, +individual component statistics, and more, go to URL +http://guide.wz2100.net

Enjoy Warzone 2100!

images/logo.png
diff --git a/macosx/Resources/WarzoneHelp/ar01s02.html b/macosx/Resources/WarzoneHelp/ar01s02.html new file mode 100644 index 00000000000..970a25cdea5 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s02.html @@ -0,0 +1,16 @@ + + +2. Interface

2. Interface

The interface can be turned on or off with Tab.

images/interface.jpg

diff --git a/macosx/Resources/WarzoneHelp/ar01s03.html b/macosx/Resources/WarzoneHelp/ar01s03.html new file mode 100644 index 00000000000..a01cc9f123c --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s03.html @@ -0,0 +1,24 @@ + + +3. Controlling the Camera

3. Controlling the Camera

What is the Camera? When Warzone was released in 1999, it was one of the first real-time strategy +games to be in 3D. Now, most real-time strategies are in 3D, but, if you’re not +used to the new trend, let us help you along.

Basic Controls

Advanced Controls

diff --git a/macosx/Resources/WarzoneHelp/ar01s04.html b/macosx/Resources/WarzoneHelp/ar01s04.html new file mode 100644 index 00000000000..c1b3253aecf --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s04.html @@ -0,0 +1,37 @@ + + +4. Minimap

4. Minimap

The minimap is a very useful tool on the Warzone battlefield. It helps you keep +track of your units and structures, your opponents units and structures (within +range), and the map itself. Orders can be issued over the minimap, and it can +be used to jump to part of the map very quickly.

The minimap is given after you build a Command Center.

images/minimap.jpg

Controls

diff --git a/macosx/Resources/WarzoneHelp/ar01s05.html b/macosx/Resources/WarzoneHelp/ar01s05.html new file mode 100644 index 00000000000..2072d289b29 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s05.html @@ -0,0 +1,21 @@ + + +5. Power

5. Power

images/powerbar.jpg

The power bar

images/oilresource.jpg

A spare oil resource, and a derrick hard at work

In real life, money is power, but in Warzone, power is money. You spend power +to build structures, manufacture units, and research upgrades/new technology.

5.1. Getting Power

So how do you get power? Power is generated by Oil Derricks. However, you must +have at least one Power Generator for every four Oil Derricks.

Oil derricks must be built on oil resources, but the generator can be anywhere +on the map. Keep in mind that additional generators beyond one for every four +derricks will provide no benefit. Also note that building heaps of power +generators won’t do anything at all until you have at least one oil derrick for +each.

5.2. Pricing

Icons in the Manufacture, Build, and Research menus will have yellow bars in +them representing their price:

images/cheapweapon.png Inexpensive weapon

images/expensiveweapon.png Expensive weapon

When you place your mouse over an icon, the power bar will have a green +section, representing its price. If you cannot afford it, the power bar will +instead turn red.

The amount of power you have is shown on the very left of the power bar. If you +place your mouse over an icon, if you have enough power to get it, the number +will show the amount of power it will cost. If you can’t afford it, the number +will show the amount of power you need to be able to afford it.

Power is drawn as soon as the icon is clicked. Providing you have sufficient +power for the activity, the initial progress bar fills quickly with green +(slower with more costly actions) and the construction or research begins. A +yellow progress bar then charts the progress achieved by the current activity.

5.3. Upgrades

images/powerupgrade.png

Power Generators can have a Power Module built on top of them to squeeze out +more power. Power Modules need to be researched before you can build them. +There are also several researchable upgrades available which increase the +amount of power you receive.

diff --git a/macosx/Resources/WarzoneHelp/ar01s06.html b/macosx/Resources/WarzoneHelp/ar01s06.html new file mode 100644 index 00000000000..e22f1146a55 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s06.html @@ -0,0 +1,45 @@ + + +6. Ordering Units

6. Ordering Units

6.1. Using Units

Gotten used to the interface? Okay, well, time to actually use our units.

Selecting and moving units

To select a unit or cyborg, left click on it. Multiple units can be selected by +clicking and dragging, and encasing the units in the drawn square, or by +holding down Ctrl or Shift and clicking on multiple units.

To move selected units, left click on the terrain of the map. This can also be +done over black areas of the map to explore the area. To attack an enemy unit, +left click on it. You can deselect a unit (or a group of units) with a +right-click.

Queuing and waypoints

You can set a path with waypoints, which units will visit each waypoint in +order. You can also select a queue of enemies for units to attack. Hold Shift +or Ctrl while selecting units or clicking places to move.

This also works for queuing construction of Oil Derricks and/or structures in a +chain - hold the key down while building the structures one by one, then, when +building the final structure, release the key.

Groups of Units

To make groups of units, select the units you want and press Ctrl+[number] to +make a group. A group of units will have a number next to it. To select a group +of units you have made, press [number]. Groups can also be selected by +double-clicking a unit in a group. To center the camera on a group, press the +[number] twice.

Defending

Click a friendly structure or truck with weapon units selected (the cursor will +be a shield) and the units will move to guard it.

6.2. Unit orders menu

images/unitordersmenu.jpg

Right-click on a unit (or select a unit and hit NUM0 on the numeric keypad), +and a unit orders menu will appear above the command panel. This contains +options to configure a unit’s behaviour.

Right-clicking on a factory will customize the orders of all future units that +that factory produces.

Attack range

images/attackrange.jpg

Optimum Range: Fires at most accurate range +(default)

+

Short Range: Moves to short range and attacks

+

Long Range: Attacks at long range

Retreat threshold

images/retreatthreshold.jpg

Do or Die: Your unit will not retreat +unless ordered to. (default)

+

Retreat at Medium Damage: Your unit will retreat (return to repair facility, +HQ, or LZ) at medium (yellow) damage

+

Retreat at Heavy Damage: Your unit will retreat at heavy (red) damage

Firing

images/firing.jpg

Fire At Will: Fires at any enemy (default)

+

Return Fire: Only fire if fired at

+

Do Not Fire: Units will not fire

Movement

images/movement.jpg

Patrol: Moves in a circle on a position. Just +click an area after selecting it.

+

Pursue: Pursue enemy.

+

Guard: Stay near an area or structure. (default)

+

Hold Position: Do not move under any circumstances.

Return

images/return.jpg

Return for Repair: Unit will return to a Repair +Facility

+

Return to HQ: Unit will return to Command Center or LZ (campaign)

+

Go To Transport: Unit will go and board transport

Recycling

images/recycling.jpg

Recycling a unit will send it to the nearest Repair Facility or Factory, and +destroy it. Half the power used in making it will be refunded to you. The +unit’s experience level will be placed in the next unit that is manufactured.

Unit experience

See also: URL Unit +experience

Units have experience levels depending on how many kills the unit has. A higher +experience level means that a unit is more accurate, moves faster and takes +less damage. An icon displaying a unit’s rank is displayed next to the unit’s +health bar.

Hardpoints and bunkers

Hardpoints, bunkers, and other defensive structures cannot be ordered to shoot +directly. However, you can assign artillery emplacements to a sensor tower. +Nearby commanders with the indirect fire support option activated will also +command these structures.

Indirect-fire units and sensors

See: Sensors and artillery

diff --git a/macosx/Resources/WarzoneHelp/ar01s07.html b/macosx/Resources/WarzoneHelp/ar01s07.html new file mode 100644 index 00000000000..f73175d43bc --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s07.html @@ -0,0 +1,42 @@ + + +7. Ordering VTOLs

7. Ordering VTOLs

VTOLs are used similarly to ground units. However, they do have a few +differences. For one thing, they can fly

7.1. Design and production

To produce VTOL units, you’ll need the URL +VTOL Propulsion and +URL VTOL Factory +researched, and a VTOL Factory built. You should also research and build a few +URL VTOL +Rearming Pads, otherwise, they won’t be able to reload ammo.

Before you produce a VTOL unit, you must design it. VTOLs are designed the same +way as regular units — simply select VTOL propulsion — but use slightly +different weapons (more on that later).

VTOLs can only be built at VTOL Factories. VTOL factories can be upgraded with +factory modules — there’s no need to research a separate "VTOL factory +module".

7.2. Moving

After producing a VTOL from a VTOL Factory, it will fly and land on the rally +point. VTOLs can be ordered to move and attack like any regular unit. Although +they will fly over water and cliffs, they can’t land on them.

7.3. Attacking

VTOL weapons differ drastically from the norm.

To attack with a VTOL, select it and click an enemy like normal. However, you +may have noticed the white ammo bar below its health bar as you start +attacking.

Unlike ground units, which reload automatically, VTOLs carry a limited amount +of ammo. Once that ammo runs out, the VTOL can’t attack until it refuels. A +VTOL out of ammo will automatically find a VTOL rearming pad to rearm and +repair itself (and will resume attacking once fully rearmed), or it can be +manually rearmed by selecting it and clicking on a rearming pad.

VTOLs will not attack anything automatically. However, by selecting a VTOL and +alt+clicking on an area, a VTOL will patrol the area between its current +location and the clicked location, and attack anything in the vicinity. +Alternatively, they can be assigned to VTOL strike towers and VTOL CB towers, +which will cause them to function similarly to artillery assigned to sensor towers.

7.4. VTOL weapons

Most weapons have a VTOL equivalent, which does approximately twice as much +damage, but has limited ammo. VTOL versions of regular weapons, like cyborgs, +do not need to be researched separately.

In addition to VTOL versions of ground-based direct weapons, VTOLs can also use +URL bomb weapons. +These weapons are the equivalent of artillery, and are very powerful.

7.5. Defending against VTOLs

VTOLs are not ground-based units, so most ground weapons cannot hit them. They +an only be hit by either anti-air (often abbreviated AA) (can only hit air) or +versatile (can hit air or ground) weapons.

There are only a few weapons that are versatile: machineguns, lasers, and +Mini-Rocket Pod. Rockets and missiles are also versatile, but only when mounted +on a cyborg or VTOL. In addition to being uncommon, versatile weapons do not do +as much damage to VTOLs as dedicated anti-air, so having some AA is +recommended.

There are three types of dedicated AA. In order of powerfulness, they are: Flak +(Hurricane, Cyclone, Whirlwind), SAM (Avenger, Vindicator), and Stormbringer.

7.6. Other orders

Patrol: In the Unit Orders box (right-click, remember?), there are a couple of +new icons. Patrol will do the same thing as alt+clicking — move back and forth +between its current location and the clicked location, and attack anything near +its path, refueling when they need to before returning to defending.

Circle: In the Unit Orders box, next to Patrol, is the Circle button. Click it +and then click an area of ground, and the selected VTOLs will take off and fly +in a circle above the selected point. Like Patrol, they will attack anything +that gets nearby, and refuel automatically.

diff --git a/macosx/Resources/WarzoneHelp/ar01s08.html b/macosx/Resources/WarzoneHelp/ar01s08.html new file mode 100644 index 00000000000..2b34cf372da --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s08.html @@ -0,0 +1,9 @@ + + +8. Command Panel

8. Command Panel

There are six different command panel interfaces, plus a central button. You +open up a command interface by pressing the appropriate button.

images/commandpanel.png

F1: Manufacture

+

F2: Research

+

F3: Build

+

F4: Design

+

F5: Intelligence Display

+

F6: Commanders

The middle button closes any open command interface.

diff --git a/macosx/Resources/WarzoneHelp/ar01s09.html b/macosx/Resources/WarzoneHelp/ar01s09.html new file mode 100644 index 00000000000..5a78ccb4da6 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s09.html @@ -0,0 +1,23 @@ + + +9. Manufacturing

9. Manufacturing

Manufacturing units is similar to building structures. The buildings that can +build structures are Factories, Cyborg Factories and VTOL Factories.

images/manufacture-select.jpg

Selecting a unit to be manufactured

images/manufacture.jpg

The unit being manufactured

9.1. Building a Unit

To manufacture a unit, you need to press the Manufacture button. A Fast Find +bar will open at the bottom of the screen, between the radar and the Command +Panel.

The bottom row of the two contains every Factory, Cyborg Factory and VTOL +Factory built. Clicking it will zoom the camera to the structure.

To manufacture a unit, click the space above a factory. If this factory is +capable of building a unit, it will appear in a menu on the left side of the +screen.

A factory can only build a unit if the body of a unit is a certain type +(unit/cyborg/VTOL), and if the factory has enough modules applied.

9.2. Queuing Units

You can build up to nine units by repeatedly clicking the unit. You can also +right-click the unit to lower the amount of units to build — right-clicking on +a unit with no units queued will set the queue to 9.

9.3. Building Status

While a unit is building, the Fast Find bar above the factory building the unit +will be displayed. If the bar is green, the unit is gathering power to build +the unit. If the bar is yellow, the unit is building.

9.4. Rally Points

When the unit is done building, it will spawn next to the factory, then proceed +to a rally point. A rally point is created when a factory is made. +Right-clicking on the factory in the bottom Fast Find row will centre the +camera on a spawn point. Clicking a rally point will allow you to move it in a +similar way to building a structure. Please note that moving a rally point +while a unit is moving to one will not affect its path.

images/rallypoints.jpg

Rally points (clockwise, from top left): Cyborg rally point, Factory rally +point, Repair Facility, VTOL rally point

9.5. Looped production

You can also set looped production by left and right clicking the loop button +in the left column near the top. This repeats the build sequence you set the +amount of times shown next to the button. This can be set to infinite by +right-clicking when the number reads zero.

diff --git a/macosx/Resources/WarzoneHelp/ar01s10.html b/macosx/Resources/WarzoneHelp/ar01s10.html new file mode 100644 index 00000000000..25037868bc3 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s10.html @@ -0,0 +1,21 @@ + + +10. Research

10. Research

Researching technologies is very simple. You can only research technologies +with Research Facilities.

images/research-select.jpg

Selecting a topic to research

images/research.jpg

The topic being researched

10.1. Researching

Single Player

In the single player game, you collect Artefacts from enemies and research +them. Artefacts are small white boxes with a wrench above them, and can be +collected by any unit by moving to it.

Multiplayer/Skirmish

In Multiplayer/Skirmish games, you progress along a "tech tree" - a couple of +topics can be researched, which in turn will unlock more technologies - also +referred to as progressing up the tech tree.

10.2. Researching a topic

When you open the Research menu, a Fast Find menu with two rows will appear at +the bottom of the screen. All your research facilities are shown on the second +row. Clicking a research facility will zoom the camera to it.

Clicking the blank icon above a facility will show a set of icons on the left. +You can hold the mouse over an icon to see its name. Click an icon to start +researching it. Only one center can research one technology at a time.

While a facility is researching, it displays a bar in its Fast Find area. If +the bar is green, the facility is gathering power. If it is yellow, the topic +is being researched.

10.3. Research Completion

When research is completed, the game will inform you by a message and playing a +sound "Research Completed". If it was a major technology advancement, an entry +will be made in the Intelligence Display. You can check the entry for more +information about the research.

10.4. Research Upgrades

You can research a Research Module during the course of the game. To apply it, +select a truck and left click a non-upgraded Research Center, and the truck +will build it. However, the topic you are researching will be stopped until the +module is built - it’s your choice to let it build or wait.

Other upgrades are also available for Research Centers, but these don’t make +you wait to apply an upgrade to a building.

diff --git a/macosx/Resources/WarzoneHelp/ar01s11.html b/macosx/Resources/WarzoneHelp/ar01s11.html new file mode 100644 index 00000000000..6594ecdf0df --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s11.html @@ -0,0 +1,30 @@ + + +11. Building

11. Building

Building structures is absolutely vital in Warzone - from Factories to build +units, to Research Centers for researching new technology.

Building can be done with units with Trucks as turrets and Combat Engineers.

images/building-select.jpg

Selecting a structure to build

images/building.jpg

Selecting an area to build the structure

11.1. Building a Structure

To build, you need to select Build on the Command Panel, and this will bring up +two rows of icons on the bottom of the screen, between the Command Panel and +the Radar. These each represent one unit (either a truck or a Combat Engineer) +that is able to build. Clicking the bottom row of icons will zoom the camera to +the unit. The top row of icons will pull up a bar on the left side of the +screen (diagram 1). The two columns of icons represent the structures you can +build. Click a structure on the columns to select it for building. You can hold +the mouse over an icon to see the structure’s name.

11.2. Selecting a location

When you select a structure, it closes the two menus (like clicking the middle +button). A white square will appear in the world. This is where your structure +will be placed. Move the square by moving the mouse. Click to place the build +site for the structure. If the square is red, the structure cannot be placed. +To build "walls" (when building defenses) you can click and drag the box to +draw a wall.

11.3. Oil Derricks

Oil derricks can only be built on Oil Pools which aren’t on fire. Fires on Oil +Pools will burn out over time. Oil derricks are built automatically if a truck +is selected and you left-click an Oil Pool.

The unit you selected to build the structure will move to build the structure.

If you open the Build menu again, the unit’s status will be shown in the Fast +Find bar. If there is a structure without a bar in the Fast Find top row above +a unit, the unit is moving to the build site. If there is a green bar, it is +accumulating power for building. If there is a yellow bar, it is building the +site.

11.4. Repairing

You can assign a unit to repair a structure by selecting it and left-clicking a +building.

11.5. Demolishing

Demolishing a building is nearly as simple as building one. Select "Demolish +Structure" in the Structure menu and click a building to demolish. The unit +will move to the building and destroy it, giving you half the power used in +building the structure. Demolish Structure will always be available, from start +of game to end.

11.6. Teamwork

You can assign extra trucks/cyborgs to a building to build it faster. Simply +select a unit and left-click a structure, and the unit will move to the +building and start helping construction.

11.7. Hardcrete and Tank Traps

You may wonder what the Hardcrete and Tank Traps do. Well, they do nothing. +They just sit there and keep your units and enemy units from passing through.

diff --git a/macosx/Resources/WarzoneHelp/ar01s12.html b/macosx/Resources/WarzoneHelp/ar01s12.html new file mode 100644 index 00000000000..c647053e2c1 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s12.html @@ -0,0 +1,42 @@ + + +12. Design

12. Design

You need to design new units and VTOLs if you want to overpower your enemies +and get that sweet taste of victory. This aspect of the game is what makes +Warzone unique in its own way. Note that you need a Command Center to be able +to design units!

images/design.jpg

Designing a new unit

images/design-unit.jpg

The unit being designed

12.1. Designing a unit

To make a new unit, select the Design icon in the Command Panel. This will make +two columns appear on the left of the screen. To make a new design, select the +green body. To select another unit to edit, just click it.

Designing a new unit is simple. It’s a three-step procedure: selecting a body, +a propulsion system, and a turret. The three picked will result in a new unit.

images/design-more.png

Clockwise, from top left: Select a body, propulsion type, turret, and closing +the menu

12.2. Designing the unit

When a new unit is started, a list of bodies will appear on the right, with a +green outline of a body in the centre. A two-column body list will appear on +the right. Select one to move on to the next section — the propulsion type. +Select a type and move on to the turret. There are two types of turrets, +weapons and systems. Both are defined at the top of the two-column by buttons — you can switch by clicking the respective button. Select a turret, and +you’re done.

images/design-screen.jpg

The top half of the Design (minus completed designs)

  1. +The name of a unit. You can click this and change it by typing. +
  2. +Click this to change a body of a design. +
  3. +Click this to change a propulsion type of a design. +
  4. +Click this to change a turret of a design. +
  5. +Click this to delete the currently selected design (only works with +completed designs) +
  6. +Power required to make the unit +
  7. +Hit points the unit has +
  8. +Select the System turrets (turret only, normal units only) +
  9. +Select the Weapon turrets (turret only, normal units only) +

images/design-bars.jpg

  1. +How fast the unit moves over roads +
  2. +How fast the unit moves off-road +
  3. +How fast the unit moves over water +
  4. +Weight of the unit (affects the speed and durability of the unit) +
diff --git a/macosx/Resources/WarzoneHelp/ar01s13.html b/macosx/Resources/WarzoneHelp/ar01s13.html new file mode 100644 index 00000000000..1556f6d593b --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s13.html @@ -0,0 +1,10 @@ + + +13. Intelligence Display

13. Intelligence Display

While the Intelligence Display doesn’t have a large purpose like the rest of +the functions, it is still very useful indeed - it contains a record of all the +technology you have researched, and your mission objective in Campaign +missions.

images/intelligencedisplay.jpg

Intelligence display with piece of intelligence selected

13.1. What’s displayed

When you open the Intelligence Display, two rows of icons appear on the bottom +of the screen. Selecting an icon will display information in the middle of the +screen. This is helpful for looking at technologies you have researched. During +Campaign, a piece of intelligence always displayed is your mission objective.

13.2. We Brake For Nobody

Please note that while the Intelligence Display pauses the game in Campaign +mode, it doesn’t do so in Multiplayer and Skirmish!

diff --git a/macosx/Resources/WarzoneHelp/ar01s14.html b/macosx/Resources/WarzoneHelp/ar01s14.html new file mode 100644 index 00000000000..a21790ec6e1 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s14.html @@ -0,0 +1,30 @@ + + +14. Commanders

14. Commanders

images/commander.png

Command turrets are used much like sensors, except +they can command any attacking unit, not just artillery. They are limited to +having 6 non-artillery attacking units assigned to them at first, but this +limit rises by 2 each time the commander gains a rank, which happens relatively +quickly.

Command turrets provide an URL +accuracy, armor, and movement speed bonus +to all units assigned to them.

images/commander-panel.jpg

The Commanders panel. Note the similarity to the Unit Orders panel.

14.1. Prerequisites

Commanders require you to research the Commander technology.

14.2. Attaching

To attach a unit to a Commander, select a unit, then left-click the Commander +you want to attach the unit to. A symbol will appear next to the unit to +signify it is attached.

14.3. Limits

Be warned, however; Commanders have a limit to the amount of direct-fire units +(eg machineguns) which is affected by their own experience level. Levels are +earned by the

Commander reaching 2 kills, 4, 8, 16, 32, 64 and so on. Each experience level +allows the Commander 2 more direct-fire units. However, a Commander can have as +many indirect-fire units as it wants.

14.4. Detaching

To detach a unit from a Commander, select the unit you want to detach, hold the +Control key, and give the unit a new order (eg. move).

14.5. Targeting a unit

You can designate a target by selecting a Commander and right-clicking a unit. +This allows any attached units to have greater accuracy when firing on a +targeted unit.

14.6. Commander Unit Command Centre

A Commander Unit Command Centre is similar to a Unit Command Centre, but there +are extra buttons.

14.7. Factory Assignment

images/commander-factory-assignment.jpg

The Commander Factory assignment buttons

You can assign a factory to a Commander. This makes a factory manufacture units +and automatically assign them to the Commander’s group. To do so, bring up the +Commanders menu by left-clicking the Commander and opening the Commanders menu, +or right click the Commander, and click the factory NUMBER at the bottom of the +Command Console.

You can find a factory number by looking at the number on the factory in the +Manufacture Fast Find bar. There are three rows of these numbers — the top is +normal Factories, middle; Cyborg factories, bottom; VTOL factories.

14.8. Going for repairs, BRB

A unit that retreats from the battle to go to a repair facility, will stay +connected to its Commander group. When it is done repairing, it will return to +the Commander.

14.9. Indirect fire support

images/indirect-fire-support.jpg

The indirect fire support icon

You can assign all the indirect fire pits and emplacements to a Commander’s +designated target, also known as "fire support". To do so, simply select a +Commander, open the Commanders menu, and select the above icon. To cancel it, +select the same button, or assign the fire support to another commander.

diff --git a/macosx/Resources/WarzoneHelp/ar01s15.html b/macosx/Resources/WarzoneHelp/ar01s15.html new file mode 100644 index 00000000000..6862a45f0a3 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s15.html @@ -0,0 +1,46 @@ + + +15. Artillery and Sensors

15. Artillery and Sensors

As a review, keep in mind that "artillery" here refers to all indirect-fire +weapons except the mini-rocket artillery (MRL) and Angel Missiles, namely:

Although the MRL and Angel Missiles are indirect-fire weapons, they should be +used like one would use direct-fire weapons, since their range is low enough +that its internal sensor can handle it; external sensors are unnecessary.

15.1. Sensors

images/sensor.png

Regular sensors can be used for scouting and surveillance, but they have a more +important usage: to spot for artillery.

15.2. Using sensors with artillery

Artillery weapons, by themselves, cannot fire more than their sensor range (8 +tiles without upgrades). However, even the lowly mortar has an 18-tile weapon +range. To use it, players need to use sensors.

Artillery structures are the easiest. Simply build a sensor tower, and if the +sensor tower is targeting something within your artillery structures' weapon +range, they will fire at it. An artillery tank, however, needs to be explicitly +assigned to a sensor to function. Select the artillery tanks, then click on a +sensor to assign the tank to the sensor.

images/artillery-sensor.jpg

Artillery assigned to a sensor. Notice the * next to them, which indicates that +they are assigned.

Once the artillery is assigned, if it is assigned to a sensor tower, that tower +will target enemies that come in range automatically.

If it is assigned to a sensor tank, the sensor can be used to attack enemies by +selecting the sensor and targeting an enemy. All artillery assigned to the +sensor will attack its target.

images/artillery-far-away.jpg

Notice that the artillery can be very far away — only the sensor turret needs +to get within range.

To unassign a unit from a sensor, the easiest way is to right-click it, then +tell it to move somewhere. Multiple units can be selected with ctrl+click, and +moving them all.

15.3. CB sensors

images/cb-sensor.png

A CB (Counter-Battery) tower or turret is used similarly to a standard sensor; +however, it serves a specialized purpose: To counter-attack enemy artillery.

Normal sensor towers will direct your artillery to attack whatever is nearby, +but CB towers will direct your artillery to attack any artillery attacking you, +even if they are further away from you than other targets. If you have both a +CB tower and a sensor tower, artillery structures will attack CB targets first, +and only other targets once you are no longer being bombarded by enemy +artillery.

images/cb-sensor-vtol.png

A VTOL CB sensor does the same thing, except to VTOLs assigned to it.

15.4. Sensor towers

Sensor towers and sensor units have several major differences:

  • +A standard sensor turret has a range of 12; a standard sensor tower has a +range of 16 (special sensor turrets have the same range as their tower). +
  • +A sensor tower cannot be ordered to target something specific; they +automatically target the nearest unit (except CB and VTOL CB towers). +
  • +A sensor turret will not target anything automatically; it must be manually +ordered to attack a target +

What counts as a sensor

images/hq.png = images/sensor-tower.png

images/satellite-uplink.png = images/wss.png

The Command Center (HQ) is also considered a standard sensor tower, while the +Satellite Uplink Center is also considered a Wide Spectrum sensor tower. In +addition to their usual functionality, they can also be used as the +corresponding sensor tower (for instance, you can assign artillery to them).

diff --git a/macosx/Resources/WarzoneHelp/ar01s16.html b/macosx/Resources/WarzoneHelp/ar01s16.html new file mode 100644 index 00000000000..9de305e7fcd --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s16.html @@ -0,0 +1,34 @@ + + +16. Transports

16. Transports

Transports are used during the campaign to transport units from one sector to +another (known as Away Missions). In multiplayer, they’re used to transport +cyborgs from one part of the current map to another.

images/transport.jpg

A transport with some units loaded in. The transport menu is open.

16.1. Campaign

Loading Units

To load units into a transport, select the desired units and click the +transport. Only 10 units can occupy a transport at one time. The number of +units you have loaded can be seen in the top left of the screen, next to the +launch button.

Opening the Menu

To open a transport’s menu, click the transport itself. In the screenshot, the +menu is open.

The units already in the transport are listed to the right.

Launching a Transport

To launch a transport, click the button in the top left corner of the screen. +The transport will launch, and proceed to the destination.

Away Missions

images/awaymission.jpg

Hunkered down at the landing zone.

Arrival

When you arrive at the destination, the transport will drop off the units you +loaded into the transport and fly away.

Normal Base Operations

During away missions, you can still research, manufacture and design units. +Simply do it as you would normally, and it will happen back in the base area. +You can only build with trucks you have under your control, though. Remember +you’re on an away mission, and in some missions, you won’t get reinforcements, +so stock well.

Requesting Reinforcements!

On missions where you CAN request reinforcements, the transport button should +be at the top left of the screen. Click it, and you’ll see the transport menu, +with one little twist - all the units you left at home alone are on the right +side of the screen.

To load units into the transport, click them, and they’ll be moved from the +right side of the screen to the left. To launch, hit the launch button again. +To close this screen, hit the middle button on the Command Panel.

Your units will be on their way. The timer next to the Transport button will +have the time remaining until your units get to your location.

Take Me Home

Once your units are on an away mission, they’re not going home until the +mission is completed, or you’ve gotten them killed. I think they’d prefer the +earlier option.

16.2. Multiplayer

The use of transports in Multiplayer is much more limited in comparison to +Singleplayer.

Cyborg Transport

The only type of transport available in Multiplayer is the Cyborg Transport. As +you may or may not have guessed by the name, it can only hold Cyborgs, no +normal units or VTOLs allowed. Cyborg Transports can only be built by VTOL +Factories with 2 modules attached, and the technology needs to be researched.

Loading

To load a cyborg into the transport, select it and click the Cyborg Transport. +The cyborg will load on.

Moving

The Cyborg Transport moves like a normal VTOL - select it and click on a piece +of terrain to move it. It will take off and land at the place you selected.

Unloading

The interface used by the Cyborg Transport is a watered-down version of the +Transport interface. To open it, right click the transport. The cyborgs loaded +on will be displayed on the left. To boot out a cyborg, click it (while landed, +we don’t want them falling, do we? :) ).

Destruction

Cyborg Transports have no weapons, and so are sitting ducks for AA turrets and +hardpoints. If a Cyborg Transport is destroyed and it has a few cyborgs on +board, you’ll lose them too. So be careful, OK?

diff --git a/macosx/Resources/WarzoneHelp/ar01s17.html b/macosx/Resources/WarzoneHelp/ar01s17.html new file mode 100644 index 00000000000..0f921c07b97 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s17.html @@ -0,0 +1,7 @@ + + +17. Keyboard Shortcuts

17. Keyboard Shortcuts

These are the default keyboard shortcuts. If you have customized your key +mapping, your shortcuts may be different.

17.1. Game

Esc

Pause/Menu

F1

Manufacture

F2

Research

F3

Build

F4

Design

F5

Intelligence

F6

Commanders

`

Open/close messages at top

17.2. Multiplayer communication

Enter

Send message

Alt+H

Drop beacon

Z

Toggle sensor display

Table 1. Unit selection by groups

Ctrl+[number]

Assign group [number]

[number]

Select group [number]

Alt+[number]

Select commander [number]


17.3. Unit selection by type

Ctrl+U

Select all units

Ctrl+Z

Select all similar units

double-click

Select all similar units

Ctrl+S

Select all units on screen

Ctrl+D

Select all heavily damaged units

Ctrl+A

Select all attack units (units with weapons)

Ctrl+V

Select all VTOLs

Ctrl+H

Select all hover units

Ctrl+W

Select all wheeled units

Ctrl+F

Select all half-tracked units

Ctrl+T

Select all tracked units

17.4. Unit orders

Ctrl+click

Queue order *

NUM0

Open orders menu

right-click

Open orders menu

/

Do or Die! (Do not retreat automatically)

.

Retreat at Heavy Damage

,

Retreat at Medium Damage

F

Fire at Will

E

Return Fire

C

Hold Fire

S

Hold Position

P

Pursue

Q

Patrol

I

Optimum Range

U

Long Range

R

Return for Repair

Ctrl+R

Return for Recycling

* "Queue order" means that when you Ctrl+click, the unit will do what it +would do if you had clicked, but it will do it after it’s finished what it’s +currently doing. You can hold down Ctrl and tell the unit to do a whole bunch +of things, and it will do them in order.

17.5. Game control

Ctrl+-

Decrease game speed *

Ctrl+=

Increase game speed *

NUM.

Toggle sound

* Note that changing the game speed might lead to problems.

17.6. View

B

Center view on Command Center

F12

View location of previous message

17.7. Camera control

Backspace

Snap (rotate) view to North

NUM8

Pitch back (rotate up)

NUM2

Pitch forward (rotate down)

NUM5

Reset pitch (reset vertical rotation)

NUM4

Rotate left

NUM6

Rotate right

space

Tracking camera (follow selected unit)

17.8. Interface

F10

Take screenshot

Shift+Tab

Toggle radar colors

Ctrl+Tab

Toggle radar terrain

Tab

Toggle interface

diff --git a/macosx/Resources/WarzoneHelp/ar01s18.html b/macosx/Resources/WarzoneHelp/ar01s18.html new file mode 100644 index 00000000000..1bc663e067a --- /dev/null +++ b/macosx/Resources/WarzoneHelp/ar01s18.html @@ -0,0 +1,65 @@ + + +18. Credits

18. Credits

Taken from the AUTHORS.TXT file:

Original game developed by Pumpkin Studios, and published by EIDOS Interactive.
+
+The Warzone 2100 Project team, in alphabetical order:
+
+Thomas Barlow <Mysteryem> : 3D Graphics
+-- <Buginator> : Programming
+Bruce V. Edwards <cathuria> : 2D/3D Graphics
+Elio Gubser <elio, ohyeh> : 2D Graphics
+Steven Koenig <kreuvf> : Documentation, translation
+Gerard Krol <gerard_> : Programming, Textures
+Guangcong Luo <Zarel> : Programming, Balancing, and Documentation
+Per I. Mathisen <per> : Programming
+Kim Metcalfe <lav-coyote25> : Documentation, Maps and Support
+Christian Ohm <cybersphinx> : Programming
+Tim P. <kamaze> : Webmaster
+Giel van Schijndel <Giel> : Programming and Debian Linux and Windows Packaging
+Dennis Schridde <devurandom> : Programming and general Linux and Windows Packaging
+Freddie Witherden <EvilGuru> : Programming and MacOSX Packaging
+
+Former contributors to the GPL version, in alphabetical order:
+
+Scott Balneaves <sbalneav> : Programming
+Roman C. <troman> : Programming and Scripting + Scripting-engine rewrite and AI
+Denis Dupeyron <charun> : Programming
+Don Edwards : 2D Graphics support
+Mike Gilmore <Chojun> : Programming
+-- <Hatsjoe> : 2D Graphics
+Carl Hee <Watermelon> : Programming + Multiturrets
+Adam Holland
+Stefan Huehner <shuehner> : Programming + original 64bit support
+Ari Johnson <iamtheari> : Programming and MacOSX Packaging + original MacOSX port
+Martin Koller <mkoller> : Programming
+Angus Lees <gus> : Debian Packaging
+Dennis Luxen <pret> : Programming
+Kevin Malec <Kevin`> : Websupport
+Dion Mendel <noid> : Programming, original Linux port
+Phil Procario <GrimMoroe, grimandmandy> : 3D Graphics
+-- <Pseudonym404> : Programming + original 64bit support
+Victor Qamly <vqamly> : Programming
+Marcus Rast <charon> : Programming
+Ben Russon <grizzly> : Support
+Hylke van der Schaaf <TheNoid> : Programming
+Dmitri Shuralyov <shurcool> : Programming
+Rodolphe Suescun <rodzilla> : Programming
+-- <vs2k5> : Programming
+
+Non-project members whose content has been used in Warzone, in alphabetical order:
+
+Tristan Bethe : Terrain textures
+Jennifer Boyer : Terrain textures
+Bart Everson : Terrain textures
+Mitch Featherston : Terrain textures
+Peter Kaminski : Terrain textures
+Konstantin Kleine-Niermann : Terrain textures
+Sherrie Thai : Terrain textures
+Mark A. Vargas : Terrain textures
+
+Writers of the Warzone 2100 Quick Start Guide:
+
+Ben Latimore <BlueMaxima>: Wrote most of this guide's content
+Guangcong Luo <Zarel>: Rewrote some sections
+
+This guide is published under the CC0 license.
diff --git a/macosx/Resources/WarzoneHelp/docbook-xsl.css b/macosx/Resources/WarzoneHelp/docbook-xsl.css new file mode 100644 index 00000000000..28412259785 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/docbook-xsl.css @@ -0,0 +1,314 @@ +/* + CSS stylesheet for XHTML produced by DocBook XSL stylesheets. + Tested with XSL stylesheets 1.61.2, 1.67.2 +*/ + +span.strong { + font-weight: bold; +} + +body blockquote { + margin-top: .75em; + line-height: 1.5; + margin-bottom: .75em; +} + +html body { + margin: 1em 5% 1em 5%; + line-height: 1.2; +} + +body div { + margin: 0; +} + +h1, h2, h3, h4, h5, h6 +{ + color: #527bbd; + font-family: tahoma, verdana, sans-serif; +} + +div.toc p:first-child, +div.list-of-figures p:first-child, +div.list-of-tables p:first-child, +div.list-of-examples p:first-child, +div.example p.title, +div.sidebar p.title +{ + font-weight: bold; + color: #527bbd; + font-family: tahoma, verdana, sans-serif; + margin-bottom: 0.2em; +} + +body h1 { + margin: .0em 0 0 -4%; + line-height: 1.3; + border-bottom: 2px solid silver; +} + +body h2 { + margin: 0.5em 0 0 -4%; + line-height: 1.3; + border-bottom: 2px solid silver; +} + +body h3 { + margin: .8em 0 0 -3%; + line-height: 1.3; +} + +body h4 { + margin: .8em 0 0 -3%; + line-height: 1.3; +} + +body h5 { + margin: .8em 0 0 -2%; + line-height: 1.3; +} + +body h6 { + margin: .8em 0 0 -1%; + line-height: 1.3; +} + +body hr { + border: none; /* Broken on IE6 */ +} +div.footnotes hr { + border: 1px solid silver; +} + +div.navheader th, div.navheader td, div.navfooter td { + font-family: sans-serif; + font-size: 0.9em; + font-weight: bold; + color: #527bbd; +} +div.navheader img, div.navfooter img { + border-style: none; +} +div.navheader a, div.navfooter a { + font-weight: normal; +} +div.navfooter hr { + border: 1px solid silver; +} + +body td { + line-height: 1.2 +} + +body th { + line-height: 1.2; +} + +ol { + line-height: 1.2; +} + +ul, body dir, body menu { + line-height: 1.2; +} + +html { + margin: 0; + padding: 0; +} + +body h1, body h2, body h3, body h4, body h5, body h6 { + margin-left: 0 +} + +body pre { + margin: 0.5em 10% 0.5em 1em; + line-height: 1.0; + color: navy; +} + +tt.literal, code.literal { + color: navy; +} + +.programlisting, .screen { + border: 1px solid silver; + background: #f4f4f4; + margin: 0.5em 10% 0.5em 0; + padding: 0.5em 1em; +} + +div.sidebar { + background: #ffffee; + margin: 1.0em 10% 0.5em 0; + padding: 0.5em 1em; + border: 1px solid silver; +} +div.sidebar * { padding: 0; } +div.sidebar div { margin: 0; } +div.sidebar p.title { + margin-top: 0.5em; + margin-bottom: 0.2em; +} + +div.bibliomixed { + margin: 0.5em 5% 0.5em 1em; +} + +div.glossary dt { + font-weight: bold; +} +div.glossary dd p { + margin-top: 0.2em; +} + +dl { + margin: .8em 0; + line-height: 1.2; +} + +dt { + margin-top: 0.5em; +} + +dt span.term { + font-style: normal; + color: navy; +} + +div.variablelist dd p { + margin-top: 0; +} + +div.itemizedlist li, div.orderedlist li { + margin-left: -0.8em; + margin-top: 0.5em; +} + +ul, ol { + list-style-position: outside; +} + +div.sidebar ul, div.sidebar ol { + margin-left: 2.8em; +} + +div.itemizedlist p.title, +div.orderedlist p.title, +div.variablelist p.title +{ + margin-bottom: -0.8em; +} + +div.revhistory table { + border-collapse: collapse; + border: none; +} +div.revhistory th { + border: none; + color: #527bbd; + font-family: tahoma, verdana, sans-serif; +} +div.revhistory td { + border: 1px solid silver; +} + +/* Keep TOC and index lines close together. */ +div.toc dl, div.toc dt, +div.list-of-figures dl, div.list-of-figures dt, +div.list-of-tables dl, div.list-of-tables dt, +div.indexdiv dl, div.indexdiv dt +{ + line-height: normal; + margin-top: 0; + margin-bottom: 0; +} + +/* + Table styling does not work because of overriding attributes in + generated HTML. +*/ +div.table table, +div.informaltable table +{ + margin-left: 0; + margin-right: 5%; + margin-bottom: 0.8em; +} +div.informaltable table +{ + margin-top: 0.4em +} +div.table thead, +div.table tfoot, +div.table tbody, +div.informaltable thead, +div.informaltable tfoot, +div.informaltable tbody +{ + /* No effect in IE6. */ + border-top: 3px solid #527bbd; + border-bottom: 3px solid #527bbd; +} +div.table thead, div.table tfoot, +div.informaltable thead, div.informaltable tfoot +{ + font-weight: bold; +} + +div.mediaobject img { + margin-bottom: 0.8em; +} +div.figure p.title, +div.table p.title +{ + margin-top: 1em; + margin-bottom: 0.4em; +} + +div.calloutlist p +{ + margin-top: 0em; + margin-bottom: 0.4em; +} + +@media print { + div.navheader, div.navfooter { display: none; } +} + +span.aqua { color: aqua; } +span.black { color: black; } +span.blue { color: blue; } +span.fuchsia { color: fuchsia; } +span.gray { color: gray; } +span.green { color: green; } +span.lime { color: lime; } +span.maroon { color: maroon; } +span.navy { color: navy; } +span.olive { color: olive; } +span.purple { color: purple; } +span.red { color: red; } +span.silver { color: silver; } +span.teal { color: teal; } +span.white { color: white; } +span.yellow { color: yellow; } + +span.aqua-background { background: aqua; } +span.black-background { background: black; } +span.blue-background { background: blue; } +span.fuchsia-background { background: fuchsia; } +span.gray-background { background: gray; } +span.green-background { background: green; } +span.lime-background { background: lime; } +span.maroon-background { background: maroon; } +span.navy-background { background: navy; } +span.olive-background { background: olive; } +span.purple-background { background: purple; } +span.red-background { background: red; } +span.silver-background { background: silver; } +span.teal-background { background: teal; } +span.white-background { background: white; } +span.yellow-background { background: yellow; } + +span.big { font-size: 2em; } +span.small { font-size: 0.6em; } diff --git a/macosx/Resources/WarzoneHelp/images/artillery-far-away.jpg b/macosx/Resources/WarzoneHelp/images/artillery-far-away.jpg new file mode 100644 index 00000000000..b78b3b921fc Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/artillery-far-away.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/artillery-sensor.jpg b/macosx/Resources/WarzoneHelp/images/artillery-sensor.jpg new file mode 100644 index 00000000000..c3f4619c89e Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/artillery-sensor.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/attackrange.jpg b/macosx/Resources/WarzoneHelp/images/attackrange.jpg new file mode 100644 index 00000000000..0dcfd747935 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/attackrange.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/awaymission.jpg b/macosx/Resources/WarzoneHelp/images/awaymission.jpg new file mode 100644 index 00000000000..997ad614ad4 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/awaymission.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/building-select.jpg b/macosx/Resources/WarzoneHelp/images/building-select.jpg new file mode 100644 index 00000000000..6f8498da530 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/building-select.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/building.jpg b/macosx/Resources/WarzoneHelp/images/building.jpg new file mode 100644 index 00000000000..253f7b5a210 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/building.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/cb-sensor-vtol.png b/macosx/Resources/WarzoneHelp/images/cb-sensor-vtol.png new file mode 100644 index 00000000000..c196c240511 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/cb-sensor-vtol.png differ diff --git a/macosx/Resources/WarzoneHelp/images/cb-sensor.png b/macosx/Resources/WarzoneHelp/images/cb-sensor.png new file mode 100644 index 00000000000..8b9cef602ae Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/cb-sensor.png differ diff --git a/macosx/Resources/WarzoneHelp/images/cheapweapon.png b/macosx/Resources/WarzoneHelp/images/cheapweapon.png new file mode 100644 index 00000000000..f5ed8cb9835 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/cheapweapon.png differ diff --git a/macosx/Resources/WarzoneHelp/images/commander-factory-assignment.jpg b/macosx/Resources/WarzoneHelp/images/commander-factory-assignment.jpg new file mode 100644 index 00000000000..cb2d15cca60 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/commander-factory-assignment.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/commander-panel.jpg b/macosx/Resources/WarzoneHelp/images/commander-panel.jpg new file mode 100644 index 00000000000..34ae7161e87 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/commander-panel.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/commander.png b/macosx/Resources/WarzoneHelp/images/commander.png new file mode 100644 index 00000000000..0275d98bfae Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/commander.png differ diff --git a/macosx/Resources/WarzoneHelp/images/commandpanel.png b/macosx/Resources/WarzoneHelp/images/commandpanel.png new file mode 100644 index 00000000000..956ef48c1d2 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/commandpanel.png differ diff --git a/macosx/Resources/WarzoneHelp/images/design-bars.jpg b/macosx/Resources/WarzoneHelp/images/design-bars.jpg new file mode 100644 index 00000000000..123805a746b Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/design-bars.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/design-more.png b/macosx/Resources/WarzoneHelp/images/design-more.png new file mode 100644 index 00000000000..771a53981f6 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/design-more.png differ diff --git a/macosx/Resources/WarzoneHelp/images/design-screen.jpg b/macosx/Resources/WarzoneHelp/images/design-screen.jpg new file mode 100644 index 00000000000..cdf83133976 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/design-screen.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/design-unit.jpg b/macosx/Resources/WarzoneHelp/images/design-unit.jpg new file mode 100644 index 00000000000..802a67c3ed5 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/design-unit.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/design.jpg b/macosx/Resources/WarzoneHelp/images/design.jpg new file mode 100644 index 00000000000..575139c9df4 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/design.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/expensiveweapon.png b/macosx/Resources/WarzoneHelp/images/expensiveweapon.png new file mode 100644 index 00000000000..ddea9fe43a2 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/expensiveweapon.png differ diff --git a/macosx/Resources/WarzoneHelp/images/firing.jpg b/macosx/Resources/WarzoneHelp/images/firing.jpg new file mode 100644 index 00000000000..0754057919e Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/firing.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/hq.png b/macosx/Resources/WarzoneHelp/images/hq.png new file mode 100644 index 00000000000..34093923255 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/hq.png differ diff --git a/macosx/Resources/WarzoneHelp/images/indirect-fire-support.jpg b/macosx/Resources/WarzoneHelp/images/indirect-fire-support.jpg new file mode 100644 index 00000000000..7fba590c8ef Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/indirect-fire-support.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/intelligencedisplay.jpg b/macosx/Resources/WarzoneHelp/images/intelligencedisplay.jpg new file mode 100644 index 00000000000..f63db7f5150 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/intelligencedisplay.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/interface.jpg b/macosx/Resources/WarzoneHelp/images/interface.jpg new file mode 100644 index 00000000000..1e5ab626df4 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/interface.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/logo.png b/macosx/Resources/WarzoneHelp/images/logo.png new file mode 100644 index 00000000000..f24992c7176 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/logo.png differ diff --git a/macosx/Resources/WarzoneHelp/images/manufacture-select.jpg b/macosx/Resources/WarzoneHelp/images/manufacture-select.jpg new file mode 100644 index 00000000000..a44f163cdac Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/manufacture-select.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/manufacture.jpg b/macosx/Resources/WarzoneHelp/images/manufacture.jpg new file mode 100644 index 00000000000..c8aa934a54c Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/manufacture.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/minimap.jpg b/macosx/Resources/WarzoneHelp/images/minimap.jpg new file mode 100644 index 00000000000..c354c2fa825 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/minimap.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/movement.jpg b/macosx/Resources/WarzoneHelp/images/movement.jpg new file mode 100644 index 00000000000..0046773a037 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/movement.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/oilresource.jpg b/macosx/Resources/WarzoneHelp/images/oilresource.jpg new file mode 100644 index 00000000000..3b10050fb17 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/oilresource.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/powerbar.jpg b/macosx/Resources/WarzoneHelp/images/powerbar.jpg new file mode 100644 index 00000000000..56fa20e422b Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/powerbar.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/powerupgrade.png b/macosx/Resources/WarzoneHelp/images/powerupgrade.png new file mode 100644 index 00000000000..b4945fc7e61 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/powerupgrade.png differ diff --git a/macosx/Resources/WarzoneHelp/images/rallypoints.jpg b/macosx/Resources/WarzoneHelp/images/rallypoints.jpg new file mode 100644 index 00000000000..fdff980e4ec Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/rallypoints.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/recycling.jpg b/macosx/Resources/WarzoneHelp/images/recycling.jpg new file mode 100644 index 00000000000..51df3165cdc Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/recycling.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/research-select.jpg b/macosx/Resources/WarzoneHelp/images/research-select.jpg new file mode 100644 index 00000000000..08df756fb56 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/research-select.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/research.jpg b/macosx/Resources/WarzoneHelp/images/research.jpg new file mode 100644 index 00000000000..4c4ec1605c5 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/research.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/retreatthreshold.jpg b/macosx/Resources/WarzoneHelp/images/retreatthreshold.jpg new file mode 100644 index 00000000000..e9b1ee7479a Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/retreatthreshold.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/return.jpg b/macosx/Resources/WarzoneHelp/images/return.jpg new file mode 100644 index 00000000000..c076087cb1c Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/return.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/satellite-uplink.png b/macosx/Resources/WarzoneHelp/images/satellite-uplink.png new file mode 100644 index 00000000000..d9162cded18 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/satellite-uplink.png differ diff --git a/macosx/Resources/WarzoneHelp/images/sensor-tower.png b/macosx/Resources/WarzoneHelp/images/sensor-tower.png new file mode 100644 index 00000000000..24c4c301be8 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/sensor-tower.png differ diff --git a/macosx/Resources/WarzoneHelp/images/sensor.png b/macosx/Resources/WarzoneHelp/images/sensor.png new file mode 100644 index 00000000000..b41eb8d6536 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/sensor.png differ diff --git a/macosx/Resources/WarzoneHelp/images/transport.jpg b/macosx/Resources/WarzoneHelp/images/transport.jpg new file mode 100644 index 00000000000..5e2906c1a07 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/transport.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/unitordersmenu.jpg b/macosx/Resources/WarzoneHelp/images/unitordersmenu.jpg new file mode 100644 index 00000000000..d06f04cda33 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/unitordersmenu.jpg differ diff --git a/macosx/Resources/WarzoneHelp/images/wss.png b/macosx/Resources/WarzoneHelp/images/wss.png new file mode 100644 index 00000000000..5b98331e2f2 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/wss.png differ diff --git a/macosx/Resources/WarzoneHelp/images/www.png b/macosx/Resources/WarzoneHelp/images/www.png new file mode 100644 index 00000000000..f07303ad60f Binary files /dev/null and b/macosx/Resources/WarzoneHelp/images/www.png differ diff --git a/macosx/Resources/WarzoneHelp/index.html b/macosx/Resources/WarzoneHelp/index.html new file mode 100644 index 00000000000..613c6df1183 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/index.html @@ -0,0 +1,3 @@ + + +Warzone 2100 Quick Start Guide

Warzone 2100 Quick Start Guide


Table of Contents

1. Introduction
2. Interface
3. Controlling the Camera
4. Minimap
5. Power
5.1. Getting Power
5.2. Pricing
5.3. Upgrades
6. Ordering Units
6.1. Using Units
6.2. Unit orders menu
7. Ordering VTOLs
7.1. Design and production
7.2. Moving
7.3. Attacking
7.4. VTOL weapons
7.5. Defending against VTOLs
7.6. Other orders
8. Command Panel
9. Manufacturing
9.1. Building a Unit
9.2. Queuing Units
9.3. Building Status
9.4. Rally Points
9.5. Looped production
10. Research
10.1. Researching
10.2. Researching a topic
10.3. Research Completion
10.4. Research Upgrades
11. Building
11.1. Building a Structure
11.2. Selecting a location
11.3. Oil Derricks
11.4. Repairing
11.5. Demolishing
11.6. Teamwork
11.7. Hardcrete and Tank Traps
12. Design
12.1. Designing a unit
12.2. Designing the unit
13. Intelligence Display
13.1. What’s displayed
13.2. We Brake For Nobody
14. Commanders
14.1. Prerequisites
14.2. Attaching
14.3. Limits
14.4. Detaching
14.5. Targeting a unit
14.6. Commander Unit Command Centre
14.7. Factory Assignment
14.8. Going for repairs, BRB
14.9. Indirect fire support
15. Artillery and Sensors
15.1. Sensors
15.2. Using sensors with artillery
15.3. CB sensors
15.4. Sensor towers
16. Transports
16.1. Campaign
16.2. Multiplayer
17. Keyboard Shortcuts
17.1. Game
17.2. Multiplayer communication
17.3. Unit selection by type
17.4. Unit orders
17.5. Game control
17.6. View
17.7. Camera control
17.8. Interface
18. Credits
diff --git a/macosx/Resources/WarzoneHelp/javascript.pdf b/macosx/Resources/WarzoneHelp/javascript.pdf new file mode 100644 index 00000000000..f8e45f439d7 Binary files /dev/null and b/macosx/Resources/WarzoneHelp/javascript.pdf differ diff --git a/macosx/Resources/WarzoneHelp/warzone2100.6.html b/macosx/Resources/WarzoneHelp/warzone2100.6.html new file mode 100644 index 00000000000..e50760f68d2 --- /dev/null +++ b/macosx/Resources/WarzoneHelp/warzone2100.6.html @@ -0,0 +1,89 @@ + + +warzone2100

Name

warzone2100 — 3D real time strategy game

Synopsis

warzone2100 [OPTIONS]

DESCIPTION

This manual page documents briefly the warzone2100 command.

Warzone 2100 is a 3D science fiction real time strategy game.

OPTIONS

Note: In contrast to older versions option parameters need a =, space doesn’t +work anymore.

+--cheat +
+ Run in cheat mode. +
+--datadir=DIR +
+ Set default datadir to DIR. +
+--debug=FLAG +
+ Show debug for FLAG, use this several times for several flags. Useful + flags include wz, 3d, sound, video. all gives all of that and + much more. +
+--debugfile=FILE +
+ Log debug output in FILE. +
+--fullscreen +
+ Play in fullscreen mode. +
+--help +
+ Show help and exit. +
+--mod=MOD +
+ Enable global mod MOD. +
+--mod_ca=MOD +
+ Enable campaign only mod MOD. +
+--mod_mp=MOD +
+ Enable multiplay only mod MOD. +
+--savegame=NAME +
+ Load a saved game NAME (needs to include the .gam extension). +
+--window +
+ Play in windowed mode. +
+--version +
+ Output version info and exit. +
+--resolution=WIDTHxHEIGHT +
+ Run at WIDTH times HEIGHT screen resolution. This needs to be a + resolution supported by your X server. +
+--(no)shadows +
+ Toggle the shadows. +
+--(no)sound +
+ Toggle the sound. +
+--(no)texturecompression +
+ Toggle texture compression (default on). At least on systems where Mesa’s + libtxc-dxtn handles texture compression, loading is slower with it enabled. + In-game FPS are also higher though. +

The fullscreen/window, resolution, sound, and shadows settings are +stored, so they only need to be specified once, or when you want to +change them.

EXAMPLES

+warzone2100 --fullscreen --resolution=800x600 +
+ Run in full screen at 800x600 screen resolution. +
+warzone2100 --window --resolution=800x600 +
+ Run in a window at 800x600 screen resolution. +
+warzone2100 +
+ Run the game, with the last used resolution, fullscreen/window, sound and + shadow settings. +

AUTHORS

See the copyright file included in the package.

This manual page was originally written by Linas Zvirblis <0x0007@gmail.com> +for the Debian project, and modified by the Warzone project.

diff --git a/macosx/Warzone.xcodeproj/project.pbxproj b/macosx/Warzone.xcodeproj/project.pbxproj index f45619e54a0..0260b643844 100644 --- a/macosx/Warzone.xcodeproj/project.pbxproj +++ b/macosx/Warzone.xcodeproj/project.pbxproj @@ -7,6 +7,18 @@ objects = { /* Begin PBXAggregateTarget section */ + 435AE73F14B5566700B01C85 /* Generate Docs */ = { + isa = PBXAggregateTarget; + buildConfigurationList = 435AE74614B5566D00B01C85 /* Build configuration list for PBXAggregateTarget "Generate Docs" */; + buildPhases = ( + 435AE73E14B5566700B01C85 /* Doc Build */, + 435AE76714B55AE000B01C85 /* Doc Index */, + ); + dependencies = ( + ); + name = "Generate Docs"; + productName = "Generate Docs"; + }; 438B0C05137730FE008184FC /* Fetch Third Party Sources */ = { isa = PBXAggregateTarget; buildConfigurationList = 438B0C0E13773146008184FC /* Build configuration list for PBXAggregateTarget "Fetch Third Party Sources" */; @@ -437,6 +449,7 @@ 4355E13110D6028C00A19EE4 /* theora.h in Headers */ = {isa = PBXBuildFile; fileRef = 4355E12D10D6028C00A19EE4 /* theora.h */; settings = {ATTRIBUTES = (Public, ); }; }; 4355E13210D6028C00A19EE4 /* theoradec.h in Headers */ = {isa = PBXBuildFile; fileRef = 4355E12E10D6028C00A19EE4 /* theoradec.h */; settings = {ATTRIBUTES = (Public, ); }; }; 4355E13310D6028C00A19EE4 /* theoraenc.h in Headers */ = {isa = PBXBuildFile; fileRef = 4355E12F10D6028C00A19EE4 /* theoraenc.h */; settings = {ATTRIBUTES = (Public, ); }; }; + 435AE7B014B55C3400B01C85 /* WarzoneHelp in Resources */ = {isa = PBXBuildFile; fileRef = 435AE76A14B55C3400B01C85 /* WarzoneHelp */; }; 435D3B6A149AC4A000E24F69 /* cursors_sdl.cpp in Sources */ = {isa = PBXBuildFile; fileRef = 4301EC49149A3DE90054BABB /* cursors_sdl.cpp */; }; 436671C713D1FF5D00FE85BA /* glc.h in Headers */ = {isa = PBXBuildFile; fileRef = 436671C213D1FF5D00FE85BA /* glc.h */; settings = {ATTRIBUTES = (Private, ); }; }; 436671C813D1FF5D00FE85BA /* glew.h in Headers */ = {isa = PBXBuildFile; fileRef = 436671C313D1FF5D00FE85BA /* glew.h */; settings = {ATTRIBUTES = (Private, ); }; }; @@ -1603,6 +1616,7 @@ 4355E12D10D6028C00A19EE4 /* theora.h */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.h; name = theora.h; path = external/libtheora/include/theora/theora.h; sourceTree = ""; }; 4355E12E10D6028C00A19EE4 /* theoradec.h */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.h; name = theoradec.h; path = external/libtheora/include/theora/theoradec.h; sourceTree = ""; }; 4355E12F10D6028C00A19EE4 /* theoraenc.h */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.h; name = theoraenc.h; path = external/libtheora/include/theora/theoraenc.h; sourceTree = ""; }; + 435AE76A14B55C3400B01C85 /* WarzoneHelp */ = {isa = PBXFileReference; lastKnownFileType = folder; name = WarzoneHelp; path = Resources/WarzoneHelp; sourceTree = ""; }; 4366712C13D1FCC300FE85BA /* QuesoGLC-All.xcconfig */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = text.xcconfig; name = "QuesoGLC-All.xcconfig"; path = "configs/QuesoGLC-All.xcconfig"; sourceTree = ""; }; 4366712D13D1FCC300FE85BA /* QuesoGLC-Debug.xcconfig */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = text.xcconfig; name = "QuesoGLC-Debug.xcconfig"; path = "configs/QuesoGLC-Debug.xcconfig"; sourceTree = ""; }; 4366712E13D1FCC300FE85BA /* QuesoGLC-Release.xcconfig */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = text.xcconfig; name = "QuesoGLC-Release.xcconfig"; path = "configs/QuesoGLC-Release.xcconfig"; sourceTree = ""; }; @@ -2100,6 +2114,7 @@ 0246A05C0BD3C975004D1C70 /* Warzone.icns */, 02356D780BD3BB3500E9A019 /* Warzone-Info.plist */, 43B8FF3C127CD949006F5A13 /* Fonts */, + 435AE76A14B55C3400B01C85 /* WarzoneHelp */, 43025C2B111FB072006C49B1 /* wzlocal */, ); name = Resources; @@ -3895,6 +3910,7 @@ 43AA702913C7FC640015B52B /* QJson */, 4366718113D1FD5600FE85BA /* QuesoGLC */, 43F77C7710F0125E00E04615 /* Make DMGs for Release */, + 435AE73F14B5566700B01C85 /* Generate Docs */, ); }; /* End PBXProject section */ @@ -3913,6 +3929,7 @@ files = ( 0246A05D0BD3C975004D1C70 /* Warzone.icns in Resources */, 438BDDF31129DC9A00998660 /* InfoPlist.strings in Resources */, + 435AE7B014B55C3400B01C85 /* WarzoneHelp in Resources */, ); runOnlyForDeploymentPostprocessing = 0; }; @@ -4108,6 +4125,34 @@ shellPath = /bin/sh; shellScript = "DirectorY=\"gettext-0.17.mpkg_\"\nOutDir=\"gettext-0.17.mpkg\"\nFileName=\"gettext-0.17.mpkg.tar.gz\"\nBuiltDLP=\"http://downloads.sourceforge.net/project/warzone2100/build-tools/mac/gettext-0.17.mpkg.tar.gz\"\nMD5Sum=\"ba7984918fe0b36e2e7c786693e005f2\"\n\n# Checks\nexport PATH=$PATH:/sw/bin:/opt/local/bin\nif type -aP msgfmt; then\n echo \"msgfmt exists, skipping\"\n exit 0\nelif [ -x \"/opt/local/bin/port\" ]; then\n echo \"warning: Please run the following command in the terminal: 'sudo port install gettext'.\" >&2\n open -b com.apple.Terminal\n exit 1\nelif [ -d \"${SRCROOT}/external/${OutDir}\" ]; then\n touch build/notrans.dis\n echo \"warning: Gettext support has been disabled because we could not find a binary.\" >&2\n exit 0\nelif [ ! `sw_vers -productVersion | sed -e 's:^...\\(.\\)..$:\\1:'` -ge \"6\" ]; then\n touch build/notrans.dis\n echo \"warning: Gettext support has been disabled because we could not find a binary.\" >&2\n exit 0\nfi\n\nconfigs/FetchPrebuilt.sh \"${DirectorY}\" \"${OutDir}\" \"${FileName}\" \"${BuiltDLP}\" \"${MD5Sum}\"\nFetchExitStatus=$?\n\n# Install\nif [ ! \"${FetchExitStatus}\" = \"0\" ]; then\n exit \"${FetchExitStatus}\"\nelif [ -d \"${SRCROOT}/external/${OutDir}\" ]; then\n echo \" Please install the gettext package before continuing.\" >&2\n open \"${SRCROOT}/external/${OutDir}\"\n exit 1\nfi"; }; + 435AE73E14B5566700B01C85 /* Doc Build */ = { + isa = PBXShellScriptBuildPhase; + buildActionMask = 2147483647; + files = ( + ); + inputPaths = ( + ); + name = "Doc Build"; + outputPaths = ( + ); + runOnlyForDeploymentPostprocessing = 0; + shellPath = /bin/sh; + shellScript = "export PATH=$PATH:/sw/bin:/opt/local/bin\n\n# Config\nmWarzoneHelp=\"macosx/Resources/WarzoneHelp\"\n\ncd \"${SRCROOT}/..\"\n\n# asciidoc based docs\nif type -aP a2x; then\n\t# quickstartguide\n\ta2x -f chunked -D \"${mWarzoneHelp}\" doc/quickstartguide.asciidoc\n\tcp -af ${mWarzoneHelp}/quickstartguide.chunked/* ${mWarzoneHelp}\n\trm -fr ${mWarzoneHelp}/quickstartguide.chunked\n\n\t# man page\n\ta2x -f xhtml -d manpage -D \"${mWarzoneHelp}\" doc/warzone2100.6.asciidoc\nelse\n\techo \"error: no suitable a2x (asciidoc) in path\"\n\texit 1\nfi\n\n# LaTeX based docs\nif type -aP pdflatex; then\n\t# javascript doc\n\tgrep src/qtscript.cpp -e '//==' | sed 's://==::' > doc/globals.tex\n\tgrep src/qtscript.cpp -e '//__' | sed 's://__::' > doc/events.tex\n\tgrep src/qtscript.cpp -e '//--' | sed 's://--::' > doc/functions.tex\n\tgrep src/qtscriptfuncs.cpp -e '//--' | sed 's://--::' >> doc/functions.tex\n\tgrep src/qtscriptfuncs.cpp -e '//;;' | sed 's://;;::' > doc/objects.tex\n\tcd doc/\n\tpdflatex javascript.tex\n\tcd ..\n\tcp -af doc/javascript.pdf ${mWarzoneHelp}\nelse\n\techo \"error: no suitable pdflatex (tetex) in path\"\n\texit 1\nfi\n\nexit 0\n"; + }; + 435AE76714B55AE000B01C85 /* Doc Index */ = { + isa = PBXShellScriptBuildPhase; + buildActionMask = 2147483647; + files = ( + ); + inputPaths = ( + ); + name = "Doc Index"; + outputPaths = ( + ); + runOnlyForDeploymentPostprocessing = 0; + shellPath = /bin/sh; + shellScript = "rm -f Resources/WarzoneHelp/WarzoneHelp.helpindex\nhiutil -Caf Resources/WarzoneHelp.helpindex Resources/WarzoneHelp\ncp -af Resources/WarzoneHelp.helpindex Resources/WarzoneHelp/\nrm -f Resources/WarzoneHelp.helpindex\nexit 0\n"; + }; 4366712213D1F83200FE85BA /* QuesoGLC - Fetch source */ = { isa = PBXShellScriptBuildPhase; buildActionMask = 2147483647; @@ -4327,6 +4372,7 @@ ); name = Patch; outputPaths = ( + external/libvorbis/vorbis.diff, ); runOnlyForDeploymentPostprocessing = 0; shellPath = /bin/sh; @@ -5187,6 +5233,27 @@ }; name = Release; }; + 435AE74014B5566800B01C85 /* Debug */ = { + isa = XCBuildConfiguration; + buildSettings = { + PRODUCT_NAME = "Generate Docs"; + }; + name = Debug; + }; + 435AE74114B5566800B01C85 /* StaticAnalyzer */ = { + isa = XCBuildConfiguration; + buildSettings = { + PRODUCT_NAME = "Generate Docs"; + }; + name = StaticAnalyzer; + }; + 435AE74214B5566800B01C85 /* Release */ = { + isa = XCBuildConfiguration; + buildSettings = { + PRODUCT_NAME = "Generate Docs"; + }; + name = Release; + }; 4366718413D1FD5700FE85BA /* Debug */ = { isa = XCBuildConfiguration; baseConfigurationReference = 4366712D13D1FCC300FE85BA /* QuesoGLC-Debug.xcconfig */; @@ -5493,6 +5560,16 @@ defaultConfigurationIsVisible = 0; defaultConfigurationName = Debug; }; + 435AE74614B5566D00B01C85 /* Build configuration list for PBXAggregateTarget "Generate Docs" */ = { + isa = XCConfigurationList; + buildConfigurations = ( + 435AE74014B5566800B01C85 /* Debug */, + 435AE74114B5566800B01C85 /* StaticAnalyzer */, + 435AE74214B5566800B01C85 /* Release */, + ); + defaultConfigurationIsVisible = 0; + defaultConfigurationName = Debug; + }; 4366718713D1FD5700FE85BA /* Build configuration list for PBXNativeTarget "QuesoGLC" */ = { isa = XCConfigurationList; buildConfigurations = (