CNCTA SOO LAB - BUGS|ERRORS REPORTING

o0netquik0o

CNCTA SOO LAB - BUGS|ERRORS REPORTING

Hi All! I want to create a new topic dedicated to BUGS/ERRORS reporting for scripts.
Especially useful to report problems after server updates.
Please report any problem and errors you spot using userscripts, better with a screenshot explaining the issue. I will try to find a a solution and fix the not working scripts. Thanks.

EE_Elephterion

I pinned the discussion to the section so it won't get lost

HanSolo8822

Why it wrongly counts the forgotten bases?
It should be 16 and it shows 19

https://prnt.sc/1d9hlxb

tributarium

On Wrath 22 the simulator does not work on attacking someone. No where does it show what your attack is about to gain or lose. On the other worlds, with the same account, it works as usaul, but not on Wrath 22.

o0netquik0o

@HanSolo8822 Hi mate. First be sure to use last wavy code available.
https://github.com/netquik/CnCTA-SoO-SCRIPT-PACK/blob/master/TA_Wavy.user.js
5 months ago i fixed a max distance issue in this script maybe the problem is the same you are facing.

o0netquik0o

@tributarium Hi

tributarium wrote: »

On Wrath 22 the simulator does not work on attacking someone. No where does it show what your attack is about to gain or lose. On the other worlds, with the same account, it works as usaul, but not on Wrath 22.

Which simulator script are talking about? i entered wrath 22 and have no problems in last versions of TACS and TABS v2. Need more info about the issue to help you out. Maybe try cleaning you browser cache and reload you script and game.



FOR ALL: remember that this is a thread dedicated to userscripts issues only. when posting try to give as much information as possible about your configuration and script versions.

nefrontheone

Please, when reporting bugs from SoO Pack indicate following information:

- Name of script
- Version of script
- Browser used
- World with problem
- Snapshot (if possible)
- How other player can reproduce the error

Please, before sent report check if you have latest version of the scripts pack.

THANK YOU!

o0netquik0o

Hi all! i find a unpleasant issue with InfoSticker script (last version) and new server patch 21.3 (and all other scripts that adds items in base list navigation bar).

The game added a reorder function for base list navigation bar and Infosticker add it self just there. Now the issue is that when user drag and specifically 'drop' a base button to reorder on the base list an error comes up because InfoSticker items don't have a getBaseId function. Now... fixing this problem is a pain in the neck. the 'drop' event is hard coded in the class costructor of webfrontend.gui.bars.BaseNavigationBar so no way (for now) for me to "patch" it. I can detect the new server patch and disable "draggable" base button to stop the errors. I have not deep digged yet in the code but the best solution ( to test) would be that beloved developers change the class costructor addlistener function to a more secure function. As for code

bp.push(br[i].getBaseId());

should become something like

"function"===typeof br[i].getBaseId&&bp.push(br[i].getBaseId());

. Not sure btw that this will solve all problems. @EE_Elephterion

nefrontheone

Remember, they are working in a recode of this "sort list base" option.
Actual version 21.3 is not finished.

o0netquik0o

@nefrontheone ah ok so it will not be added on 28 of July? Because the actual implementation will break functionality for people using infosticker

o0netquik0o

o0netquik0o wrote: »

Hi all! i find a unpleasant issue with InfoSticker script (last version) and

Ok Guys while waiting for a reply from developers i modded Infosticker script to fix the problem. As i couldn't find a way to patch the class costructor webfrontend.gui.bars.BaseNavigationBar, i modified Infosticker adding to BaseNavigationBar two more listeners for dragstart and drop and attaching there a "temporary self destruction" of infosticker to allow the game to do its work without issues. Then i reactivate infosticker. Things seem running smooth.

Want to try?
version 1.11.10.6
https://github.com/netquik/CnCTA-SoO-SCRIPT-PACK/blob/Testing/TA_Info_Sticker.user.js
UPDATE:
ok wait have fix something else
ok had to patch also reset order button function
I applied the same fix for the button that i suggested previously for the game data itself and it seems to work so if developers decide to run that "check" before calling getBaseId also my work is useless ahahah

you can test it now!
@nefrontheone @iguanaworld

nefrontheone

o0netquik0o wrote: »

@nefrontheone ah ok so it will not be added on 28 of July? Because the actual implementation will break functionality for people using infosticker

They have not given a date to deploy the new version in the PTE environment but my recommendation would be to wait for the final version of the code and if they cannot use InfoStickers in a single world, hold on for a bit, I don't think it is so critical.
Especially since that environment can be reset at any time.

o0netquik0o

nefrontheone wrote: »

They have not given a date to deploy the new version in the PTE environment

https://forums.ea.com/en/commandandconquer/discussion/273046/21-3-patch-maintenance-28th-july#latest and https://www.ea.com/it-it/games/command-and-conquer/command-and-conquer-tiberium-alliances/news/21-3-patch-notes-maintenance-18-july
yes but that code will go public if i'm not wrong ina few days.

Anyway here is another version of the fix... this time i removed my hard patch on game function and done the work differently. Infosticker just disable itself before dropping and before reorder button, then it comes up again. if someone want to test on PTE.

version 1.11.10.8
https://github.com/netquik/CnCTA-SoO-SCRIPT-PACK/blob/Testing/TA_Info_Sticker.user.js

o0netquik0o

update

https://github.com/netquik/CnCTA-SoO-SCRIPT-PACK/blob/Testing/TA_Info_Sticker.user.js

should work on "<=21.3" servers

nefrontheone

Who can test Info_Stickers in PTE to give @o0netquik0o a rating?

o0netquik0o

yes it should work fine in PTE and version <21.3 ... i have to do some little change but from my own test it seems working ( i added also a way to save the state of mcvPane.. after removing and readding).

https://github.com/netquik/CnCTA-SoO-SCRIPT-PACK/blob/Testing/TA_Info_Sticker.user.js

https://github.com/netquik/CnCTA-SoO-SCRIPT-PACK/blob/Testing/TA_Info_Sticker_SUPERCOMPACT.user.js

both version 1.11.10.9

P.S.
I will anyway push a new version of the pack for review before tomorrow. Infosticker should work normally on not patched servers. But on 28 it would cause problems if people start to try new reordering function of the game. Hope i can go public before that time. I'm speeding up because the pack has many new things in the code so not simple task. But i'm confident.

nefrontheone

Heh, heh, heh, there is a standard in every software development team:

"The author of the code cannot carry out the complete tests of the code"

If one person believes, another verifies that everything works as it should and on many occasions performs tests that not even the author himself had imagined.

o0netquik0o

Authors sometimes have go alone for good of community ... In any case the code is here. Testing on Firefox I found strange behaviour of that browser on the infamous script button hard coded in the game that fails on on obsolete pointer event of window navigator ... I just leave it alone. As long as know only one script use it in the way it was intended ...

AdeIina

https://ibb.co/Pg33WZT
It looks like something is wrong when upgrading buildings.

o0netquik0o

AdeIina wrote: »

https://ibb.co/Pg33WZT
It looks like something is wrong when upgrading buildings.

Hi are you sure you ave exact amount of resource to upgrade? as the requirement is rounded

AdeIina

> @o0netquik0o said:
> Hi are you sure you ave exact amount of resource to upgrade? as the requirement is rounded

It allowed me to upgrade at 12.38
The values you see in the picture changed in 10 seconds at 12.38 and then it allowed me to upgrade.
Whatever , it”s not a big deal for me but I thought you might want to know that something like this can happen.