2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6

TheDog

There are hundreds of minor improves some of them are;

2.6 is

Its a lot faster than 2.5 - improved Computer player speed & AI turn processing
Status bar has a Territories units listed
map zoom to 200%,
unit cycling
Improved purchase panel, keeps your old purchases when you over buy.
xml has a new function isAI - great for making the AI appear better
Battle panel has a no retreat symbol, so kill them off first
Notes tab - removed from the right hand pane - only use Menu Help> Game Notes
Players tab has alliances are in bold

.
Bid system is different

buy units upto the maxBuiltPerPlayer limit
place infinite or stacking/placementLimit units per territory or sea zone
place land units in any territory you own (no 'factory' required)
place ship units in any friendly sea zone with ship(s) of the same owner already in it
Construction/immobile units placed obeys upgrade rules and canOnlyBePlacedInTerritoryValuedAtX
Units can only be placed if territoryEffect unitsNotAllowed allows them

hans

Here the error I got:
Welcome to an automated dedicated host service (a host bot).
If anyone disconnects, the autosave will be reloaded (a save might be loaded right now).
You can get the current save, or you can load a save (only saves that it has the map for).
Bot601_California: Jun 05, 2024 6:20:09 PM games.strategy.engine.framework.startup.launcher.ServerLauncher launchInternal
Bot601_California: SEVERE: Unrecognized error occurred. If this is a repeatable error, please make a copy of this savegame and report to:
Bot601_California: https://github.com/triplea-game/triplea/issues/new
Bot601_California: java.lang.RuntimeException: Exception on remote
Bot601_California: at games.strategy.engine.message.UnifiedInvocationHandler.invoke(UnifiedInvocationHandler.java:58)
Bot601_California: at games.strategy.engine.framework.$Proxy33.startPlayerStep(Unknown Source)
Bot601_California: at games.strategy.engine.framework.ServerGame.waitForPlayerToFinishStep(ServerGame.java:544)
Bot601_California: at games.strategy.engine.framework.ServerGame.runStep(ServerGame.java:407)
Bot601_California: at games.strategy.engine.framework.ServerGame.startGame(ServerGame.java:289)
Bot601_California: at games.strategy.engine.framework.startup.launcher.ServerLauncher.launchInternal(ServerLauncher.java:173)
Bot601_California: at java.base/java.lang.Thread.run(Thread.java:829)
Bot601_California: Caused by: java.lang.RuntimeException: Exception on remote
Bot601_California: at games.strategy.engine.message.UnifiedInvocationHandler.invoke(UnifiedInvocationHandler.java:57)
Bot601_California: at com.sun.proxy.$Proxy10.performMove(Unknown Source)
Bot601_California: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Bot601_California: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Bot601_California: at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Bot601_California: at java.base/java.lang.reflect.Method.invoke(Method.java:566)
Bot601_California: at games.strategy.engine.player.PlayerBridge$GameOverInvocationHandler.invoke(PlayerBridge.java:154)
Bot601_California: at com.sun.proxy.$Proxy10.performMove(Unknown Source)

hans

and now I uploaded apparently an out-of-date version

zlefin

Ok, I'm using 2.6.14748 and am getting a consistent crash upon making any move in a bot game. As are others (hans_; verified in both WaW and Revised maps on 2 different bots in different bot lines.

So I'm suspecting the problem is the bots being incompatible with people running 2.6,

It occurs to me I should ask in the lobby if anyone running any version of 2.6 is able to use the bots; data forthcoming

edit: noone has as yet reported a successful bot game with 2.6 line, but people may simply not be responding.
The crash occurs once a move is made in the game, not just on loading; a unit has to actually make a move for the crash to happen.
Hummel reports the same crashing issue with 2.6.14752

compass reports that playing 2.6 with lobby bots in the regular lobby was working up until a couple of days ago, when it stopped working, and he had to go back to 2.5 to get it to work.

Investigating the timeline of that, I note that 2 days ago there were no changes in the core triplea engine itself, nor any within 1 day of that. The engine versions show no number changes logged at that time, though curiously the version number shifts by 3, from 14748 to 14751

just keeping archival copies of discussion
"Compass: zeflin i was playing 2.6 till 2 days ago
Compass: then it didnt let me play
Compass: i had 2 start 2.5 to get playing again
zlefin: where you playing on the main lobby wher emost people were, or in a separate 2.6 lobby?
Compass: same lobby
Compass: i tried
simon33 has joined
Compass: but it didnt let me move as mentioned above"

