PTE & 19.2 issues

gamerdruid · April 22, 2019 10:48AM

• The home marker should now correctly point to the last base you visited

This does not happen....... Still points to the previous base that shot a forgotten base, not a base that had been selected and viewed.

pulstar_ru · April 24, 2019 1:03PM

He he he he. I'm - [Player_2459370]:

M8u8r4r4a0796 · April 24, 2019 4:32PM

the PTE is showing leo stat passwords instead of names

gamerdruid · April 24, 2019 5:01PM

If you log out and back in again the player number should change back to your player name. Mine did!

iguanaworld · April 25, 2019 8:03PM

Today, when I entered one of the worlds that I play, in the "My games" tab, the PTE world did not appear.
Using the link that @gamerdruid has in the forums I was able to access the PTE world but my name appeared as player_xxxxxx and the PTE world still did not appear in my list of worlds.
I decided to go back to the previous page and then move on to the next page (it would be something like going back to the previous world and then going back to the PTE).
At that moment my name appeared again correctly and the PTE world was added to the list of worlds.
Is it normal ?

gamerdruid · April 25, 2019 10:43PM

This is a result of a recent update to fix issues - yes it is 'normal' *ie happens for everyone* and once your player name is showing correctly it will continue to do so. PTE will show on the list of worlds and as the most recent world (if it is the most recent). It is a one time error.

Keyser_888 · April 26, 2019 7:20PM

If the MoveRecoveryCheat also would reset the attack recovery 10 field move limit in PTE... it would be nice

Buggy?!?
The very first attack I had was really slow and would not launch. After restarting it would work, but not until a couple of minutes after logging in.
I restarted next time and I could attack straight away so it might have been a local problem with me, but if (when!) that happens in game that an attack won't lauch during PvP, 1+ minute of not being able to attack after logging in would mean you'r dead...

I have had it happen in game on earlier server as well that it would freeze while attacking, and especially in PvP (of course!) otherwise I would not have mentioned it here yet until testing it more.

And Yes Gamerdruid, It was both with and without scripts & Tampermonkey

Started to turn it all off during PvP just to be sure.

/Key

gamerdruid · April 28, 2019 5:16PM

BUG Report: The badges earned for killing the fortress are not showing correctly when on the PTE. Many badges are missing but show OK on other worlds.

gamerdruid · April 30, 2019 8:38AM

• Currently, level 1 defense units will be displayed as disabled for players of the opposite faction when spectating a base, even if all requirements are met and the units will be active during combat. This is a visual bug and does only affect level 1 units.

The visual bug is showing only some units as disabled.

EE_Elephterion · April 30, 2019 9:25AM

gamerdruid wrote: »

Default defense units, Walls and Scorpion/MG-Nest that have no research dependency are not affected afaik. Any other units i am not aware of?

gamerdruid · April 30, 2019 3:04PM

Unfortunately the base I was looking at has now being killed - and is unlikely to return - so I'm not sure. It was a NOD base and had infantry of some kind showing OK, not as as disabled.

I'll do a little research........
and the result of that research was that the bug is now fixed - or at least not visible to me!

iguanaworld · May 5, 2019 11:40AM

One of the novelties of version 19.2 is to show the number of supports that are on our base when we are attacking?

Is it normal for a text to appear instead of a number (perhaps the name of a variable)?
I think that "tnf:" is because the location is missing, right?
I'm using the last version of Chrome: Version 74.0.3729.131 (Official build) (64 bits)

gamerdruid · May 5, 2019 3:01PM

The text disappears if a support is on the base. I'm not sure if the text is meant to be visible or a 0 showing.

The tnf: is because something is missing in their setup - they are aware of this. Before it is rolled out later this week it should be fixed.

EE_Elephterion · May 6, 2019 1:01PM

It seems the Support Summary has its display triggered by MoveCooldown or other Altert states of a base.
This will unlikely get fixed in 19.2 I think.

The tnf: is related to the localization of the window description. I'm looking into why that is currently not properly displaying a translation.

Retired_XDaast · May 7, 2019 8:39PM

I know its no concern of Envision but The Movement script by petui has been broken by 19.2. Please let me know if a fix is found.

Keyser_888 · May 8, 2019 7:21PM

I think they may have changed the way they collect the ID for the bases, camps, etc.
I don't see the city_id anymore on PTE when turning on 'Show Debuginfo'

Du you know Elep?

EE_Elephterion · May 9, 2019 9:46AM

Which script are you using to enable the Debug Information to begin with? I'm not aware on changes in that regard.

Keyser_888 wrote: »

I think they may have changed the way they collect the ID for the bases, camps, etc.
I don't see the city_id anymore on PTE when turning on 'Show Debuginfo'

Du you know Elep?

nefrontheone · May 9, 2019 12:27PM

EE_Elephterion wrote: »

Which script are you using to enable the Debug Information to begin with? I'm not aware on changes in that regard.

I only can view this error of The Movement script in PTE:
And the buttons for the script don't appears:
In other worlds works and not error is showed.

nefrontheone · May 9, 2019 12:46PM

I'm not a developer, sorry, but…
can the fault be in this line ?

Retired_XDaast · May 9, 2019 2:34PM

Yes, that is where the error occurs.

PTE & 19.2 issues

Replies

Howdy, Stranger!

Quick Links