{"push_id":1164795393,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"462f268e3d9596596a0c1a904551825170f77b81","before":"b7bfa83f4f1de05a8d48884e24534f59305b1ce0","commits":[{"sha":"462f268e3d9596596a0c1a904551825170f77b81","author":{"name":"Colin Basnett","email":"b368e135f87ce04d767d0180204f77f9312bb0d2@gmail.com"},"message":"Fix for bug https://github.com/DarklightGames/DarkestHour/issues/537\n\nThis is a slight partial rewrite of how mortar targets are stored and cleared.\n\nI suspect the *actual* cause of this was that a player who changed teams would have `ClearMortarTarget` called *after* the team was switched. This means that the team & index look-up would be erroneous, resulting in bizarre behavior. To fix this, instead of using a team and target index to clear targets, the controller (`DHPlayer`) is passed into `ClearMortarTarget`, and mortar targets are cleared if they have a matching controller. This provides a more robust solution.\n\nRemoved `MortarTargetIndex`, a variable that provided a negligible performance benefit when clearing targets. For some reason it was a replicated variable, so now that's less data to replicate, also.","distinct":true,"url":"https://api.github.com/repos/DarklightGames/DarkestHour/commits/462f268e3d9596596a0c1a904551825170f77b81"}]}
{"actor":{"display_login":"cmbasnett"}}