Simon

None of those actions will have any impact on the issue.  Neither HD nor Java are filtering the drives that are shown - it’s purely a permissions issue

"How's that mask sounding now, Sparky?"
 

side note: was highly amused that one of the concerns was with people that may argue the mask mandate in the building. My response:  we're blacksmiths.  We have 2000 degree steel and hammers, there is no argument.  Also, if they try to say that they have a medical condition that prevents them from wearing  a mask, they definitely should not be in a forge with coal smoke.  

side note: was highly amused that one of the concerns was with people that may argue the mask mandate in the building. My response:  we're blacksmiths.  We have 2000 degree steel and hammers, there is no argument.  Also, if they try to say that they have a medical condition that prevents them from wearing  a mask, they definitely should not be in a forge with coal smoke.  

side note: was highly amused that one of the concerns was with people that may argue the mask mandate in the building. My response:  we're blacksmiths.  We have 2000 degree steel and hammers, there is no argument.  Also, if they try to say that they have a medical condition that prevents them from wearing  a mask, they definitely should not be in a forge with coal smoke.  

Was glad to see that come through -- on a local level, I _just_ managed to get the historic society to say that we're going to require masks at the forge and museum starting tomorrow, so this was good timing.

side note: was highly amused that one of the concerns was with people that may argue the mask mandate in the building. My response:  we're blacksmiths.  We have 2000 degree steel and hammers, there is no argument.  Also, if they try to say that they have a medical condition that prevents them from wearing  a mask, they definitely should not be in a forge with coal smoke.  

Was glad to see that come through -- on a local level, I _just_ managed to get the historic society to say that we're going to require masks at the forge and museum starting tomorrow, so this was good timing.

side note: was highly amused that one of the concerns was with people that may argue the mask mandate in the building. My response:  we're blacksmiths.  We have 2000 degree steel and hammers, there is no argument.  Also, if they try to say that they have a medical condition that prevents them from wearing  a mask, they definitely should not be in a forge with coal smoke.  

side note: was highly amused that one of the concerns was with people that may argue the mask mandate in the building. My response:  we're blacksmiths.  We have 2000 degree steel and hammers, there is no argument.  Also, if they try to say that they have a medical condition that prevents them from wearing  a mask, they definitely should not be in a forge with coal smoke.  

side note: was highly amused that one of the concerns was with people that may argue the mask mandate in the building. My response:  we're blacksmiths.  We have 2000 degree steel and hammers, there is no argument.  Also, if they try to say that they have a medical condition that prevents them from wearing  a mask, they definitely should not be in a forge with coal smoke.  

Was glad to see that come through -- on a local level, I _just_ managed to get the historic society to say that we're going to require masks at the forge and museum starting tomorrow, so this was good timing.

The problem that OP is running into is mainly one of definition.  Fundamentally, he's looking to have various setup/activation Limitations on an ability...but not have them be quite as Limiting as they are by default (e.g. they're not required every time the ability is used).  As has been stated in multiple ways by multiple people in this thread, there are a number of perfectly rules-legal ways to approach this idea....what you do NOT need to do is start creating your own rules.  You also do not need to alter the duration of the ability in question, since that is explicitly not what you're after for an effect.
 
Easiest (IMO):  based on how often the character needs to go through the setup/activation process for the ability, reduce the net Limitation for all of the activation process (e.g. Incantations, Gestures, Extra Time, etc.) based on how much the character is limited.  Use Conditional Power or Limited Power instead of the individual setup limitations.  The value for the Limited Power Limitation may be -0...or could be up to -1/2 or -1, depending on how Limiting it is to the character.  If it's something that the character needs to do when they wake up in the morning and then the ability/abilities are ready for the day, then it's likely just flavor and worth -0.  If it's something that the character needs to do within 5 minutes of using the ability and is time-prohibitive to perform in active combat, then you could be looking at up to a -1 depending on GM input.
 
Invoking some slightly tweaked rules from the supplements, you get another perfectly viable option:  Time Limit.  As with Differing Modifiers, OP is not understanding the intent of the Modifier here....in particular the implication of applying Time Limit on an Instant Power.  This has been established by Steve and is intended for precisely what has been described. My main hesitation with using this approach is that it increases the Active Cost of the ability without actually providing any Advantage to the ability itself (again, we're not looking to Advantage the ability, we're looking to lessen the Limitation(s)).
 
Others have proposed equally valid ways to approach it -- pick whatever works best for your taste/flavor....just try to avoid creating or altering core rules when there's no need to do so (and apparent lack of understanding/misunderstanding of the rules being modified).
 

Ok, upon rereading the entire thread, this comment stands out to me now.
 
