@beelee

Understand, I read that and pulled part of your reply into the other thread.

If I understand the rules that you are referring to Paratroopers only receive their bonus support when they are only attacking alone, and only for 1 round of combat. That is why I don't think @Azimuth idea for using "whenHitPointsDamagedChangesInto" will work, because other attacking units need to be considered.

Rule quoted in question:
When Paratrooper units attack by air the attack
factor is “3” in the first round of combat.
From the second round of combat the attack
factor is “1”.
If Paratroopers attack by air and are supported by
units other than Paratroopers, the Paratroopers
attack at “1”.

So, when a Paratrooper attack only with other Paratroopers, they attack at 3, when supported by other units they attack at 1. This would require a self-support, plus a cancelation support from other units. Both would need max round limited to 1:

<attachment name="supportAttachmentParatrooperSelf" attachTo="Paratrooper" javaClass="UnitSupportAttachment" type="unitType"> <option name="unitType" value="Paratrooper"/> <option name="faction" value="allied"/> <option name="side" value="offense"/> <option name="dice" value="strength"/> <option name="bonus" value="2"/> <option name="number" value="1"/> <!-- New option to check for rounds --> <option name="maxRounds" value="1"/> <option name="bonusType" value="ParatrooperSelfSupport"/> <option name="impArtTech" value="false"/> </attachment>

Would this help?

Cheers...

@jkprince interesting

It's not that bad to add the preview image, particularly now that it's standardized. This file:
https://github.com/triplea-game/triplea-game.github.io/blob/master/maps/maps.html

With the below modifications (note the new img block):
6483066e-429b-4c1f-8e49-ef41406cf4ba-image.png

Looks like this:
b998cdcf-acca-4e08-bb9d-31ae6c4401ed-image.png

Is there anyone good with CSS that can style this up more nicely?

I don't have bandwidth to help here. The updates look good. Replacing the files in the map repository should be do-able with some googling and small determination.

@black_elk said in Contextutal unit sprite "animation":

reading a rulebook manual in the notes seems somehow less compelling than Victoria breaking it down for us.

Yes

Victoria should get the job

Yeah it's an interesting dilemma, and one that I didn't encounter until attempting to upscale a WW2 game for to play on a WQXHD screen (1600p). Standard QHD still works reasonably well, provided the map images themselves are large enough. It works alright at 1440 even with no upscaling of the font from 100% to 125%, cause the UI is still large enough there, and the actual font sizes in game can be increased within tripleA. But it gets harder as you go up in res.

This is one my favorite graphics on wikipedia
https://en.wikipedia.org/wiki/4K_resolution#/media/File:Vector_Video_Standards8.svg

The hard and fast rule is that the new standard will give 4x the size and 2x the resolution, over whatever previous standard. The previous standard in this case would be FHD at 1080p which most peeps still use for gaming, like especially on laptops. Also there are features like DLSS and whatnot to smooth over this transition in gaming, though obviously tripleA isn't the sort of game we're talking about there really.

Also, the issue is going to be less pronounced if one were say running tripleA through a giant TV or a projector which will soften the visual, as opposed to say a laptop or gaming monitor where the user is right up on top of the screen.

The issue is not for all images in tripleA, just the graphics inside the UI itself. So for example the map visualization (or anything displaying within the map field of view) this stuff all upscales normally. Using a higher resolution image for the map, you will see that scrolling around the map will be very clean. Just like watching a TV show at 4K or at a higher framerate, you'll see less motion blur when dragging around the map in the UI. This is actually pretty cool, and will instantly make the player feel the upgrade, but then the UI graphics works against that feel (map will look ultra clean, but UI will have that jank.)

Some of our larger maps (larger in terms of pixel height/width) should be fine. For example the UHD global map even at like 5K ultra wide or 5K UHD will still work, because the map image is tall enough that the player will still be able to zoom out to a 50% mapview at least. The text in the UI will also work fine at that scale, because of the way font scaling works (basically as vector for fonts) but the tiny images in the UI, say units or icons upscaling as raster, those will hit the ceiling very quickly when doubling like that.

Also maps which are not tall enough to allow any pulling out in mapview will become sort of unusable without an upscale to the map dimensions. So for example one of our smallest maps is v3, it was drawn back when many monitors where still at aspect 4:3, or when HD 720p and widescreen displays were still relatively new. If you imagine playing a map where the zoom is locked at max zoom-out, with no scrolling/dragging (no zoom in/out from there) you can get a feel for the issue. For the actual maps, we can deal with this by upscaling the map image (basetiles/relief) outside of tripleA to produce a larger/cleaner image, but for stuff like unit icons we're much more limited. 54px is a hard ceiling right now, we can provide a larger upscaled graphic with interpolation, but the game will simply crop it inside the UI.

To me the minimum for anything UHD inside tripleA is at least some give for the map zoom. It needs to have somewhere to go from 100% mapview there (e.g. the map image needs to be larger than the intended screen's display). If not, then the only real option there is to downscale the display resolution of your screen. We have a little play here, because tripleA 2.6 can zoom to 200% mapview now, but there's still an issue anytime the screen and the map image approach 1:1, since your zoom out will just be the map at scale taking up the entire screen at once. Ideally you'd want the map to be at least twice as tall as the intended display, so that the drag and zoom stuff feels normal, but this is limited by the UI upscaling. In short a UHD map would still be serviceable at much higher resolutions say 5K or 8K possibly (even if the map scaling range isn't nearly as broad) but the UI is going to get stuck (for anything other than Font), and start bumping heads on that ceiling.

@ice1 said in quality of life improvements:

QOL improvement would be a given choise to which carrier you want to land your plane (similar to a transport, and the option to SEE on which carriers wich planes are located with the territory TAB

2nd is in line with first, see which units are on whitch transport with the territory tab

I believe that one should be able to see of which ship any (air or land) unit is cargo (if it is) by just looking at the board (so without having to look at the Territory tab provided that there are enough placement spots to display all the units in the zone).

A way may be to have a line connecting any unit which is cargo of a ship with the ship, though it would be much better if such cargo units are always drawn as near as possible to their ships. I've no idea if this is feasible.

@beelee sent you PM

@lafayette

0638e671-989c-483b-bc27-56fe9d0abab0-afbeelding.png

@bluelionman said in Thoughts on playing TripleA / AI:

Besides in the board game Heavy Bombers got 3 dice, online (TripleA) it's 2 which is better as 3 is far two powerful.

Under V3 rules, you roll 2 dice per heavy bomber and hit only once if at least one of the two dice hits or use the higher of the two results for bombing raid damage.

How heavy bombers work in "Big World 1942 v3" is wrong if it is actually supposed to be V3 rules.

There are four problems with documenting techs in notes.

Our correct understanding of the rules may change overtime (because of clarifications from the rules makers or even official errata). This would require a program change, and, if each game has tech documentation in notes, one would have to update them all singularly or leave them outdated. TripleA may (and actually does) implement the tech rules incorrectly, which would create the problem of whether in notes you should document how the game should work or how it works. The game-maker may make mistakes in documenting tech in notes, which would create or add to the problem of whether players should try to play by the notes or as per what the program does. Tech may create complex situations, so it is something for which it is hard to be clear and exhaustive.

However, I would agree that every game should provide the full rules-book for the game (which means fully documenting the techs too).

This said, you can find tech documented in some V3 rules games. For example, this is what you can find in the "World War II v3 1941" game-notes,

Technology *** Air/Naval Tech *** SUPER SUBS- subs attack at 3 JET POWER- fighters attack at 4 IMPROVED SHIPYARDS- naval units are cheaper AA RADAR- AA hit on 2 or less LONG RANGE AIRCRAFT- aircraft range increased by 2 HEAVY BOMBER- roll 2 dice for each bomber attack *** Land/Production Tech *** IMPROVED ARTILLERY SUPPORT- artillery support 2 infantry ROCKETS- AA conduct rocket attacks for 1d6 damage to production (each factory may only be targetted once per turn by one rocket, and only 1 rocket in each territory may fire) PARATROOPERS- each bomber may carry 1 infantry into combat (must stop in first enemy territory it reaches) INCREASED FACTORY PRODUCTION- factories produce 2 additional units (if territory value is 3 or greater), repairs 1/2 price WAR BONDS- collect an 1d6 extra PUs each turn MECHANIZED INFANTRY- tanks may carry 1 infantry each for 2 spaces

and this is what you can find in the "WWIIv3 1941 Move-Buy-Move" game-notes.

Technology *** Air/Naval Tech *** SUPER SUBS- submarines attack at 3 JET POWER- fighters attack at 4 IMPROVED SHIPYARDS- submarine, transport and destroyer costs reduced by 1; cruiser cost reduced by 2; carrier and battleship costs reduced by 3 AA RADAR- AA guns hit on 2 or less LONG RANGE AIRCRAFT- aircrafts range increased by 2 HEAVY BOMBER- roll 2 dice for each bomber in attack, but use only the lowest one, and 2 dice for each bomber in bombing raids, but use only the highest one *** Land/Production Tech *** IMPROVED ARTILLERY SUPPORT- artillery support 2 infantry ROCKETS ADVANCE- AA guns conduct rockets attacks, with a range of 3, for 1d6 damage to production (each factory may only be targeted once per turn, and only 1 AA gun in each territory may fire) (AA guns conducting rockets attacks can't move) PARATROOPERS- bombers may carry 1 infantry each into hostile land territories only (both units must begin their movement in the same territory; the bomber can't make a bombing raid; the bomber must stop its Combat Move movement in the first land territory it enters that was enemy owned at start turn; if the attacked territory has only AA guns and no other defending units, the AA guns are automatically captured without firing; if the bomber is hit by AA guns, the infantry it carries is also destroyed; paratroopers alone have no way to retreat; if retreat is possible, paratroopers retreat together with all other retreating land units) INCREASED FACTORY PRODUCTION- factories produce 2 additional units, if territory value is 3 or greater; repair 1/2 price, rounded up WAR BONDS- collect 1d6 extra PUs each turn MECHANIZED INFANTRY- armours may carry 1 infantry each

As an example of what I was saying at point 2, you can notice that the "if the attacked territory has only AA guns and no other defending units, the AA guns are automatically captured without firing" rule for the "Paratroopers" is how the game works but not how the rules are supposed to work (The AA guns should actually be able to fire in this case too.).

I'd let @Panther check that what I wrote and pasted is all correct if he will.

@stu_the_k said in Bids system still here?:

I grew up in Detroit

@stu_the_k said in Bids system still here?:

so I was also busy getting an early Xmas present from the Lions

👍

Been here all my life!!

Cheers...

I like this idea, was thinking of it as a "same luck" option.

Suggested updates to PoS2 for isAIPlayer:

In the "<!-- National Objectives and Condition Attachments -->" area, line 2939 between "switch" and "turns" (which should be updated to "rounds":

<!-- National Objectives and Condition Attachments --> <!-- ... switch values: "true" or "false" (default is true). This is just a simple on/off switch, which gives map makers some memory function for their conditions. isAIPlayers values: "true" or "false" check if player is AI controlled. rounds values: which rounds this will be checked on (example: value="1:4:6-8:11-+" means rounds 1,4,6,7,8,11, and all rounds after 11) ... -->

And then "conditionAttachment_Americans_Aid_UK" can be changed to reflect the usage:

<attachment name="conditionAttachment_Americans_Aid_UK" attachTo="Americans" javaClass="games.strategy.triplea.attachments.RulesAttachment" type="player"> <!-- is the Americans not AI controlled --> <option name="isAIPlayers" value="false"/> <!-- players can be added to check both Americans and British --> <!-- <option name="players" value="Americans:British"/> --> </attachment>

All I can think of---

Cheers...

@wc_sumpton

Thank you!

Going to try this again. 😂

This time I have added testing for haveResources.

LOL

Cheers...

To minimize the requests to what I believe would be the marginally most important improvement here, I suggest at least adding a decimal to the Wins and Draw results (or using the permille instead of the percent).

Currently a 100% Win in the battle-calculator is anything from 99.5% to 100.0% Win, and being 99.9% sure to win a battle may be significantly different from being 99.5% sure of the same, but currently they are both given as 100%.

@cernel

Created the following:
Pull Request

Don't know if it will take.

Cheers...

@thedog

Thank you!

I already have 2.5 and 2.6 installed.
Appreciate the suggestion.

Cheers