2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6
-
@alexei-svitkine said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
My goal is to try to get 2.6 to a level where there are no regressions over 2.5 so we can just release it, making the stable version benefit from all the improvements over the last few years.
Maybe it is worth to point out what the improvements really are, that players profit from .
I mean there have been countless merges of PR that certainly mean something to developers but are only cryptic for players.
Have there been changes with impact on game rules? Is there something to playtest against rules compliance? Have there been noteable improvements of gameplay?
What actually needs to be tested?Apart from of course welcome specific detail interests of map makers - are there any improvements for the playing communities that come with 2.6?
Being one of the few persons who were or maybe still are interested in trying to follow development I unfortunately got lost at an unspecific point in the past, personally.
-
@panther
Of note for 2.6, not an improvemen as such, but something to be aware of- map folders are now played unzipped
- new, use of a map.yml file for control
https://forums.triplea-game.org/tags/thedog
https://forums.triplea-game.org/topic/3741/curated-best-top-maps-triplea-guides -
@rogercooper said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
@alexei-svitkine New mods are not appearing. I updated TripleA this morning.
Do you mind giving an example of something that's missing from 2.6?
-
@thedog said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
@panther
Of note for 2.6, not an improvemen as such, but something to be aware of- map folders are now played unzipped
- new, use of a map.yml file for control
Thank you, that is something that I am actually aware of.
I am thinking in the heads of players/users and I am searching for something that could encourage the community to update and what specifically might need to be tested before. It is usually me who encourages the players on the other forum to update TripleA when a new "stable" is released.
As the new "stable" still will not allow for PBF with current NodeBB-versions I would really need some good arguments.
Otherwise I would agree with @wc_sumpton . If there were no "big points" for the players there would be no need to release and 'officially' promote a new stable release.
It is important for me to point out that I am not complaining - I just need some informative input, please.
Don't always trust TripleA when it comes to rules questions. Know the rules before you start … and better check what TripleA has done.
-
If you were working on improvements to a map, would you like other people to tell you "no, there's no reason to release a new version" or would you rather the improvements make it into the hands of players?
(That's why I started looking at the state of 2.6 recently - as I'd like to get the stuff I've worked for in the hands of players.)In terms of what's in 2.6, I can't speak to all the other changes, but here are some of the big ticket items I've contributed:
- The unit status bar so when you mouse over a territory, you can quickly see what units are there (very useful on crowded maps)
- Much faster AI. Makes a huge difference on some maps, like Domination 1914. Just try 2.5 and 2.6 side by side with Hard AI and see how they progress.
- Much faster battle calc - for example, e.g. on some maps like 270BC it would take tens of seconds to just bring it up before.
- Lots of fixes for random errors and crashes that currently exist in in 2.5.
- Major improvements to memory use.
The other reason for releasing it is that it would provide a new "stable" checkpoint, so that any new work can be compared to that, instead of bundled with lots of other unreleased changes as it is the case in 2.6 right now. By sitting on a lot of unreleased changes, it increases risk for the project as without full vetting via a release, bugs can creep in that may be very hard (i.e. taking a lot of time) to resolve later.
-
@alexei-svitkine said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
@rogercooper said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
@alexei-svitkine New mods are not appearing. I updated TripleA this morning.
Do you mind giving an example of something that's missing from 2.6?
Here is a list of recent mods, none of which I can download. I posted most of these myself but not all.
Election_Usa Public
HTML 0 0 0 0 Updated yesterday
World_War_II_Halifax Public
HTML 0 0 0 0 Updated last week
pacific_1942 Public
HTML 0 0 0 0 Updated last week
uhd_world_war_ii_global Public
HTML 0 0 0 0 Updated 2 weeks ago
CCLXXbc Public
HTML 0 0 0 0 Updated 2 weeks ago
NSP_v4 Public
HTML 0 0 0 0 Updated 3 weeks ago
wwiinazithreat Public
HTML 0 0 0 0 Updated last month
churchills_1939 Public
HTML 0 0 0 0 Updated on Jun 8
The_World_at_War Public
HTML 0 0 0 0 Updated on May 31
world_war_ii_v6_1941 Public
HTML 0 1 0 0 Updated on May 27There is also mod that I can download called "Test Map" that causes an error if it is downloaded. It should be fixed or removed.
-
@alexei-svitkine said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
If you were working on improvements to a map, would you like other people to tell you "no, there's no reason to release a new version" or would you rather the improvements make it into the hands of players?
Second alternative for sure. That is why I was asking for information about the improvements!
I explained before that I at an unspecific point failed to keep track, as there were so many merges - cryptic at least to me. -
@wc_sumpton said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
Adding such features, when requested by map makers, would allow that release to be tested. Not adding anything, means there is no reason to test future releases. Thus no "push" for that release.
Respectfully it may be a more complex picture regarding testing. The issue with code is that the complexity of updates grows combinatorically. Think of code as a puzzle where the puzzle pieces are super complex shapes and can connect to 30 some other pieces. Moving one piece around means you need to take care of the 30 other pieces that it connected to, and in turn each of the 30 pieces that those connect to. A good code base will try to minimize the puzzle piece connections. TripleA is not that.
Hence, there is a concept of "regression" testing, where very easily the existing puzzle pieces might have been disturbed and no longer working. This is in part what makes it so difficult to update code compared to the ease of creating new code. A great example is where we discovered that the bots were broken in 2.6 very far after the fact. Absolutely no new features there, an existing thing being broken, and we did not know about it until we tried to do a production launch.
In sum, there are many kinds of testing, "feature" or "user" testing I think is what is being thought of here. "Regression" testing is the biggest burden for TripleA and is a giant task that repeats when there are updates. Overall, regression testing properly takes several days; feature testing can take a dozen minutes to accomplish. The 'feature' testing is useful, what we really needed help with here was regression testing. The bot compatibility issue was harder to find of course because it required players to connect to a 2.6 lobby, and nobody really did that (it was a miss).
-
To keep this thread on track, the big 2.6 blocker is the network compatibility issue that makes bots unplayable. The issues with maps not working are generally known problems that can be fixed. Those fixes are inconsequential until we get that network compatibility problem figured out.
-
@lafayette said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
To keep this thread on track, the big 2.6 blocker is the network compatibility issue that makes bots unplayable. The issues with maps not working are generally known problems that can be fixed. Those fixes are inconsequential until we get that network compatibility problem figured out.
If you're talking about the bot issue, then I believe it should be fixed now. See: https://github.com/triplea-game/triplea/issues/11751
-
First off, thank you for all the work you've done. Refactoring, given the current state of TripleA, is not an easy task. @LaFayette is correct, testing such changes can be time consuming. And @Panther is also correct stating that there seems to be very little reason for the community to migrate to a new release. And you, also, have a right to see all your efforts enjoyed by the community.
TripleA has be in "Feature Lock" mode since prior to 2.5 release. As of now I know of 4 different maps being developed. And just recently @ebbe here asked about something, which if done would help with his project. Providing such functionality would require him to continue using and testing a pre-release version. isAI() is already a method. Creating a condition that checks this has been requested many times.
All I'm saying is 2.6 needs testing. Give map makers something to test, and then the community will follow. Staying "Feature Locked" for almost 2 years doesn't help the community grow.
Cheers...
-
@rogercooper said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
@alexei-svitkine said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
@rogercooper said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
@alexei-svitkine New mods are not appearing. I updated TripleA this morning.
Do you mind giving an example of something that's missing from 2.6?
Here is a list of recent mods, none of which I can download. I posted most of these myself but not all.
Election_Usa Public
HTML 0 0 0 0 Updated yesterday
World_War_II_Halifax Public
HTML 0 0 0 0 Updated last week
pacific_1942 Public
HTML 0 0 0 0 Updated last week
uhd_world_war_ii_global Public
HTML 0 0 0 0 Updated 2 weeks ago
CCLXXbc Public
HTML 0 0 0 0 Updated 2 weeks ago
NSP_v4 Public
HTML 0 0 0 0 Updated 3 weeks ago
wwiinazithreat Public
HTML 0 0 0 0 Updated last month
churchills_1939 Public
HTML 0 0 0 0 Updated on Jun 8
The_World_at_War Public
HTML 0 0 0 0 Updated on May 31
world_war_ii_v6_1941 Public
HTML 0 1 0 0 Updated on May 27There is also mod that I can download called "Test Map" that causes an error if it is downloaded. It should be fixed or removed.
I tried looking for these with 2.5 and also didn't see them. Are you sure they're posted correctly?
If they can be downloaded with 2.5, can you give me the category and map name in the download list one of these shows up as and I can investigate? -
However, looks like downloads are just broken on 2.6 right now due to a server issue? I'll file a bug on github.
-
If we want to entice players to migrate from 2.5 to 2.6 there is a one feature request that affects about 1/4 of the maps in the map downloads so about 50 of the 200+ maps.
It would make the purchasing of these units less frustrating as getting it wrong cancels all your purchases.
It is this
- maxbuiltperplayer has ≤ on the purchase panel for each unit
- the aaGun doesn't have a maxBuilt rule and hence no limit is displayed in the label
- current unit count has been appended to the end of the Production tooltip (which makes the info easy to scan). It has been suggested this info can be useful to plan production count 2
- infantry was maxed out using the max button.
- production capacity is displayed on the panel at the bottom left 5/8 = 5 units currently purchased out of the 8 maximum production/placed allowed (if applicable)
https://forums.triplea-game.org/tags/thedog
https://forums.triplea-game.org/topic/3741/curated-best-top-maps-triplea-guides -
@thedog said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
If we want to entice players to migrate from 2.5 to 2.6 there is a one feature request that affects about 1/4 of the maps in the map downloads so about 50 of the 200+ maps.
It would make the purchasing of these units less frustrating as getting it wrong cancels all your purchases.
It is this
- maxbuiltperplayer has ≤ on the purchase panel for each unit
- the aaGun doesn't have a maxBuilt rule and hence no limit is displayed in the label
- current unit count has been appended to the end of the Production tooltip (which makes the info easy to scan). It has been suggested this info can be useful to plan production count 2
- infantry was maxed out using the max button.
- production capacity is displayed on the panel at the bottom left 5/8 = 5 units currently purchased out of the 8 maximum production/placed allowed (if applicable)
Thanks for the reminder about this. It's super frustrating because the author of that prototype actually coded a bunch of that functionality and had it working, but never actually shared the code I believe and them disappeared. So we have to redo it from scratch.
-
-
If they can be downloaded with 2.5, can you give me the category and map name in the download list one of these shows up as and I can investigate?
I don't even 2.5 installed and the mods I have uploaded are being done in 2.6 style.Before downloads failed entirely, all mods were listed without categorization.
-
I've been playing 2.6 for a couple months now and from the SP perspective it seems like a pretty good upgrade.
To me the biggest selling point is the map zoom, AI/calc speed which seems pretty significant, and status bar (for that last current owner might also be nice in the list, in case the tile is contested for maps that use a battle round limit, or where multinational forces are in the same tile stuff like that, pretty much everything else is listed right there in the status for the quick glance). I've yet to encounter an error that crashed me out in 2.6 SP and I like how the folders are organized. It still seems more to me like 3.0 almost. So maybe if we want people to check it out we just skip ahead into the 3 territory? I mean what's in a name right haha.
But I agree with others that PBF would be key. Seems like promo-ing it before that and the bots and the git mod thing is resolved would be kinda premature, cause I think a lot of players are hoping for that out of a stable right?
-
@panther said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
As the new "stable" still will not allow for PBF with current NodeBB-versions I would really need some good arguments.
Are you saying the latest pre-release no longer works for PBF?
-
@redrum said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
@panther said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
As the new "stable" still will not allow for PBF with current NodeBB-versions I would really need some good arguments.
Are you saying the latest pre-release no longer works for PBF?
You might have noticed it, as you are playing at A&A .org. Pre-releases used to work for a while - but there are issues - maybe related to current NodeBB versions of the forum software - that need to be fixed. Current pre-releases do not work, indeed.
An unexpected error occurred!
IllegalStateException: Error, bad server response: HTTP/1.1 500 Internal Server Error; JSON: {“path”:“/forums/api/v2/users/2494/tokens”,“error”:“Blob is not defined”,“bodyClass”:“page-forums page-forums-api page-forums-v2 page-status-500 theme-persona user-guest”}
Don't always trust TripleA when it comes to rules questions. Know the rules before you start … and better check what TripleA has done.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login