-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possibility to choose air unit types that move onto a newly build carrier #1751
Comments
I think you are talking about some of the other fighter/carrier options:
I am talking about the behavior of "Move existing fighters to new carriers". Both the maps I mention has these settings:
If the TripleAs unit placement system can show and let the player choose specific unit types, then I hope it can be done to also let the player chose what fighters are to fly out to the sea zone and land on the newly placed carrier. |
Got it, so your issue is about an aircraft movement that occurs after the placement of the new carrier. |
Yes |
@FrostionAAA This should be implemented once #1755 is merged. |
Nice! Looking forward to testing it out. |
Why the hell no NWO / WAW / TRS players ever complained about this thing??? I've never noticed, cause I never play this kinda stuff. Actually, by correct rules, you should be able to choose to redeploy whatever air able to stay on carrier, not just your own, but also air units of your allies, not only the ones of the same player that placed the carrier, but the engine doesn't allow you to do that, either. |
@Cernelius Yeah, I was kind of surprised by this as well. I think most players forget about this rule of moving fighters to newly built carriers. "Actually, by correct rules, you should be able to choose to redeploy whatever air able to stay on carrier, not just your own, but also air units of your allies". I've actually never heard that before (also never really thought about it). Are you sure that is the case? Is it in the rules somewhere? |
Well, as I said, I wouldn't want you to go ahead and correcting this limit / bug and that's it. "Redeploy existing fighters owner restricted"
And this property should be at least added as true in NWO, TRS and WAW, to keep the behaviour as it is and has always been, unless a bunch of xp players can confirm this "change" would not somehow kill the existing balance (a confirmation we all know we are not getting). If, like, you would just make the "Move existing fighters to new carriers" work correctly, without anymore the possibility of having the current behaviour, I'm extant to push the matter and I'm not sure if this move would be totally good, just based on how many custom games have been already created with the current behaviour in mind. Maybe this limited behaviour was specifically intended, based on how messy / strange would be to move someone else air on your turn (tho you can already do something like that for allied air on your carrier). I don't think I can proof without pasting copyrighted material. But if you still can't manage to see it yourself, let me know I can just send you a mail. Moreover, and this is very important too, this is a rule made for games in which the only possible relationships were alliance and war, and never changing, thus you were sure that if, during your turn, any air was in a territory of yours, those can be only your allies, but this should not be taken as granted, here. So, you should also be sure that this works only with an "allied" relationship, meaning that both the archetype neutral and war won't allow it, because, in a FFA, you can end up with neutral and even enemy air in the territory you are producing the carrier from, when you downgrade (a map could allow you to downgrade relationship from allied to war). |
@Cernelius Alright well since no one is reporting or complaining about not being able to move allied fighters to carriers, I'm not planning to make any changes are this for now. |
@ron-murhammer When I test this out it seems to work fine. But I am wondering why the written text is altered so drastically. I would say that the old sentence is way too long, but how about something like “Move air units from X to new carrier?” / “Choose air units to move” / “Choose air units to move to carrier”. And maybe change the headline “Move fighters to carrier” to state “Move air units to carrier”, as I would think it could also be bombers on many maps. Just my thoughts :-) |
@FrostionAAA The reason for the change is it actually uses a different code component for the popup (same one as when you click on a territory). I'm not sure if the gray text is customizable currently. I do agree with changing it to "air units" instead of "fighters" and will do that. |
Please add possibility to choose what type of air units should move out onto a newly build carrier. Right now it seems that there is no possibility to choose what type of air units that are to move out onto a carrier after it has been placed. The short version of the current behavior (long can be seen at forum: https://forums.triplea-game.org/topic/73/iron-war-official-thread/79):
• After carrier placement, there is a popup that lets the player choose how many “fighters” are to be moved to the carrier (at least if the XML has "Move existing fighters to new carriers" value="true")
• There is no option to choose what type of air units to move in case one has more than one.
• The engine seems to choose for you, and I do not know the parameters for the engine’s choice. In Iron War it seems to choose 1 fighter and 1 bomber over 3 fighters, and that is not an optimal choice.
Here are an example from Star Wars Galactic War:
![unavngivet](https://cloud.githubusercontent.com/assets/15268177/26396536/c40d01ae-4073-11e7-984a-3976bc4e5458.png)
Going to place a carrier with 1 capacity (1 air unit)
After placement I can ofcourse max choose 1, but not what type, even if there are three possible fighters.
![unavngivet2](https://cloud.githubusercontent.com/assets/15268177/26396541/ca7b4640-4073-11e7-8416-e32fce8664f9.png)
Engine just chooses one of the types for you.
![unavngivet3](https://cloud.githubusercontent.com/assets/15268177/26396549/d40a6196-4073-11e7-8327-f57aa7e58ced.png)
The text was updated successfully, but these errors were encountered: