Just observed that when I put a Pathing Footprint on a Unit, behaviours are no longer able to increase/decrease/modify movement speed in any shape, way or form on that unit. Only its default movement speed (given in Units) will apply. This poses a problem for my map as I need units to move at varying speeds based on a behaviour simulating thrusters to gain/lose momentum.
Is there a workaround for this? I'm guessing that giving the units Upgrades that set the unit's base speed on a whim might work, but that's not nearly as elegant a solution.
Certain models don't respond very well to normal radius' for search areas. If they are more rectangular in shape you can end up with parts of a model that don't register when inside a search area.
What do you mean by "leak related lag" by using the Modify Player effect? Does this also happen by issuing orders to Research an upgrade? I do plan on using this quite a lot.
It has to do with how the game modifies the upgradable fields. Long story short is it causes leaks that accumulate over the course of the game resulting in lag eventually. Same with upgrades, catalog triggers and the modify player effect. As long as use is under 2000 instances per game you should be fine.
The modify player effect now has fields that allow you do anything an upgrade can without needing to research it.
Hello again,
Just observed that when I put a Pathing Footprint on a Unit, behaviours are no longer able to increase/decrease/modify movement speed in any shape, way or form on that unit. Only its default movement speed (given in Units) will apply. This poses a problem for my map as I need units to move at varying speeds based on a behaviour simulating thrusters to gain/lose momentum.
Is there a workaround for this? I'm guessing that giving the units Upgrades that set the unit's base speed on a whim might work, but that's not nearly as elegant a solution.
Why do they need the pathing footprints?
Use a Modify Player effect then to upgrade/downgrade the speed but remember using this too much will cause leak related lag.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
Certain models don't respond very well to normal radius' for search areas. If they are more rectangular in shape you can end up with parts of a model that don't register when inside a search area.
What do you mean by "leak related lag" by using the Modify Player effect? Does this also happen by issuing orders to Research an upgrade? I do plan on using this quite a lot.
It has to do with how the game modifies the upgradable fields. Long story short is it causes leaks that accumulate over the course of the game resulting in lag eventually. Same with upgrades, catalog triggers and the modify player effect. As long as use is under 2000 instances per game you should be fine.
The modify player effect now has fields that allow you do anything an upgrade can without needing to research it.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg