20.2 Patch - Base Position Swap

will do so. Thx

@nefrontheone , thanks for the tip about the working Movement version but I noted a new barrier.
I can not switch to an externat script (instead the one in the package) since the settings button of the Crucial package will not appear anymore. The landing page (main page) of the game is changed. ...this change causes that I can not switch the Movement script off.

Update:
I switched the script pack off and installed the most important scripts one by one.
"Attack Range" script causes the problem, not The Movement.

"BambiByte;c-2141663" wrote:
I switched the script pack off and installed the most important scripts one by one.
"Attack Range" script causes the problem, not The Movement.

Like me, individuals scripts and only a few of them.

If attack range have bad effects with 20.2 maybe @o0netquik0o can be notified and fix the script in his SoO pack. :-?

As "Attack Range" script highlights also our own bases, - I think, marking those bases in range makes the swap impossible.

I prefer the availability of the improved standalone script. For now, I had several problems with script packs - and usually they are fixed less dinamically.

Have notified @o0netquik0o . He is looking into it. All good. Thx guys.

"Tullysama;c-2142168" wrote:
Have notified @o0netquik0o . He is looking into it. All good. Thx guys.

The latest modifications to the scripts have been made in record time and always trying to anticipate the update in the real worlds.

But as he himself says "There are many scripts and I need help to test them all because it exceeds my capacity / personal time"

Thank you, @o0netquik0o one more time. ;-)

for all try this fix
https://github.com/netquik/CnCTA-SoO-SCRIPT-PACK/blob/Testing/TA_Attack_Range.user.js

"BambiByte;c-2141701" wrote:
As "Attack Range" script highlights also our own bases, - I think, marking those bases in range makes the swap impossible.

I prefer the availability of the improved standalone script. For now, I had several problems with script packs - and usually they are fixed less dinamically.

Right. but using an updated pack or updated single script is the same. If the script has issues it will not work. In the pack you can enable/disable scripts like you would with tampermonkey/greasemonkey.

@o0netquik0o
Thanks for the great job, the fixed script seems to be ok. :)

...the problem was that I could not switch the script off inside the pack, so I had to get rid of the full pack and use standalone scripts instead. The new landing page did not let me access the settings.

"BambiByte;c-2142304" wrote:
@o0netquik0o
Thanks for the great job, the fixed script seems to be ok. :)

...the problem was that I could not switch the script off inside the pack, so I had to get rid of the full pack and use standalone scripts instead. The new landing page did not let me access the settings.

I'm interested in this issue.. can you explain me better why you could not disable the script from options? Thanks