Forum Discussion
24 Replies
Sort By
- Hello Commander,
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. - nefrontheone5 years agoSeasoned Ace
"EE_Elephterion;c-2141114" wrote:
Hello Commander,
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. - Hello,
It doesn't work on Tib26 either.
Update:
- It may interfere with movement (planning tool) or another script. Without scripts loaded , it works. Sorry. - nefrontheone5 years agoSeasoned AceI tested The Movement (v. 1.0.3.7) with this new feature and works.
- Also Dead bases from you base access panel no longer work if you click on them it does NOT go to the ruin you have to manually search for the ruin.
- nefrontheone5 years agoSeasoned Ace
"michaelbsmith;c-2141239" wrote:
Also Dead bases from you base access panel no longer work if you click on them it does NOT go to the ruin you have to manually search for the ruin.
Are yo using external scripts?
If you deactivate the external scripts the problem persist? - 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
- Movement to and from hubs is not allowed. This is in the patch notes.
- 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.
- nefrontheone5 years agoSeasoned Ace
"Tullysama;c-2141290" wrote:
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)
About Tiberium Alliances Technical Issues
Having problems running the game or a script? Get help with Command and Conquer: Tiberium Alliances with the community!1,628 PostsLatest Activity: 3 days ago
Recent Discussions
- 3 days ago
- 5 days ago
- 19 days ago
- 25 days ago