Discussion Release Notes 1.179

[Deadeye Jerry]

Dear Humans and Elves,

Please see the Release Notes of our current game version here and let us hear your thoughts about it in this thread!

Kind regards,
Your Elvenar Beta Team

 

[Uffauffa]

Thanks @Deadeye Jerry
I am curios about this screenshot, made on last June 30th, during the “missing178gate”

Shouldn’t version 179 be already in use at that time?

 

[Heffernan]

Thanks @Deadeye Jerry
I am curios about this screenshot, made on last June 30th, during the “missing178gate”
View attachment 11548
Should version 179 be already in use at that time?

i have been confused about that also - why is there the zz… part visible at all ?
when events start it seems only the first part of version numbering (in this example 1.177….) seems to matter. here in beta world many players thought they had the right version looking at the zz part but nope, needed to update.
the zz part of version nubering is just window dressing it seems.

 

[Uffauffa]

@Heffernan , the only thing I’m sure is that zz means beta server. The following number should be the version in effect in that server.
For instance, in ITA server they add version 179, but is in use the version (it 1.178). Where “iit” means of course ITA server.

 

[Heffernan]

i’ve been under the impression that beta is a slightly higher/newer version than live worlds, but it doesn’t seem so. well, it does seem so if you look at numbering inside parenthesis but as i said in the end the zz part didn’t seem to mean anything really.

 

[Uffauffa]

You know the news? Now the version is (zz 180)…

 

[Heffernan]

You know the news? Now the version is (zz 180)…

yeah, and the announcement is 1.179
zz part is just window dressing

 

[Amy Steele]

zz means beta server

Indeed! In the screenshot above the 1.179 refers to the current beta browser version. By contrast, the 1.177 refers to the current beta mobile version. The beta mobile version is almost always one or two versions behind the browser.

i’ve been under the impression that beta is a slightly higher/newer version than live worlds

Also true. Live worlds are generally one version behind beta, as beta (browser) updates first, so that the new version can be tested, and as many bugs as possible fixed before the version is deployed on live.

It's important to know which version a particular platform (mobile/browser) or server (beta/live) is running, as the code differs between versions. It can also be important to know whether it's the latest version that's being used. So stating the beta browser version (which is always the latest/most up to date version) alongside the current mobile version enables that comparison to be made.

In the screenshot above, the 1.177 refers to the then current beta mobile version, whereas the 1.179 refers to the current beta browser version. Perhaps it would be better as
Version 1.177.0-ab6d91c-256 (zz browser 1.179)

 

[Uffauffa]

In the screenshot above, the 1.177 refers to the then current beta mobile version

And this is crucial, that’s why in browser it was possible to play the full event, while it wasn’t in app.
Thanks @Amy Steele

 

[Enevhar Aldarion]

In the screenshot above, the 1.177 refers to the then current beta mobile version, whereas the 1.179 refers to the current beta browser version. Perhaps it would be better as
Version 1.177.0-ab6d91c-256 (zz browser 1.179)

That has never been my understanding of what the versions mean. The 1.177 in that is the Live server version and the 1.179 is the Beta server version. It will show the same number whether I am on PC or mobile, Live or Beta, except Live only show the Live number and not also the Beta number.

 

[Karvest]

that's not browser version in brackets, but server version.

 

[Amy Steele]

that's not browser version in brackets, but server version.

Indeed! For the example above, 1.77 is beta mobile. At the same time, live browser would have been 1.178, since beta is usually 1 version ahead of live.
The mobile version is the same across beta and live. So when beta browser is 1.79, live browser is 1.78, and mobile (both beta and live) is 1.77.

 

[Heffernan]

aaaaaaaaaaaaarrrrrrrrrtgggghhhhhh!!!!
O.O now i don’t know what is what… and i don’t want to know anymore… forget i asked.

 

[Enevhar Aldarion]

Indeed! For the example above, 1.77 is beta mobile. At the same time, live browser would have been 1.178, since beta is usually 1 version ahead of live.
The mobile version is the same across beta and live. So when beta browser is 1.79, live browser is 1.78, and mobile (both beta and live) is 1.77.

When I log into my US account on mobile, it shows Version 1.178.0-c025e96-256 (us 1.178). When I log into the Beta server on mobile, it shows Version 1.178.0-c025e96-256 (zz 1.180). So no, the Live mobile version stays one or two updates behind the Beta mobile version, same as the browser does.

The browser for the US is v1.178.2-(6832d35) - html5 (2023-07-06 09:49) and Beta is v1.180-beta.4-(1e1242b) - html5 (2023-07-13 17:36).

 

[Karvest]

Mobile app version doesn't depend on browser version or server version (latter two are usually synced, though). You can easily play on almost any old app version, but it will be missing new assets (new buildings/effect types/mechanics/events/etc). That's why at some point server just send "client update required" and refuse loading without update to something more recent. And that cutoff can be different for beta and live - even if new app version is already published to stores, you can continue playing on live server using old app, but if you try to log in to beta - oops - update please...

 

[Droopy]

Due to the release notes on Live i noticed that the context menu has been expanded in the message system. (Did i miss the release notes on beta?)

But please keep things a bit consistent.

The context menu in the message system:

The context menu from the chat:

 

[Deadeye Jerry]

You didn't miss release notes on beta, sometimes when some bugs on live are fixed, the change on beta is made the day live servers are updated.