Changes between Version 5 and Version 6 of PetraBot
- Timestamp:
- Oct 26, 2014, 2:08:11 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PetraBot
v5 v6 12 12 13 13 The headquarter module is divided in several sub-modules as attackManager, baseManager, ... which are described below. It is responsible for the development of the civilization (building structures and training units) and the steering of its different sub-modules. 14 14 15 == !AttackManager == 15 16 The attackManager deals with the different attacks. It is mainly a steering function, the real code which handles the training, the preparation and the actual attack is in attackPlan.js. In practise, the attackManager decides on the kind of attack (rush with small number of units, standard attack with medium-size army or attack with a huge army) by creating an attack plan. Then each attack plan defines its target player and the enemy entity which is its primary target. Then it creates build orders (to train the needed units) using three queues (soldiers, champion and siege units). The attack plan may require a transport to attack overseas. Once the primary target is destroyed, the attack plan choose a new target (from the same target player) which is [#accessibility accessible] by land. This continues until either the AI army is destroyed or no new target is found, in which case the army is disbanded. 17 16 18 == !BaseManager == 17 19 Each new cc is the root of a new base, which is governed by its own baseManager. This manager handles workers assigned to that base (for gathering, hunting, fishing, ...) through the file worker.js. It is also responsible for checking base's resources levels, building new dropsites if necessary, repairing its hurt structures. 20 18 21 == !DefenseManager == 19 20 22 The defenseManager is responsible for the response to attacks (either directed towards the AI itself or towards its allies). It also deals with unit garrisoning (either garrisoning ranged units inside a "fighting" structures or garrisoning hurt units inside healing structures). 21 23 24 == !DiplomacyManager == 25 Deals with tributes with allies. 26 22 27 == !GarrisonManager == 23 24 28 It keeps track of all units garrisoned except those garrisoned in ships for transport. 25 29 26 30 == !NavalManager == 27 28 31 The navalManager is in charge of maintaining the fleet (except trader ships which are dealt with in tradeManager) and managing the transport of units (done in transportPlan.js). 29 32 … … 32 35 == !ResearchManager == 33 36 It looks for new tech available and decides on which one to research. 37 34 38 == !TradeManager == 35 The tradeManager deals with barter and trade. It is responsible for finding the best available trade route (either on land or water), training traders and switching trade route when a better one is available. (the version in A17 was rudimentary, a more complete is ready and will be commited after the release).39 The tradeManager deals with barter and trade. It is responsible for finding the best available trade route (either on land or water), training traders and switching trade route when a better one is available. 36 40 37 41 = [=#queueManager !QueueManager] = … … 53 57 In order to vary the strategy of the AI, several personality traits are used in the form of numbers between 0 and 1. Those already implemented include: 54 58 * aggressive: the higher this number, the more rushes in early game 55 * cooperative: the higher this number, the more helpful the AI will be when an allied is attacked. It is foreseen to make this number dynamic, increasing (very slowly) when receiving a tribute from an ally or when being helped by an ally when under attack (ready, but to be committed after A17 is released).59 * cooperative: the higher this number, the more helpful the AI will be when an allied is attacked. This number is dynamic, increasing (very slowly) when receiving a tribute from an ally or when being helped by an ally when under attack. 56 60 * defensive: the higher this number, the more prone to build defensive structure. 57 61
