Difference between revisions of "Unit Management"
Jump to navigation
Jump to search
Debug data:
| Line 10: | Line 10: | ||
==Micromanagement== | ==Micromanagement== | ||
===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 | + | 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 09:03, 25 May 2018
How to control your units.
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.
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 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.
Micromanagement
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.17.164.48Start request GET /mediawiki/index.php?diff=next&oldid=3973&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.17.164.48",
"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 "amk159ss7vu0l5n7faugd4u8j5p8g36e" is unsaved, marking dirty in constructor[session] SessionBackend "amk159ss7vu0l5n7faugd4u8j5p8g36e" save: dataDirty=1 metaDirty=1 forcePersist=0[cookie] already deleted setcookie: "wikidb229_mw__session", "", "1715950636", "/", "", "", "1"[cookie] already deleted setcookie: "wikidb229_mw_UserID", "", "1715950636", "/", "", "", "1"[cookie] already deleted setcookie: "wikidb229_mw_Token", "", "1715950636", "/", "", "", "1"[cookie] already deleted setcookie: "forceHTTPS", "", "1715950636", "/", "", "", "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 '3973' new 'next' 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:0f8b92a43784086f04d999a84b33fcaf:0)[Preprocessor] Cached preprocessor output (key: wikidb229-mw_:preprocess-hash:0f8b92a43784086f04d999a84b33fcaf: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}
