Mister_Bison

J'allais dire ça, mais avec 999,5 ans de moins ^^

Désolé de pas être plus présent, à mon boulot, "la mmmde a atteint le ventilateur", comme disent les anglais, et ça sentait vraiment pas bon. En plus, je préfère bosser pour sauver le jeu ou le recoder que vous tenir au courant, désolé.

Mais ne perdez pas espoir, NC fait la forte tête, mais ils ne peuvent pas ignorer Paragon Studios et des investisseurs bien longtemps. On les aura, même s'il faut recoder le jeu.

Like Hide in the stalker secondary, blaster and tanks first secondary (defiance 2.0 shoot through mez and Bruising). But actually those two were simple to "fix" (make Hide an inherent, and leave the first powers special). Then you would have needed a way to prevent the game from letting the player choose 2 primary or 2 secondary as first powers, and from these two situations, only the one where the player had no offensive power was bad.

Saw the poster of the film on imdb and the ship had a positive memory reaction. It looks like it. Thank you so much ! This thing has been driving me nuts since the internet came and I've been unable to remember the name of that one !
Edit: This is definitely it, the alternate name in France is "Cosmos 2050" while Space 1999 is known in France as "Cosmos 1999", so I did not hallucinate. This is so great, thank you again, I would never have been able to find it myself !

Tanker, Controller, Dominator, Blaster... Tanker got Martial Arts not so recently. Dominator and Blaster got Martial assault/Manipulation more recently... Martial/Ki control ?

Since we are on that, I wanted to ask some gurus of the 80s, but possibly either early 90s or even back to the 60s. The robot picture reminded me.

I remember a film where a robot, sent against the protagonists, was destroyed and got reconstructed, he ressembled Robby the Robot, the bubble arms and round glass head, but wasn't quite like it. There was a dark and red corridor at the beginning also. Then, an asteroid came down on the base, then all I remember was seeing something that ressembled Moonbase alpha from Space 1999, from which the heroes (a family or something like that) took off in a saucer+Enterprise tail ship, then they found another planet they explored in the saucer only part of their ship.

That's all I can remember of the film, I thought I labeled the VHS "Space 2000" but I can't quite really remember, but for reasons unknown, I took the VHS apart to see how it was functionning. I was 8 or so at the time, so it's quite old and doesn't make any sense.

Could you help me put a title on that ? Thank you !

Boost is templates.

That would be something new, but I take that as something to test. But if we take the scope of a whole server application, no data or code is going to take seat for long in the cache anyway.

That's not the same. dotNET assemblies are like java versions, each are different, and what they did was like linking to every version of the library each time they boot up the program, even if they needed only to print things. It's like including stdio.h and use printf just to output constant strings. Anybody can do that in any language, and it's not the same as saying "well, do I use 2k of data instead of 256bytes and have easier to read enumerations (like 1,2,3, 11,12,13, 21,22,23...) instead of no-gap but hard to read enumeration values (1,2,3,4,5,6,7,8,9,...) ?" As Arcanaville said, code efficiency is the enemy of the programmer efficiency. You can perfectly live with it but generally it does work against you.

Okay, you've not exactly answered what I asked because I'm expressing myself funnily, but that's conforting to know another, less suspicious assumption, but an assumption none the less, was true.

Of course this is not possible, this is not what I wanted to know your thoughts about, but it's related. Take this formula you gave previously:
From that I take that -5 to Cur or -5 to Abs makes the same effect to the attribute value in the end. *Both* types of mods are affecting the value, even though not both appear in the same 'item' of a power's effect list. That's what I meant.

So, we have:
- Attribmods have exactly one target attribute, exactly one target aspect to mod, no more, no less
- Attribmobs have a duration or have none. Normally attribmods to an attribute's abs are permanent (no duration), and attribmods to Cur are bound to expire (finite duration) but there are exceptions. So the attribmod's duration is independant to the target aspect.

