Simon

I've seen it, but have nothing to do with store inventory.

You're running HD from a location that you (or, more appropriately, Java) don't have full read/write permissions. The creation of the trace.log file (in that same directory) is part of what the launcher is blocking on.

Do I need to remind folks that this is NOT the politics thread? Keep it on-topic or I will have to shut this down. For those who haven't been following closely, the immediately offending posts have been removed and warnings issued where appropriate. While there will be inevitable political cross-over, posts should remain on-topic and dealing directly with COVID.

Sorry...wasn't paying attention. You can likely get what you need with just a template addition. Use the generic SKILL container and make two "required" adders for the primary and secondary methods of divination. Non-required adders should be used as normal to represent the additional primary and secondary methods of divination, though that 1/2 point for additional secondary methods may need some tweaking... Something like the following should get you started -- no need to make any code changes or custom dialogs. <SKILL XMLID="Divination" DISPLAY="Divination" MINCOST="1" FAMILIARITYROLL="8" FAMILIARITYCOST="1" EXCLUSIVE="NO"> <CHARACTERISTIC_CHOICE> <ITEM CHARACTERISTIC="INT" BASECOST="3" LVLCOST="2" LVLVAL="1" /> </CHARACTERISTIC_CHOICE> <ADDER XMLID="PRIMARYMETHOD" DISPLAY="Primary Method" BASECOST="0" MINCOST="0" MAXCOST="0" REQUIRED="Yes"> <OPTION XMLID="METHOD1" DISPLAY="Method 1" BASECOST="0"> </OPTION> <OPTION XMLID="METHOD2" DISPLAY="Method 2" BASECOST="0"> </OPTION> <OPTION XMLID="METHOD3" DISPLAY="Method 3" BASECOST="0"> </OPTION> </ADDER> <ADDER XMLID="SECONDARYMETHOD" DISPLAY="Secondary Method" BASECOST="0" MINCOST="0" MAXCOST="0" REQUIRED="Yes"> <OPTION XMLID="METHOD1" DISPLAY="Method 1" BASECOST="0"> </OPTION> <OPTION XMLID="METHOD2" DISPLAY="Method 2" BASECOST="0"> </OPTION> <OPTION XMLID="METHOD3" DISPLAY="Method 3" BASECOST="0"> </OPTION> </ADDER> <ADDER XMLID="SECONDARYMETHOD2" DISPLAY="Secondary Method 2" BASECOST="0" MINCOST="0" MAXCOST="0" REQUIRED="Yes"> <OPTION XMLID="METHOD1" DISPLAY="Method 1" BASECOST="0"> </OPTION> <OPTION XMLID="METHOD2" DISPLAY="Method 2" BASECOST="0"> </OPTION> <OPTION XMLID="METHOD3" DISPLAY="Method 3" BASECOST="0"> </OPTION> </ADDER> </SKILL>

That's your best bet...and with some clever use of regex you can have the export process convert that to whatever you need.

I should point out that the original ability that you cited was created as a Compound Power, with the display/text modified. At the time, Steve didn't want that modification to be anything official, just a shortcut for appearance on that singular writeup. If the Compound Power text bothers you, you can always edit it to your liking, though that will typically preclude any automatic updates to the text when the underlying power construction changes (e.g. if you increased the amount of protection offered).

FTFY

apply to two Characteristics: buy it as up to 50 active points of PD/ED. show up in Characteristics: you don't as the rules currently stand. You can either: make note of the fact that the character has 25 rPD / 25 rED purchased as a Naked Advantage make the entirety of the Character's PD/ED Resistant (i.e. 28 rPD/28 rED) buy purchasing +0 PD and applying Resistant to the base Characteristic (likewise for ED) get Steve Long to create a new rule which allows for either Naked Advantages to be considered Inherent when purchased for Characteristics or for Characteristic Powers to apply their Modifiers to only part of the base Characteristic. If you go the latter route, the likelihood of HD being modified to accommodate would depend on the relative complexity and applicability of the new rule. A different approach would be to sell off all PD/ED on the Characteristics tab except for what you want to be non-Resistant. Purchase the 25 PD and 25 ED as Characteristic Powers with Resistant applied.

