1. Home
  2. Map Making
  3. XML Options Browser
Log in to post
Load new posts
  • MahksM

    delegate term incorrect? - Resolved -

    10
    0 Votes
    10 Posts
    7k Views
    MahksM
    Got it Thanks! :thumbs_up_medium-light_skin_tone:
  • MahksM

    endTurnNoPU discrepancy - Resolved -

    4
    0 Votes
    4 Posts
    2k Views
    MahksM
    This step section is the worst part I have found so far. I think it has been added to and bandaided many times. I've been having a hard time untangling it. It should be one of the simplest sections, just laying out the sequence of steps and options within. <sequence> <step delegate="initDelegate" maxRunCount="1"/> <turn player="Russians"> <step number="1" delegate="tech"/> <step number="2" delegate="purchase"/> <step number="3" delegate="politics"/> <step number="4" delegate="move" combatMove="true" nonCombatMove="false" skipPosting="true"/> <step number="5" delegate="battle"/> <step number="6" delegate="move" combatMove="false" nonCombatMove="true" display="Non Combat Move"/> <step number="7" delegate="place"/> <step number="8" delegate="tech_activation"/> <step number="9" delegate="endTurn"/> </turn> <turn player="Germans">...</turn> ... <step delegate="endRound"/> </sequence> 1039
  • MahksM

    tech_activation step - Resolved -

    3
    0 Votes
    3 Posts
    2k Views
    General_ZodG
    @mahks That is correct as it applies to the techs that use the dice interface provided (tech buying/rolling). Which is 99% of maps. The other 1% use triggers to activate techs and triggers to place an x in the technology list.
  • MahksM

    combatMove & nonCombatMove steps - Resolved -

    5
    0 Votes
    5 Posts
    2k Views
    MahksM
    Can a developer confirm these are not of use anymore? Are they still required for older maps?
  • MahksM

    stepProperty attribute "Display" - Resolved -

    2
    0 Votes
    2 Posts
    2k Views
    General_ZodG
    @mahks That is correct, "display" is only an area to rename the individual steps and delegates. It can be set to anything and you can add "display" to any step that does not have it too. Just add the missing syntax . <step name="britishCombatMove" delegate="move" player="British" display="Pre-Purchase Combat Move"/> [image: 0_1524913830224_Display_Example.001.PNG] Note it only changes the name displayed in bottom right corner, not the name in the action panel.
  • MahksM

    bid explanation - Resolved -

    18
    0 Votes
    18 Posts
    6k Views
    General_ZodG
    @mahks Your getting the crash course here. You will have years of xml experience crammed into weeks. btw, finals tomorrow.
  • MahksM

    politics step - Resolved -

    2
    0 Votes
    2 Posts
    1k Views
    General_ZodG
    @mahks The diplomatic options during the politics step/delegate are defined by 3 separate methods. relationshipTypes: Defined just by name, these determine what the choices are called. relationshipTypeAttachments: Defined by attributes, these determine the behavior of the choices. politicalActionAttachments: Defined with aid of other condition and triggers, these are the choices, as presented to a player at any given time in the user interface. The logic behind the choices and their interaction is determined here.
  • MahksM

    vps and captureVps - Resolved -

    8
    0 Votes
    8 Posts
    3k Views
    RogerCooperR
    @general_zod Just the Pacific_Incomplete scenario. Cumulative scoring of VP's might be a useful feature for other scenarios.
  • MahksM

    Relationships Last Extra Rounds - Resolved -

    6
    0 Votes
    6 Posts
    2k Views
    redrumR
    @Mahks So relationship is part of a condition, so if its set to -1 then it means it'll essentially ignore duration unless "Relationships Last Extra Rounds" is set. Essentially this is what the condition checks: (currentRound - roundRelationshipWasCreated - "Relationships Last Extra Rounds") >= numberOfRoundsThisRelationshipMustExistForMinimum So if "Relationships Last Extra Rounds" isn't used then the -1 will make it so the duration check is always true.
  • MahksM

    Terms: AA unit - Resolved -

    23
    0 Votes
    23 Posts
    9k Views
    General_ZodG
    @mahks Simplest solution is to just add (first strike units) next to each aagun reference. Not perfect but will be consistent.
  • MahksM

    whenCapturedChangesInto - Resolved -

    3
    0 Votes
    3 Posts
    1k Views
    redrumR
    @mahks Here is POS2 XML: whenCapturedChangesInto values: allows a unit to change into a different unit when captured from a specific player to a specific player. "fromPlayer:toPlayer:transferAttributes:unitType:numberOfUnits". accepts "any" instead of a player name. allows multiple. examples: <option name="whenCapturedChangesInto" value="any:any:true:Minor_Factory:1"/> and <option name="whenCapturedChangesInto" value="Russians:Germans:false:gold:3:lumber:1"/> Currently, transferAttributes only transfers hit point and bombing damage from old to new unit.
  • MahksM

    willNotFireIfPresent - Resolved -

    3
    0 Votes
    3 Posts
    1k Views
    redrumR
    @Mahks Here is the POS2 XML: willNotFireIfPresent values: a list of unit types for which if they are present in the battle, this aa gun will not fire. So yeah this only affects isAA type attacks.
  • MahksM

    relationshipInitialize - Resolved -

    6
    0 Votes
    6 Posts
    2k Views
    MahksM
    Ah, got it, Thanks!
  • MahksM

    maxOperationalDamage - Resolved -

    4
    0 Votes
    4 Posts
    2k Views
    redrumR
    @mahks If it isn't set then it operates until destroyed.
  • MahksM

    canalAttachment - Resolved -

    10
    0 Votes
    10 Posts
    3k Views
    General_ZodG
    @mahks attachTo typically requires the seazone name. But it will accept a land territory as well for nonstandard use. The land portals @prastle refers to are not done via canals but via hard connections.
  • MahksM

    captureUnitOnEnteringBy - Resolved -

    4
    0 Votes
    4 Posts
    1k Views
    General_ZodG
    @mahks But some options can be manipulated in atypical ways. People seem to always figure out new ways upon experimentation.
  • MahksM

    Terms: Produced - Resolved -

    5
    1 Votes
    5 Posts
    2k Views
    General_ZodG
    @mahks As purchase, produce and production references go. I would refer to them in same existing way. Anything else would not be accurate imo.
  • MahksM

    Renaming a tech - Resolved -

    5
    0 Votes
    5 Posts
    2k Views
    redrumR
    Yeah, my understanding is this is just for display purposes and only relevant to hard coded techs.
  • MahksM

    Terms: unit name vs attribute - Resolved -

    7
    0 Votes
    7 Posts
    2k Views
    redrumR
    @mahks Yeah, generally actual attributes should be referenced not "unit names/types" especially since in many cases units can have multiple (act as both a transport and carrier). Some of the challenge is that some "types" like carrier don't have a single unit option so its annoying to have to refer to something like "isSea & carrierCapacity > 0" rather than saying carrier. Here are some common mappings: Transport: isSea & transportCapacity > 0 Carrier: isSea & carrierCapacity > 0 Sub: isSub Land Transport: isLandTransport (can use or not use transportCapacity) Air Transport: isAirTransport & transportCapacity > 0 Destroyer: isDestroyer
  • MahksM

    category - Resolved -

    4
    0 Votes
    4 Posts
    2k Views
    redrumR
    @mahks So a tech "category" is essentially a group of techs that includes 0 or more "techs" that is presented to the user for selection during the tech phase. After a user selects a category, they then roll based on tech tokens to see if they get a technology and if there is more than 1 tech in the selected category then it randomly rolls to select which one is researched.