LaFayette

Summarizing, it looks like mixing 2.5 clients with other 2.6 clients (or bots) does not work well.

My hope is that a 2.6 bot will not have these issues.

Getting that set up is needing a 2.6 lobby to be properly set up. That in turn is requiring some work

zlefin

Ok, well, let us know what you need.

Has anyone had issues with websockets when joinin the lobby btw? sometimes I'd join and get a websocket error so I couldn' talk or anything, other times it worked fine.

also did 2.6 change the default settings for where saves are located? cuz I thought my saves used to be near the autosaves, but now my regular saves are in a separate area from my autosaves when I go up the path to parent folders.

LaFayette

Re: release notes

Website is updated: https://triplea-game.org/release_notes/

@TheDog that was a killer summary you gave! Thank you, I copy/pasted most of it for the update.

As well, I forgot we had a set of release notes already in queue - so there are a number of detailed changes also listed (caveat, the detailed notes is not complete, we stopped adding to them some time ago)

LaFayette

also did 2.6 change the default settings for where saves are located?

I'm having trouble gauging how impactful this is. @zlefin would you mind clarifying if this is more an observation, a very small nuance, or perhaps annoying?

Alex might know for sure whether there were any changes/updates. 2.6 overall has a massive number of updates... I'm really curious what the answer is, but I'm trying to avoid jumping into researching an answer (2.6 lobby work is pretty urgent here)

Cernel

@lafayette I think "unit cycling" should be clarified. That was possible in 2.5 too and even before 2.0 (with the hot-key). I myself have no idea what that means so doubt many do.

Cernel

@lafayette Also, in the detailed listing there is a weird line with the first colon having the comment "Step 8 says I should edit the yaml. Did I do it right?".:face_without_mouth:

TheDog

@cernel said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:

@lafayette I think "unit cycling" should be clarified. That was possible in 2.5 too and even before 2.0 (with the hot-key). I myself have no idea what that means so doubt many do.

I looked backed through my notes, please remove "unit cycling" as even Im not sure what it means

zlefin

@lafayette

it is a mildly annoying detail; though I'm still not sure as to what caused it. It's annoying because it means I have to navigate folders more to switch between regular saves and autosaves; though I should be able to fix it by adjusting my settings. I just don't recall having to do it in the past, but I might be misremembering or just wrong as I didn't use autosaves much in the past due to not being able to direct host for home network reasons which changed recently.

It's definitely not important enough to overtake anything else.

LaFayette

@zlefin thanks for context

@thedog & @Cernel , appreciate the recommendations. There were some updates to unit 'cycling', I think it was something like the 'sleep' was removed or something that. I'm happy striking the line in the release notes. Do feel free to suggest edits to the document, log into github & you should see an option to edit this page directly (almost as if it were a wiki): https://github.com/triplea-game/triplea-game.github.io/edit/master/release_notes.md; it would certainly be helpful to me and the players to have someone polish up the text and make any needed corrections.

TheDog

@lafayette
Hopefully removed line 75 below
Step 8 says I should edit the yaml. Did I do it right?

It probably needs approval.

zlefin

observation: the crash issues from mixing 2.5/2.6 only apply if you are a player in the game; if you're an observer not playing any of the nations, then crashes do not occur. I was able to observe games, both direct hosts and lobby bots, without crashing either of them.

LaFayette

@thedog I merged the update. Hehe, when I read your response, I thought you were asking "did I do it right?" = D

Panther

@LaFayette

Currently - as of typing this - the "Download"-buttons on https://triplea-game.org/download/
point to 2.5.22294 again - obviously silently, without any further info or note to the users.

Is the roll-back to the previous ('stable') release intended?

Shall we encourage players who updated to the recently offered '2.6.stable' encourage to revert back?

Cernel

@panther The serious problem is only for bot-users right? Anyone who does not use bots has no reasons not to get 2.6 correct?

Panther

@cernel
I have no idea, that is why I asked. But if that's the case, I know what to do (or not to do). Thank you.

FlyingBadger

Thanks to everyone for their hard work on 2.6, love some of the new features:

Potential scramble warning
Showing units in a territory in the status bar
No retreat symbol when picking casualties