Now, considering only the 'Cur' and 'Abs' attribmods out there, in the game, but completely ignoring which of the two aspects it is, what are the attribmods in the game, that in the end (that is considering the code that gets executed on them), temporarily affect Endurance, Health, Meter or maybe knocks/repel ? What are the attribmods that permanently affect the other attributes ? (I'm thinking def, other status, recov/regen, perception and stealth, others may still fall in this category or the one of health/end etc)

I hope you understand I'm just trying to get this piece of information for 3 questions already, I'm sorry to everybody to flooding, but especially to you, whom I'm bugging to no end. I'm bad at asking questions it seems.

Interesting, I would have said that absorb is not permanent, but that's because I didn't read the description enough.

Templates are tricky. If you take my attribmod calculator, I already have only 2 megs of binary code, and thats mainly because I have Attribs::NUMBER*Aspects::NUMBER methods of accessing the attributes and maintain an array to access the corresponding method from the Attribute and Aspect. Static code is powerful, and memory is plentiful nowadays, so it doesn't matter, complexity is king now, so use it, I say, but sometimes it get even over that... During my internship, I did perfectly legal template metaprogramming, but code generation went over the 6 gigs of my computer... Yeah, there was a hell of a lot of data, too bad it didn't work it would have been blazingly fast though :')

Yeah I understood that. But what's the point of knowing this powers's duration or magnitude is resisted, when it's irresistible ? =) But you need another bit anyway. I want ternary computer =)

So is there any need to have that flag then ? Can't we use the same determining factor ?

How do you resist the magnitude and duration of Grant Power !? I mean, what does these even mean ?

Well, the game certainly isn't going to tell you your buff gives 0.13 defense, it is not pretty (nor big enough ! =) ), it could just be formatting (especially in cases of defense and To-Hit, where things can go above 100%). So I'm not going to take real number formatting for anything, the order yes, but the formatting doesn't mean anything.

Could I ask where you did get this string-value map ? Also... I see things missing here. There is a Max to Max (a MaxMax), a Max and MinRes, and a MaxStr too. Those maybe aren't in the attributes, so where are they ? the MaxMax health gets recalculated everytime there is a Max modification ? The MaxStr is too, or is it fixed ? Is Maxresistance an entity-independant constant ?

Very clever of them. It can be used for anything that is 4bytes wide... including pointers on non x86-64 machines. Gonna do that in my code so that will force it to have it optimized this way. That will throw my caching off though.

I suspected so, would have made this bar as an attribute, but wanted to check that myself, so thanks for the confirmation. Thanks for the insight about the brute's and dom's inherents too.

Neat, so there is still only one resistance and one strengh for an entity attribute and it does become "Magnitude resistance/strengh" or "duration resistance/strengh" because the effect is flagged to be magnitude-resisted or the other, and this flag is a boolean. Also, one same attribute can be duration or magnitude at the same type in different powers, so no hard coding that in the "modification" of the value when the effect is resistible. Actually, that makes it a 3-value flag whether the effect is to be duration-resisted, magnitude resisted, or not at all. Makes me wonder if there isn't a fourth possibility.

About buffs to status and status protection, get a character with power boost and Tactics or any Leadership power that protects against status. I'd do it if I wasn't at work.

Yes, knockback, knockup and repel have reduced magnitude when resisted., since duration in these would be... strange oO

Truths here. You only need powers in one place and only ID them from the entity. Like in databases. You could also have one place for effects and ID them from powers, but I don't know if this would be efficient (indirection is indirection). The "scale" value is an inherent part of the attribmod and should be left there if you plan on keeping the value in databases, but if indeed you store these values in the entity, you can already do the Scale*table[level]. All that's remaining to do when applying is get the caster buffs and enhancement or ignore them, and apply the resistance or ignore it. But strengh *does* vary between attribmods calculation. What happens if you code Buildup and a damage power and execute them in sequence ? Will the damage be buffed properly if you account for the strengh only when linking powers to entities ? Will you make a pass on all the entities powers and effects to buff their strengh, even though it's going to be used for a handful power launches ?

Are you going to code a script ? Or are all your powers going to be resolved at t=0 ? That's going to be wasted code though. You could already put that as delay already and decrease the counter every instant.

In my idea of implementation, you should keep time like that until this power is the next one to resolve on this entity, when it's really needed to keep track of the "delay remaining".

I think you're overdoing it, if arcanatime is exactly 132ms and not 133,33..., then the clock you're looking for is 33ms, not 33,33333... ms. This kind of exact calculation is going to take its toll on the server.

Also, I already thought of all that, it is sorted out, I just wanted to have sorted out the formulas before I went forward. If it's just a matter of adding variables to structures, it's not a problem. If you have to code new functions for new cases, it's another matter.

Then again you should not go into that part like me until things about Cur/Abs are sorted out.

Also, you didn't answer my question about whether you did have evidence Cur is used for time-limited attribmods, or Cur is the time-limited attribmods-dedicated storage value because it is. Is that going to be answered any day or are you keeping your sources a secret ? I'm a scepticist, so I need evidence. At least answer what line (in powers.bin ?) did say defense buffs were Cur mods, without modifying the wording (as Codewalker said "kCurAbs", and I saw kMeter...

oh shucks.

isn't kCurAbs a sort of pointer/flag to designate which of Abs or Cur is gonna be moded ? like kMeter could be a pointer to a meter/attribute, and these variables/aliases are part of the attribmod attributes ??

Please, Codewalker, could I have a look at Mids and City of Data interpreters of powers.bin ? This could answer so much.

Answer is, we want to have the unresisted effect. So my implementation is (going to) be incorrect. Well was, because I know that I need to correct this.
Against melt armor mobs in AE, my resistance went 33.38,18.99 then -21.6 then 0. So they *do* recalculate everything everytime res or unresisted res gets modified, so you've got to store the applied value and delay the cancellation value computation until, well, the cancellation.

Just to get a pictured case, and a test case in AE, what do we want to happen when this happens ?:
Brute has 40% res to energy, brute gets hit by thermal radiation.melt armor, brute toggles off its defensive toggle, melt armor expires.

We want to brute to get back to 0% res. But what happens during the time the melt armor is the only remaining effect ? is it the full debuff or the resisted debuff ?

Or isn't it strange enough to still think Cur mods as being temporary ? We at least need a simple way to make +5% mods, because of regen and recovery.

Of course, I was using brute innocence. It does make sense to have 1.0 def = 100% because you use percents afterwards in the to-hit formula. But the game does deal with percentage, with regen and recovery at least, it did and still does with the old Moment of Glory (I think). Resistance is also percentage based, but def is not. Yet, the game real numbers and city of data still display resistance and def in percents whereas they do not tend to be equivalent at all. 50% resistance does mean 50%. 50% def means nothing if you don't have the emitter's to-hit.

Codewalker and I seem to differ from this conception. Just a question: where did you get the knowledge that defense buffs are Cur modification ? (OTHER than it's duration-based) I want the exact, string from the game, quote. I expect you're going to give me a funny polish notation expression again, but go.

You could at least trigger recalculation only when you get an irresistible resistance mod applied. As I said, they tend to be rare (except when raids buffers are spamming >_>)

ooooh but there are different effects in powers than attribmod my dear. There are Summons, there are GrantPowers, RevokePowers, SetModes & UnSetModes, SetEffectChance, and I could be missing some others.

As you said it yourself, "we'll see".

I don't see the point here. Status resistance decreases duration, not magnitude (another special case ? Yes, I have to code that)

When you apply a resistible debuff/buff, you're modifying the resistible value of the mod with (1-res) and apply this mod directly to the result... as if it was irresistible ! Right ? So you (well my code at least) fall back to this case. And what do you do to cancel an irresistible mod ? You use an irresistible mod with opposite value ? Yes ! That's what I made, well, actually set up only, in my attribmod code (you must have found funny that my functions returned a value instead of nothing, and also, applying an Effect returns an Executable instead of void). Why, do you ask ? That's the raw cancellation effect that you would need to apply if the effect had a duration. You (nearly) have the result on hand, even if the effect is of no duration (such as heal or damage), it takes nearly nothing to leave it on the stack, so I put that as the signature of the method. This was how I would have tackled the "engine" part, leave the cancellation on a stack to apply later on or upon removal of the effect.

Let's suppose you are right, you in fact do have Cur that sums the duration-based effects and Abs the others. You anyway need to have a timer on hand for each effect in order to know when to cancel them, and what amount to cancel each effect individually, or you need to reconstruct from adding all the remaining effects, which is the same amount of data but plain computationally inefficient. Something that takes as much or less space and calculation is to keep the list of "timer & cancellation value" per applying effect instance, and you don't need store each sum separately, because "Abs+(Cur-Cancellation)" is "Abs+Cur-Cancellation". So it's more effective to store the total in either Cur or Abs as the result, and apply cancellations over it.

Also, I didn't find any duration-infinite status effect, Regen, Recovery or Recharge buff or debuff. Only damage, health and endurance modification are "infinite" and "absolute" modification (or am I missing something ?). And those don't have duration-finite modification to their Value (Spectral Wound's damage gets couteracted by a heal, not negative damage). In fact, I didn't find any attribute that needs both of them.

Also, about flooring and ceilings, you may have found that in my code I have a 'val' and an 'abs_val' fields in every Aspects. That's because "getters" are reading the val that is floored&ceiled version of the abs-val that is the blunt sum of all mods, and val gets updated when the Aspect gets modified (I was supposing you had far more reads than mods, so I opted for this "caching". But that's quickly changed if the contrary is proven)

We may be mixing "percentage" with "percents" here, see how this fits: we stopped assuming you even *have* a Cur nor an Abs and go back to the basics. You need a "Current" value for these attributes. But I'm going to call it Abs, but it's the current sum, the "absolute value" of the sums. But you do have the meaning of '1' of Abs, let's say, 1 def is 1% of def, 1 Health is, well, 1 health point. (Just remarked that you say one health point, meaning it's an arbitrary unit that doesn't donvert to anything else). But what does that mean, 1% def ? Actually 45% def means that you get missed by 95% of attacks in mosts cases, it's not exactly a percentage, right ? It's a unit. What's one point of held protection ? well, it nullifies itself with one point of held magnitude ! What's a point of Perception ? A feet ! 1% of def is what nullifies 1% of To-Hit...

So, what is Cur ? The only thing I find making sense is an old post from Arcanaville about Cur being something like (Abs-Min)/(Max-Min), meaning that with an attribute being in between 0 and a max, it's the normalized value of Abs to the Max.

Ok, I understand, but do you do realize this is inefficient ? You could store the unresistable values somewhere specifically for that, but that would nullify my "resistible cancellation is an irresistible mod of opposite of resited value", the workaround I found was cloning irresistible resistance buffs in another aspect. Also, unresistable resistance debuffs don't exist in the game, as far as I know about player powers. Not even [Rest]. Do you know one that I don't know ? Codewalker, could you do a quick check on the whole powers.bin ? (recreate a City of Data somewhere with a modified algorithm to print the name of the power that bears such an effect)

Highly unefficient, that's a logic-based test for each irresistible buff on a list for each entity that has irresistible buffs, for each iteration.

the only thing that needs to be time-aware is the thing that sees the powers and effects and keep tracks of the entities. I would never do an engine without *events*, that is, "entity X wants to launch power Y with target Z" from AI and client, and "auto-power launched" from the *clock*, so at least that is tricky. But I did it as time-aware as it needed to be. Attribmods are not, in essence, time-aware, Effects are. You're lucky I even coded an Effect or Entity class, but that was to have clean and useable code in the long run.

You've totally seen through me now. But I've not called it complete yet either, the "bulk" of the problem indeed lies here but is similar to making a full power engine, which is going to be done next week-end normally. You do the infrastructure before really coding, you do the data structures before making algorithms and functions that are going to handle them. That is the same here, I made the Entity-Attribute-Aspect, and the (Power)-Effect-Executable hierarchies, what's going to be linking them all is a fully time-Entities-Power-aware engine, which is actually more than just a simple attrib-mod calculator that can calculate modifications at any moment. But it does require that.

In fact, everybody always tend to think they are better than they are, because they don't expect external events that nearly always make you slower, not faster.

That was roughly what I was aiming to do. Try, if not keeping tabs of hours, maybe half-days equivalents or something, to measure this 40-50 hours. In which language are you coding it in the end ? Consider using C++ but only its best parts, as I did (no virtual inheritance or new operator overloading, but the namespaces, minute amount of operator overloading, and member methods do come in handy). Also, I think you won't need that, but best of luck anyway.

Enhancement are a different beast, I have an idea of how to implement them, but it's going to be Carte Blanche since I didn't see anything about how they could be handled by the server. But given how the Dual Pistols powers work, and how efficient it's going to need to be, I have this idea. But it'll come later.

I think entity spawning can be done by the movement engine, I mean, very basic entity spawning, like an empty shell, to pass to the power engine for such things as summoning pseudo- and full pets and so on. You could these empty shell for effects that would then only need to provide templates to these empty entity, transforming them into full-fledged Ice Storm and whatnot. Also, you could copy your attributes to them to buff their powers exactly as yours, or as default the movement engine creates clones of you as fork/exec does in UNIX.

Did test with a crabspider, you're right. Great! So the question is, do we need (i.e. is there a power with) duration-limited +-X Cur effects ? (we do need one-shot Cur mods, that's not the question) But that's in the event that Cur is just a 0-100% representation of Abs in regard to Min and Max as you said in another thread. But I'm beginning to understand given your formula you wrote below that maybe in Cur are added resistible mods and in Abs the irresistible mods. Or in Cur time-restricted mods, and in Abs time-infinite (or one-shot) mods. So what is right ?

I agree with you, as I said, and as you could see in the code since there is no "period" field for an attribmod, it doesn't support "_oT" effects now. In that sense, I failed, but I didn't want to get into time-related (to see the "why" of that, and your question, see ** below)


Just to be sure I understand, so what you meant was "resistable buffs are resisted only by the unresistable resistance buffs". Actually, what I implemented was "resistable resistance buffs and debuffs are resisted only by the unresistable resistance buffs" and "other resistible buffs and debuffs are resisted by the net resistance, whether by resisted or unresisted buffs and debuffs". Maybe that's not true. I think that's what is implemented on the server, but in this case any resistible resist buff is going to be resisted by itself or any other similar effect ! And I didn't see any case of powers like that, at least for damage resistance, that's why I said "don't make resistible resistance buffs" because their effect is... unpredictable.

I special cased resistible resist modifiers, yes. (I have functions for resistible modifiers and other functions for irresistible modifiers) It's already done, and it's necessary for the above to work, at least because "resistible resistance debuffs gets resisted by resistance buffs".

Well, mid's also order them like that, as well as in-game descriptions and real numbers, if it's of any use to you, but they may be incorrect !!! But all descriptions I can see right now order them as damage first, then debuff. Also, you order Cur and Abs aspects before resist, so even if these mods are listed, or applied, in the order of Aspects, I am right.

As I said, it is an attribmod calculator. It's not a power calculator, attribmods are only a part of the power effects (other beings summons, grant powers, etc), so you need this attribmod calculator to make the power calculator, and you need that last one to make the combat engine. In your own previous **words, highlighted for emphase:
So I did end up overtiming this "assignment" (or challenge, we are not in school anymore) since I didn't manage to do it "for the full duration of those attribmods, moment by moment", but that necessitates time-awareness, an "engine" aspect, or at least it's stupid to implement it outside an engine (or loop) because it's going to be rewriting when you have to do the engine, so I prefered to do the engine outright. In any case, I avertised "3 weekends to implement it, 3 more to optimize it" and since I optimized a bit (that's my weakness), the result of this experiment is in the gray area. But even 12 week-ends is a tad less than 3000 hours. But to your defense, these 12 week-ends are just the writing of the implementation I already thought up in my mind, and that is based on your analysis of what the server did or closely did. So in total, that is 3000 hours or even more, but most of the work is already done somewhere.

if you're refering to your previous quote, you did say at that time that the bold+"moment by moment" part was "like at most 1/6th of a full combat engine". I do realize 1% is less than 16,67% (1/6th) but that is one hell of a margin.

But let's stop playing "that's what you said" "-No what I said", "That's not what I meant"... Someone earlier in this thread posted a link that basically said it's impossible to plan or estimate a plan effectively because there are so many unknowns, either that or you have an all-seeing eye and/or pure luck, or take excessive amounts of margin, and guess what, you and I are just trying to guesstimate the time it would take to code this. And I'm the only one to actually work to try to measure that, and you're the only one able, or at the very least the best fit, to evaluate this. You already corrected approximately 5 things I misunderstood or thought I knew, and I may have corrected myself to 3 or 4 on my own by looking at the Paragonwiki and City of Data, and Codewalker did some more. I think I did ridiculize myself quite well already, but I want more because my mind just can't stop thinking how to implement the thing. I guess it thinks it's a hero.

I think we have sufficiently derailed the thread here, in fact, it may already be overtaken. I would like to take this moment to (finally) apologize to Bill Z. Arcanaville, would you like to continue this project discussion/report/criticism in another thread, maybe in another forum ? (there is a city sunset category over at the Titan Network)

Yet, everything is just prevented by actually *reading* the header, where the overloaded new operator is defined...

blame the poor habits, not the language (again, no language does prevent its users from making stupidities)

Template also provide meta-programming, as I did in Entity.details. You may have headaches looking at that, wear reading glasses, even if you don't need them. Especially since you're not a fan of templates.

Dynamic calculation is very attractive, simplicity-wise, but it's a ressource hog, especially when it's not so costly to make tables and static code these days, thank the low RAM price !

And again, I'd like to apologize for only making an attribmod calculator, I thought it was only that, that was asked, not an attribmod engine. But basically, you just need to put that in a loop to make it an engine. And you also need to feed the loop, but I simply refuse to do that without the City of Data's generator as reference, as ugly and as incomplete as it may be considered by its genitors

Well, I didn't want to get into the power parsing part of the engine, because someone else already did it, so I only made the calculation toolbox, yes. The engine still lacks input this way, you are totally right.

I actually remembered something about inspirations being somewhat of normal powers, but the problem is you always need 4 small insps to get full health, even with Max health buffs. It's explicitly put even on the description: +75% heal. Unless Cur behaves I coded it, you can't make a "+X% heal" effect. And I didn't know there were other "+-X%", as in, "+-X% of max", they are all absolute modifiers, but I would like to know them if they exist. And as you invoked later, you have to have some +X% effects somewhere. And wether +cur effects wear of or not is depending on the "duration" attribute of the effect. If duration X is >0s, there is a cancellation effect that is spawned and set to be resolved X later. But that requires a full power/effect engine (especially registering current effects on an entity).

It does because resistible effects and irresistible effects are mutually exclusive, and each effect is applied separately. "Resistible" only means you have to apply the target's resistance (or target's resistance buffs in case of resistance) value before applying the mod. I think.