Recent Posts

  • StohrmS
    Stohrm

    I may have already found part of the answer to my own question in the following code:

    <attachment name="playerAttachment" attachTo="British" javaClass="games.strategy.triplea.attachments.PlayerAttachment" type="player"> <option name="shareTechnology" value="UK_Pacific"/> <option name="helpPayTechCost" value="UK_Pacific"/> <option name="retainCapitalNumber" value="2"/> <option name="destroysPUs" value="false"/> </attachment>

    Except that I'm not sure it actually works; as it currently only accepts payment from the UK_Pacific and not the British.

    read more
  • StohrmS
    Stohrm

    I would like to fully separate the British and the UK_Pacific units and turns with the exception of their Tech Development. What is the simplest way to achieve that?

    Perhaps what we really need is more than one type of tech development phases: Allied or Axis tech development where the research is pooled and shared by all members of an alliance; National tech development where only but all players of that nation pool and share their advances; and Player tech development that remains specific to that player.

    Either that or a tech brokering phase where one can give or sell their tech advances to other players.

    read more
  • LaFayetteL
    LaFayette

    I think the XOB file format is escaped. We may need to take another stab at exporting the data.

    read more
  • cameronC
    cameron

    huh. so what's adding the weird prefix?

    maybe try commenting out line 9 & 10?

    read more