You're not dealing with Characteristic Powers since you're not looking to apply Resistant to the entirety of the base Characteristic(s) -- use a Naked Advantage.

That's a Limitation that is specific to an individual slot in a Multipower that has a common modifier of Charges placed on it...where the individual slot uses more Charges than the others on any given use. With Charges being a Limitation that requires several inter-related tables to calculate its value. Yeah...use a Custom Modifier (or Limited Power, if you prefer) for that.

Again, it's how you want the character to utilize and pay for the AI -- having the AI as a character file is great...but what it represents to the character and how it is purchased defines how you want to represent it in HD.

That largely depends on how you want it to function (i.e. how you want to build it). It can be Access Points, Resource Points, Computer Link, Contact, any of a number of Talents (with the Link as the sfx)...even Vehicle/Base rules can apply. Recommendation: figure out how you want to represent the Computer/AI within the rules of the system (with your GM's aid/input as needed) - that will typically tell you precisely what to do within HD.

Note that UAA Powers need to have defenses which are both "reasonably common" (as determined by the GM) and obvious -- the characters shouldn't have to guess to figure out how to prevent themselves from being teleported against their will. In short, UAA Powers _do_ have defenses, just not one defined defense for all UAA abilities. And the defenses tend to be all-or-nothing -- if the character has the defense, the power doesn't work at all.

6E1 page 355:

Let's try a different approach: You purchase Combat Piloting and TF: Anthropomorphic Mecha. Your character is pretty danged good at piloting anthropomorphic mecha that can fly in combat situations. Congratulations. During the campaign, your character comes across an anthropomorphic mecha that is unable to fly. Guess what? Your Combat Piloting won't come into play. Similarly, your Combat Piloting and TF: Small Planes won't help you when you get into a cessna with the wings cut off.

You don't need that knowledge, you just need basic common sense (as outlined above).

Why in the name of all that's holy are you even worrying about that? Seriously. Pause. Think about it. Don't just go and post. If you purchase Combat Piloting and then purchase TF: Anthropomorphic Mecha, that TF will cost you 0 points. Why? Because it is presumed that you have a brain in your head. If you purchase Combat Piloting and then purchase TF: Anthropomorphic Mecha, Small Planes, that TF will cost you 1 point. It's entirely up to you which of those categories is free and which is 1 point...and it makes exactly zero difference in the display, the math, or any other aspect of character creation or use.

Again, giving the benefit of the doubt that if a character purchases Combat Piloting and then selects a singular TF for one of the mecha, then that mecha will be able to fly (otherwise, that Combat Piloting isn't going to do them much good).

HD is tracking that just fine and discounting 1 point TF for any flying vehicle type...even gives the benefit of the doubt for the various mecha.

"If you need to go to the bathroom after this next series of tests, please let a test associate know, because in all likelihood, whatever comes out of you is going to be coal. Only temporary, so do not worry. If it persists for a week, though, start worrying and come see us, because that's not supposed to happen." - Cave Johnson

Java's versioning has always left a bit to be desired....but at this point, you'd have to actively try to download a version of Java that wouldn't run HD.

So you've followed all of the instructions except for that pesky bit about Java being required to run a Java application? Go to www.java.com - click the big red button.

*golfclap* you got me on that one -- I had to do some reading to figure out why it wasn't implemented. Fewer Tasks is a variable Limitation which reduces the number of tasks relative to the character's EGO that are required...which is itself a table based on the friendliness of the summoned being. Your solution (custom modifier) is likely to be the best way to go. I'll see if there's any way to automate the logic (without undue complexity in the code) once the current holiday (and it's side-effects) are past. Edit: understand that the complexity is not just in calculating the value of the Modifier (which could be a simple drop down list), but in configuring the displayed number of tasks required (which would be necessary once the value is changed from default)

When there’s more than a one line change that affects only the rare build, yes. Beyond that, I tend to wait until various minor/esoteric changes add up a bit

FWIW, I have a new update posted which essentially implements the logic above (slightly different in that there's already a check for an ability that doesn't use END, so it checks if the original Duration is Instant and the ability does not have a continuing effect -- disallowing if so).