@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...

@azimuth

no worries I still think it has possibillities 🙂

hmmm ... dont think i spelled that right lol

@thedog well I don't think 2.6 does anything different as far as the yaml goes.

When you update the yaml you'll get a notification when you start triplea saying there updates for any maps that you have downloaded.

If you don't update yaml, the new version will still be the one that gets downloaded.

That's why I have a notification with the date and version at game start, similar to what you have.

I'm not entirely sure about the future of the map yaml, I thought maybe it was gonna go away when 2.6 is released.

I'm not sure about that or how it would work if it happens though.

@azimuth Remember software isn't released, it escapes. Good luck with your project.

@nothingtoseehere no worries i had to run also 🙂

Good advice from both of you. I agree, it will be much better with transparency, so i am willing to go for that for my final version.
As for my version 0.2, half of the models with background are finished so i will just finish the rest too. Even without transparency the map will be much more fun to play that way.

I will probably look into greenfish already while workig on 0.2, to see if i get a hook on it.

@edit:
Oh one more thing:
I found that i can make the background the same color as the map territories, belonging to the respective race. So the Empire background is the same grey as the empire territory, so it looks like tranparency as long as you do not go on allied territory.

Cheers

Raise this, for triplea.log not truncating
https://github.com/triplea-game/triplea/issues/12536

TheDog-GH created this issue in triplea-game/triplea closed 2.6.147xx tripla.log does not truncate and can grow to 210M+ #12536

@jkprince havent been doing much lately, here is some pixelart that might find its way in as unit sprites
5c0667b2-1d88-44d1-b29f-b43624525602-image.png 1849d59b-1729-42a5-935a-9107e955011e-image.png 21379730-daa3-44e6-a998-f623e5f04342-image.png 2953405c-1eeb-4d0f-8d01-b8411db2c899-image.png 49c9d10f-9b2a-4a70-a8b5-d95236223dd6-image.png cbc292e8-9bc7-4bdb-9eab-4fb6d92bf457-image.png 579b14e5-d9f4-4e1d-83e6-085aa142e746-image.png

Testing Forum poster

Test summary from TripleA, engine version: 2.6.14719, time: 9:32:49 AM
Savegame

I am reactivating this old thread to post the results of some experiments with the AI's and see how they compare in actual games.

My first experiment

Scenario World at War Variant - v3
https://axisandallies.fandom.com/wiki/World_At_War_Variant_-_v3
Version 2.6.14696
Results Hard AI did better. When the Allies used Hard and the Axis the used Fast, the Axis was too aggressive in Eastern Europe initially, which the Russians exploited successfully, overruning much of Eastern Europe.

Both AI's played the Americans poorly, building land units and transports without bringing them across the Atlantic.

@ubernaut he did on git a few times but I don't ever remember seeing him here.

@LaFayette Should new maps/games which (quite certainly like this one) will be released after TripleA 2.6 is released avoid having the "mapName" entry in the game (XML) file?

@panther yeah this is weird one i think gmail has been black holing them but first issue i've seen with yahoo

excellent. that worked perfectly (once i corrected the slight typo at the end (that final '/')).
thank you kindly. : )

I actually found a very, very, very dirty trick. But my map is already so heavily modded that it could do the job. Sharing just in case 😉

I use the repairPlayers step option, which allows a player to repair for another player. The feature seems to be working ONLY if the main player has anything to repair for himself (which isn't very logic or intuitive). To say it another way, if you want Germans to be able to repare italian factories, you need to have at least one german damaged facility as well, otherwise the phase is skipped.

So I created two extra (hidden) players, " Axis" and "Allies". Only those two have the repair frontier. In order to have the repairPlayers feature working (see above), both have a (hidden) fake damaged unit on the map (in Sahara and Himalaya, respectively) that cannot be repaired (no repair frontier).

This way, the repair screen doesn't pop-up before regular players purchase phase (as they don't have the frontier). Instead, just after the Place phase of each players, there is a separate "repair" phase, actually lead by the "Axis" and "Allies" players, and using pooled resources.

This all just to make sure factories cannot be repaired before placing units...

TripleA Move Summary: Germans round 1

TripleA Move Summary for game: World War II Global 1940 2nd Edition

Game History

Round: 1 Purchase Units - Germans Germans buy 1 armour, 1 bomber and 1 factory_minor; Remaining resources: 0 PUs; Combat Move - Germans 1 submarine moved from 124 Sea Zone to 111 Sea Zone 1 submarine moved from 118 Sea Zone to 111 Sea Zone 1 submarine moved from 108 Sea Zone to 110 Sea Zone 1 submarine moved from 103 Sea Zone to 110 Sea Zone 1 submarine moved from 117 Sea Zone to 106 Sea Zone 1 battleship moved from 113 Sea Zone to 110 Sea Zone 2 artilleries and 2 infantry moved from Holland Belgium to Normandy Bordeaux 3 tactical_bombers moved from Western Germany to 111 Sea Zone 2 fighters moved from Western Germany to 111 Sea Zone 1 fighter moved from Norway to 110 Sea Zone 1 fighter moved from Holland Belgium to 110 Sea Zone 2 bombers moved from Germany to 110 Sea Zone 1 tactical_bomber moved from Germany to 110 Sea Zone 3 armour moved from Greater Southern Germany to France 1 artillery, 3 infantry and 4 mech_infantrys moved from Western Germany to France 3 armour and 2 infantry moved from Holland Belgium to France 2 artilleries and 6 infantry moved from Greater Southern Germany to Yugoslavia 2 infantry moved from Slovakia Hungary to Yugoslavia 1 armour moved from Poland to Yugoslavia 1 fighter moved from Slovakia Hungary to Yugoslavia 1 tactical_bomber moved from Poland to Yugoslavia

Savegame

@black_elk

I like the other one better 🙂

@black_elk

You are a triplea treasure Elkstar 🙂

@rogercooper Here is an example of open source project using a wiki, https://freeciv.fandom.com/wiki/Main_Page