(Note I did write "Resistible RESIST buffs, all other buffs can be resistible, does that answer your concern ?)
IIRC, the Original MoG did what ? It was a, irresistible +100% res heal (or more, to cut heals), +100% irresistible heal mod (to remove any damage), -75% irresistible heal mod after a 0,1sec delay (to put you at low health from full health), -10000% cur regen (to cut regen), and insane amounts of def and res, why would it need to have resistible *resist* buffs ? I'm at a loss here

I may have been imprecise again, this is for Res buffs only (hence the comment is near the ResBuf aspect of an attribute)

Well, as I said, since it's a one-shot calculator only at the moment, and (as you can see on the City of Data) since the damage is listed first before the resistible resistance debuff, should the power resolution method (not written at the moment) resolve effects in their order, the first tick of damage is not under the influence of the debuffs, but all the other ticks (resolved laters) are.

I've had problems with geany (a lightweight IDE) not properly recognizing .h as C++ headers but as C headers instead, making it unable to parse the file properly and I had to change the document's language by hand each time I opened a C++ .h header >_<

Some formulas are in Effect, others in Attribs*, and you've got to look at Aspect to understand them. Also, they are also used by encapsulation in Entity (to make a single call to an entity's method is single-pass as the layout of the aspects in an entity is fixed thanks to the use of arrays and enums)

