With the recent series of patches that came from the PTE, when would we expect a world reset for the PTE? Can anyone give me a prediction on what month it might occur in?
I don't think there is currently a certain date.
This world is for testing and as it is notified when entering it, it can be restarted at any time for the needs of the developers.
There are times that it has lived two weeks and some have reached about six months.
In other words, unpredictable.
Not a part of EA / Envision teams - My comments are only mine.
Totally unpredictable. The last time I asked the answer was 'no current plans'. 21.4 isn't finalised yet so a reset is less likely, unless they wish to finalise it on a new world.
I am not an employee of EA/Envision. The views expressed are my own!
No, it means it's unpredictable what will come and when. @EE_Elephterion has already referred to a WCS coming in the announcement for this PTE so it is actually very likely one will come sometime before 31st December 2021!
I am not an employee of EA/Envision. The views expressed are my own!
We will be patching PTE 21.4 tomorrow with the fixes for the discovered bugs affecting substitution permissions for markers/invites. Maintenance will commence around 07:00 to 09:00 UTC.
We haven't really been able to reproduce the issue with messages containing links that @iguanaworld reported so this will prolly be spared for now.
A little late now, but did you view the 'more information' link and what did it say?
In google help replies:
Chrome error code 5
Memory leak "Chrome Error 00005": the consequences of a Google Chrome memory leak involve a malfunction of the operating system. Possible causes include Google Inc.'s failure to deallocate memory in the program, or when faulty code is executing an "infinite loop."
And...
Post edited by nefrontheone on
Not a part of EA / Envision teams - My comments are only mine.
A heads up, we got another small update online in 10 minutes, at 09:30 UTC that fixes the Protection Bubble Loss message being displayed when it should not.
It seems to be FIXED! ~I'll keep testing but I see no reason for it not to be declared fit for purpose!
Have you tested all test cases?
- Enter a new player to the world and move his base
- Move a recent created base
- Move a respawned base (after enemy's destruction)
- Relocate to another sector (thanks @gamerdruid)
- any more?
Post edited by nefrontheone on
Not a part of EA / Envision teams - My comments are only mine.
A forgotten base began to attack me in a four-wave zone and I returned fire until it was destroyed.
It couldn't launch its fourth wave because it had been destroyed, great !!
Edited:
I don't know if it is a correction of this version but I think it is fantastic that it is no longer an independent routine that allows a forgotten destroyed base to continue attacking even if it does not exist.
It seems to be FIXED! ~I'll keep testing but I see no reason for it not to be declared fit for purpose!
Have you tested all test cases?
- Enter a new player to the world and move his base
- Move a recent created base
- Move a respawned base (after enemy's destruction)
- any more?
Of course I haven't tested every single variation. (I would expect the developers have done that, that's part of their job!) The most common incarnation of the error was when you relocated to a new sector then moved beyond the level 20 area.
In some cases the bubble is intended to burst.
When you enter a new player to the world and move that base beyond level 20 it is intended that the bubble goes.
When you move a recently created base beyond level 20 then it is intended that the bubble goes (I think) and also when you move it within an area that is beyond level 20.
The problem isn't the bubble going - it was the message showing when it shouldn't. If it is intended to remove the bubble shield then of course the message should be shown.
EDIT: I was able to check a respawned base after destruction by forgotten. The bubble message doesn't appear nor the bubble disappear.
Post edited by gamerdruid on
I am not an employee of EA/Envision. The views expressed are my own!
Replies
As for replacing a commander-in-chief, I agree with @iguanaworld.
This world is for testing and as it is notified when entering it, it can be restarted at any time for the needs of the developers.
There are times that it has lived two weeks and some have reached about six months.
In other words, unpredictable.
Thx
DEATHDEALER
We haven't really been able to reproduce the issue with messages containing links that @iguanaworld reported so this will prolly be spared for now.
Sent privately more info to detect the fail. Thank you.
Show "Error 5"
With Chrome last version. (Version 95.0.4638.54 (Official build) (x86_64))
Note1: And no, I wasn't touching any other game or tab or anything other than the game
Note2: After a refresh page game works normally again (and I continued with the attack).
In google help replies:
Chrome error code 5
Memory leak "Chrome Error 00005": the consequences of a Google Chrome memory leak involve a malfunction of the operating system. Possible causes include Google Inc.'s failure to deallocate memory in the program, or when faulty code is executing an "infinite loop."
And...
Nope, sorry. In the middle of the battle only refreshed page and back to combat... O:-)
Have you tested all test cases?
- Enter a new player to the world and move his base
- Move a recent created base
- Move a respawned base (after enemy's destruction)
- Relocate to another sector (thanks @gamerdruid)
- any more?
A forgotten base began to attack me in a four-wave zone and I returned fire until it was destroyed.
It couldn't launch its fourth wave because it had been destroyed, great !!
Edited:
I don't know if it is a correction of this version but I think it is fantastic that it is no longer an independent routine that allows a forgotten destroyed base to continue attacking even if it does not exist.
Of course I haven't tested every single variation. (I would expect the developers have done that, that's part of their job!) The most common incarnation of the error was when you relocated to a new sector then moved beyond the level 20 area.
In some cases the bubble is intended to burst.
When you enter a new player to the world and move that base beyond level 20 it is intended that the bubble goes.
When you move a recently created base beyond level 20 then it is intended that the bubble goes (I think) and also when you move it within an area that is beyond level 20.
The problem isn't the bubble going - it was the message showing when it shouldn't. If it is intended to remove the bubble shield then of course the message should be shown.
EDIT: I was able to check a respawned base after destruction by forgotten. The bubble message doesn't appear nor the bubble disappear.
Congratulations!