yep, the bases were within range, both were able to move, and not on hub terminals. I figure it must be external scripts - I will try deactivating (I use SoO) and see what happens. One of our other guys on Tib 42 tried it and it worked for them, so we just have to work through and find out what is stopping it
Found the culprit. As I am using SoO script pack, there were several external scripts being used, so, I disabled them all, and slowly built back up, until I found the bug, then only installed that script to be sure. It was Tiberium Alliances Attack Range 2.2 that caused the issue, at least for me.
Found the culprit. As I am using SoO script pack, there were several external scripts being used, so, I disabled them all, and slowly built back up, until I found the bug, then only installed that script to be sure. It was Tiberium Alliances Attack Range 2.2 that caused the issue, at least for me.
If you found any problem with scripts in SoO you can try deactivating some scripts and testing.
And if you find some problem like this (inside SoO), please, report this to @o0netquik0o (Thank you)
Not a part of EA / Envision teams - My comments are only mine.
@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.
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.
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.
@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
Replies
what where the circumstances of your test?
Both bases need to be able to use the Move action and they cant be positioned on Hub Terminals.
And in range of movement.
It doesn't work on Tib26 either.
Update:
- It may interfere with movement (planning tool) or another script. Without scripts loaded , it works. Sorry.
Are yo using external scripts?
If you deactivate the external scripts the problem persist?
If you found any problem with scripts in SoO you can try deactivating some scripts and testing.
And if you find some problem like this (inside SoO), please, report this to @o0netquik0o (Thank you)
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.
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. :-?
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.
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. ;-)
https://github.com/netquik/CnCTA-SoO-SCRIPT-PACK/blob/Testing/TA_Attack_Range.user.js
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.
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