The target is void* because it could be a Location in case of powers that summoned entities. Well, it could also be an Entity, created at power launch time, but empty, and then modified by the power effect, similarly to fork/exec. Actually, that would prevent the headache of making the power location-aware, that would also carry out the current buffs and debuffs, and then you only have to ignore them in case of ignoreBuffs&Enhancements and apply the summoning power's enhancements to the entity... I like it! If I have to implement the Summon kind of Effects, I'd definitely do that.

Also, you may notice that there seem to be an awful lot of functions involved to just modify a mod once you know the value and attrib and aspect targeted. But it should be optimized out because of inlining and templates, it just doesn't show in the debug because there is no optimization. I wouldn't be against a rewrite either if it keeps the optimality.

*: Especially the special cases and Aspect clamped value caching (val is the clamped, abs_val is the unclamped value for modification). Had to do that in Attribs because it's another or two other aspects that sometimes dictate the range of an aspect, like Min and Max limit Abs (and are involved in the calculation of Cur), and MaxMax restricts Max, and then Str and Res are also limited. So it only makes sense when you have all the aspects.

Thanks for the transition, here is the calculator source code, disclaimer: IT'S OF NO USE TO NON-PROGRAMMERS, it's in C++, it's ugly, but it comes optimized a bit. Normally. Comes also with code stubs, follow the main to find only the useful bits.

