Difference between revisions of "Unit Management"
Jump to navigation
Jump to search
Debug data:
| Line 17: | Line 17: | ||
Unit AI is generally effective for artillery units. They will stay at maximum range and hammer away at their target. | Unit AI is generally effective for artillery units. They will stay at maximum range and hammer away at their target. | ||
There are a few quirks about using artillery however. | There are a few quirks about using artillery however. | ||
| − | * UNIT AI requires vision of its target. If you don't have vision or radar of a defensive tower, the artillery could walk into its range and die. | + | ** UNIT AI requires vision of its target. If you don't have vision or radar of a defensive tower, the artillery could walk into its range and die. |
| − | * Radar does not reveal precise location of things, and artillery will miss slightly if you don't get vision of the target at least once. | + | ** Radar does not reveal precise location of things, and artillery will miss slightly if you don't get vision of the target at least once. It will shoot at the radar dot and not at where the target actually is. This has the greatest impact on very precise artillery like the wolverine, impaler, or sling. |
| − | * Unit Ai will shoot at units and not prioritize buildings. What is closest will get shot at first. | + | ** Unit Ai will shoot at units and not prioritize buildings. What is closest will get shot at first. If there is a unit patrolling in front of a defence turret, the arty will prioritize shooting that unit, but will probably never kill it. You can get around this by manually setting targets for your artillery. |
==Micromanagement== | ==Micromanagement== | ||
| + | ===Line move=== | ||
| + | Using line move is essential to maximize unit efficiency. | ||
| + | ** It allows you to maximize | ||
===Retreat micro=== | ===Retreat micro=== | ||
A very common tactic utilized by players, especially in raider micro, is "retreat micro". This type of micro utilizes the feature that units running away tend to hit more than those chasing that unit. | A very common tactic utilized by players, especially in raider micro, is "retreat micro". This type of micro utilizes the feature that units running away tend to hit more than those chasing that unit. | ||
For example, in a scenario in which a glaive is chasing a glaive, the glaive that is running away and being followed will almost always kill the glaive that is following it. This effect is so extreme that you might be able to kill 3-4 glaives with just 1. | For example, in a scenario in which a glaive is chasing a glaive, the glaive that is running away and being followed will almost always kill the glaive that is following it. This effect is so extreme that you might be able to kill 3-4 glaives with just 1. | ||
This is a defensive tactic, as ovbiously you are retreating, but it allows you disengage when you think a fight will not go favorably. | This is a defensive tactic, as ovbiously you are retreating, but it allows you disengage when you think a fight will not go favorably. | ||
Revision as of 14:27, 25 May 2018
How to control your units. (wip)
Contents
Using Unit AI
The easiest way to to use the attack command. This utilizes the unit AI and is probably most effective when used with raiders and skirmishers.
Skirmishers
For skirmishers, this will cause them to try to keep their target at maximum range. This is most effective against units that are slower than the skirmisher, say for example a ronin fighting a thug.
Raiders
Raiders on fight command will try to stay at maximum range to their target, and engage in dodging behavior by swerving side to side, helping them dodge many slower projectiles.
Assaults
Unit ai is not very effective for assaults. It is generally better to just line move them into the enemy, so they can soak up the maximum ammount of damage and screen for your lowe hp units like skirmishers or raiders.
Artillery
Unit AI is generally effective for artillery units. They will stay at maximum range and hammer away at their target. There are a few quirks about using artillery however.
- UNIT AI requires vision of its target. If you don't have vision or radar of a defensive tower, the artillery could walk into its range and die.
- Radar does not reveal precise location of things, and artillery will miss slightly if you don't get vision of the target at least once. It will shoot at the radar dot and not at where the target actually is. This has the greatest impact on very precise artillery like the wolverine, impaler, or sling.
- Unit Ai will shoot at units and not prioritize buildings. What is closest will get shot at first. If there is a unit patrolling in front of a defence turret, the arty will prioritize shooting that unit, but will probably never kill it. You can get around this by manually setting targets for your artillery.
Micromanagement
Line move
Using line move is essential to maximize unit efficiency.
- It allows you to maximize
Retreat micro
A very common tactic utilized by players, especially in raider micro, is "retreat micro". This type of micro utilizes the feature that units running away tend to hit more than those chasing that unit. For example, in a scenario in which a glaive is chasing a glaive, the glaive that is running away and being followed will almost always kill the glaive that is following it. This effect is so extreme that you might be able to kill 3-4 glaives with just 1. This is a defensive tactic, as ovbiously you are retreating, but it allows you disengage when you think a fight will not go favorably.
Debug data:
[SQLBagOStuff] MainObjectStash using store ReplicatedBagOStuff[objectcache] MainWANObjectCache using store EmptyBagOStuffIP: 3.145.40.61Start request GET /mediawiki/index.php?diff=3991&oldid=3985&title=Unit_Management
HTTP HEADERS:
CONTENT-TYPE:
CONTENT-LENGTH: 0
USER-AGENT: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
HOST: zero-k.info
ACCEPT-ENCODING: gzip, br, zstd, deflate
ACCEPT: */*
CONNECTION: close[localisation] LocalisationCache: using store LCStoreDB[session] SessionManager using store SqlBagOStuff[DBReplication] Cannot use ChronologyProtector with EmptyBagOStuff[DBReplication] Wikimedia\Rdbms\LBFactory::getChronologyProtector: request info {
"IPAddress": "3.145.40.61",
"UserAgent": "Mozilla\/5.0 AppleWebKit\/537.36 (KHTML, like Gecko; compatible; ClaudeBot\/1.0; +claudebot@anthropic.com)",
"ChronologyProtection": false,
"ChronologyPositionIndex": 0,
"ChronologyClientId": false
}[DBConnection] Wikimedia\Rdbms\LoadBalancer::lazyLoadReplicationPositions: executed chronology callback.[DBConnection] Wikimedia\Rdbms\LoadBalancer::getLocalConnection: connected to database 0 at 'localhost'.[SQLBagOStuff] Connection mysql object #127 (handle id #121) will be used for SqlBagOStuff[session] SessionBackend "2eb5prjcmgi4mcrlc94eev6cq7d902f8" is unsaved, marking dirty in constructor[session] SessionBackend "2eb5prjcmgi4mcrlc94eev6cq7d902f8" save: dataDirty=1 metaDirty=1 forcePersist=0[cookie] already deleted setcookie: "wikidb229_mw__session", "", "1715940720", "/", "", "", "1"[cookie] already deleted setcookie: "wikidb229_mw_UserID", "", "1715940720", "/", "", "", "1"[cookie] already deleted setcookie: "wikidb229_mw_Token", "", "1715940720", "/", "", "", "1"[cookie] already deleted setcookie: "forceHTTPS", "", "1715940720", "/", "", "", "1"[DBConnection] Wikimedia\Rdbms\LoadBalancer::getLocalConnection: connected to database 0 at 'localhost'.Title::getRestrictionTypes: applicable restrictions to [[Unit Management]] are {edit,move}[ContentHandler] Created handler for wikitext: WikitextContentHandlerArticle::view: showing diff pageDifferenceEngine old '3985' new '3991' rcid ''[MessageCache] MessageCache using store SqlBagOStuff[SQLBagOStuff] Connection mysql object #127 (handle id #121) will be used for SqlBagOStuff[SQLBagOStuff] Connection mysql object #127 (handle id #121) will be used for SqlBagOStuff[SQLBagOStuff] Connection mysql object #127 (handle id #121) will be used for SqlBagOStuff[SQLBagOStuff] Connection mysql object #127 (handle id #121) will be used for SqlBagOStuff[SQLBagOStuff] SqlBagOStuff::lock failed due to timeout for wikidb229-mw_:messages:en.[SQLBagOStuff] Connection mysql object #127 (handle id #121) will be used for SqlBagOStuff[SQLBagOStuff] Connection mysql object #127 (handle id #121) will be used for SqlBagOStuff[MessageCache] MessageCache::load: Loading en... local cache is empty, global cache is expired/volatile, loading from databaseParserFactory: using preprocessor: Preprocessor_HashUnstubbing $wgLang on call of $wgLang::_unstub from ParserOptions->__constructDifferenceEngine old '0' new '0' rcid '0'WikiPage::getParserOutput: using parser cache: no[caches] parser: SqlBagOStuff[SQLBagOStuff] Connection mysql object #127 (handle id #121) will be used for SqlBagOStuff[SQLBagOStuff] Connection mysql object #127 (handle id #121) will be used for SqlBagOStuffParser cache options found.[Preprocessor] Cached preprocessor output (key: wikidb229-mw_:preprocess-hash:c9e5b89f6ea61761af990ba408e92ed6:0)[Preprocessor] Cached preprocessor output (key: wikidb229-mw_:preprocess-hash:c9e5b89f6ea61761af990ba408e92ed6:0)MediaWiki::preOutputCommit: primary transaction round committedMediaWiki::preOutputCommit: pre-send deferred updates completedMediaWiki::preOutputCommit: session changes committedMediaWiki::preOutputCommit: LBFactory shutdown completedTitle::getRestrictionTypes: applicable restrictions to [[Unit Management]] are {edit,move}