Stop overthinking everything.
 
A Power that affects a target of choice each phase while requiring a new attack roll  is the fundamental way every Instant Attack Power in the game functions by RAW. 
 
Any Modifiers you add to that Power are just that: Modifiers. If you chose some procedure that has to be done each time you use the Power, then that's one set of Modifiers which is a different set of Modifiers  than if you do the procedure only once and can use the Power for a set time and another than needing the procedure and having to pay END or Concentrate  or whatever to keep using the Power without repeating the startup.
 
KISS is areal thing, and you're making your creation process unnecessarily hard here.

It's the number of increments to advance in each iteration of a loop.  You'd use it along with START (and potentially STOP) to, say, have all even numbered items out of a given array printed out in one column and all odd numbered items in a second column.

What you've described is wanting to have an Instant Power (e.g. Blast) with setup/activation Limitation that do not apply every time the ability is used -- the ability can be setup and "readied" (going through the appropriate steps dictated by the various Limitations) and then used at will for some time thereafter.
 
That is NOT a Constant Power...and has nothing to do with a Constant Power.  It's an Instant Power with a variation of the setup/activation Modifiers.
 
There are very well-established rules for setup/activation Modifiers on Constant Powers -- variations that allow them to only apply to the initial activation, or to have them apply throughout the Power's use.  That's not what you're after, from the sound of things...since you're not dealing with Constant Powers and don't want to change the Instant Powers to Constant Powers (since that brings along a LOT of additional rules....some of which you've stated you do not want to have).

So stop thinking about changing the Power's duration -- you're not looking to do that.

For distinguishing between fixed and variable slots, you can combine the already mentioned IS_MP with some clever use of ATTRIBUTE_VALUE and the isUltra() method (part of com.hero.objects.GenericObject) -- that will return true/false (as a string)....if true, you're dealing with a fixed slot.  If false, you're dealing with a variable slot.

Or take 1/2 END on Power 1 and then make Power 2 +0 STR with 1/2 END and add modifiers to base characteristic checked.
 
Just note that rounding rules apply at each calculation (which is what caught you on the 1/2 END for Running)

1. This forum is for questions on HERO System Sixth Edition rules -- this is not really a rule so much as an option for tool-kitting, so not truly applicable to this forum. If you'd like discussion on the subject, I'd recommend posting to the discussion forum.
 
2. That said, in order to keep things consistent with the rules, I'd have to answer with the following:
For Characteristics not normally affected by REC, you Regenerate 1 characteristic point every time interval (your second option) -- this keeps the cost structure consistent with the standard BODY Regeneration For Characteristics that reduced through normal use (END and STUN), you Regenerate your REC to the Characteristic's maximum every time interval (your third option) -- this changes Regeneration slightly for these Characteristics so that it is not replacing your normal REC with something cheaper (it is not recovering END or STUN that are used/reduced) - it is only used to Regenerate "lost" values in these Characteristics (i.e. lost maximum through Drain, etc.). 

Given the potential benefits of space industrialization, such as nigh-limitless solar energy, minerals from the asteroids, and microgravity industrial processes... No, it's not clear to me that Branson could spend his money on any worthier cause. Sure, space tourism is a junket for the ultra-rich. But it's an indulgence that builds capacity for other things.
 
Dean Shomshak

It's there today - wonder what happened the other day.  Anyway, resolved - thanks.

For both Modifiers, Steve wanted them to be moved to Custom Modifiers (given the options/lack of "hard rules" surrounding).
 
You can add them back in via a custom template, if desired.  So long as you keep the XMLIDs the same (just copy the definitions from the 5E template), they should pick up the original rules for inclusion.

Try the downloads section of this site -- there are a number that replicate that look, including the default character sheet export.

A few things:
 
1. It wasn't the version of Java, per se, but the outdated libraries that the PDF functionality was dependent upon. Updating those libraries would have required significant retooling of the code.

2. No idea what the last version of Java was that the libraries would have worked under.

3. Would STRONGLY recommend never intentionally running outdated software like that. Java interacts very closely with your host operating system - you really want to keep up with updates to it as they are released.

Costs END Only to Activate is worth -¼. What you describe sounds significantly less limiting -- especially in the context of an END Reserve which doesn't drop to zero when your character is knocked out. So no, I don't think a -¼ limitation is appropriate.  It feels like -0 at best.
 
You could combine the two: Costs END Only to Activate (-¼) and Turns Off When END Reserve is Empty (-0). I recognize  this does not build the power you've described, but it has the benefit that no one would bat an eye at the value of the limitations.
 
 
Doug
You could treat is as the "boot up sequence" of the otherwise low-draw systems.