I also only had time to test (and debug, don't forget debug, debug takes time, especially when you coded tired, tired code is a hive of bug) the paragonwiki brute Energy resistance case.

I was in the process of making damage tests afterward, if somebody wills to add them to the main and do the test themselves as curiosity (I don't even know if it's going to work !) just do another effect with a negative scale (if someone here think damages are a positive thing ...!) modifying the Abs aspect of the Energy attribute. This is hardwired to modify the health's Abs, but leverages the general formulas to get the resistances and strength of the damage type.

The Effects are basic, and the attribmod effects code is meant to work only for one-shots right now, the DoesNotStackFromSameCaster clause is not handled right now because I need to register them on the Entity, but the formulas are done and should work (as always when programming, if you forget the bugs :P).

What you say !! (quoting my zero wing video in my sig)

I'm going to answer that myself. In melee powers for instance, you don't benefit from range boosting, obviously, and VIP Temp powers don't benefit from your Damage nor Recharge. In fact, these flags should only be for Damage, Recharge and Range, I think. Am I right ?

Recharge Strength is not taken into account inside an attribmod, ever. Well it may be, but in the end it's not, because recharge mods are generally (always?) [ignore buffs and enhancements].

and debuffs. I'm talking about that one.

that one is done, it was easier since it could be an attribmod attribute >_>

hmmm where is that used for instance ? Because that could be implemented as flagging each involved power effects with the previous (Effect-scale) flag on each effect that gets hit by this (power-scale) flag. So I don't see why it exists, but it does, you say ? So on which power ?