{"action":"closed","issue":{"url":"https://api.github.com/repos/SpringMCLegacy/SpringMCLegacy/issues/48","labels_url":"https://api.github.com/repos/SpringMCLegacy/SpringMCLegacy/issues/48/labels{/name}","comments_url":"https://api.github.com/repos/SpringMCLegacy/SpringMCLegacy/issues/48/comments","events_url":"https://api.github.com/repos/SpringMCLegacy/SpringMCLegacy/issues/48/events","html_url":"https://github.com/SpringMCLegacy/SpringMCLegacy/issues/48","id":84275809,"number":48,"title":"New MaxRange Issues","user":{"login":"zverofaust","id":12214376,"avatar_url":"https://avatars.githubusercontent.com/u/12214376?v=3","gravatar_id":"","url":"https://api.github.com/users/zverofaust","html_url":"https://github.com/zverofaust","followers_url":"https://api.github.com/users/zverofaust/followers","following_url":"https://api.github.com/users/zverofaust/following{/other_user}","gists_url":"https://api.github.com/users/zverofaust/gists{/gist_id}","starred_url":"https://api.github.com/users/zverofaust/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zverofaust/subscriptions","organizations_url":"https://api.github.com/users/zverofaust/orgs","repos_url":"https://api.github.com/users/zverofaust/repos","events_url":"https://api.github.com/users/zverofaust/events{/privacy}","received_events_url":"https://api.github.com/users/zverofaust/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-03T00:17:27Z","updated_at":"2015-06-03T19:43:44Z","closed_at":"2015-06-03T19:43:44Z","body":"Did some investigating, here are my findings:\r\n\r\nFirst off, all UnitMaxRange seems to do is control at which range a unit will give itself an attack order on an enemy unit. In other words, it's ManeuverLeashLength; it tells a unit what range a target has to be before it will give itself an attack order on it, nothing more. Units will still only attack with their longest-ranged weapons.. except, if their longest-ranged weapon isn't Weapon1, they can't, because it'll be /slaved/ to Weapon1, which isn't in range and can't shoot. The unit won't try to move into Weapon1 range; it'll still only move close enough to get /any/ weapon in range. \r\n\r\nAnd to make matters worse, MoveState seems to affect UnitMaxRange somehow. Here's a pic: http://i.imgur.com/PtEl8Hg.jpg In it, three Mithras tanks had 3 different engagement ranges based on their movestate (top=Hold Pos, mid=Maneuver, bottom=Roam). UnitMaxRange here was set at 0.8 of Weapon1 range. Hold Pos was the most 'accurate' and stopped to engage at around 80% of CERMBL range as it should've. Maneuver stopped at just about on CERMBL range. Roam stopped outside of range. Note that in every instance, the /instant/ the vehicle was given an attack order, it stopped to shoot because it found a weapon was in range. In Roam's instance its AC2 was in range, so it didn't have to move. But the AC2 can't fire because it's slaved to a CERMBL, which was out of range. All UnitMaxRange did was determine how close the Mithras' had to be to be given an attack order on the enemy tank, NOT at what range it should move to engage.\r\n"}}