I went ahead and made a beta release.

I'm currently working on Command Queues, Occulus Auto Attack, Post Mortem XP, and health bar scaling. However, I don't see any brilliant solutions to any of them right now. The last fix I made was the Sacrifice Fix and it was more on a whim than a purposeful find.

I figure as long as pacov puts up with me losing (nearly) every game I play with him, I should try to honor his patch release requests.

I imagine #6 would be an easy fix. You should include that in 1.02 ^^;

I've also tested Theugist's Cap's regen effect and it does in fact work. You can probably remove item 3 from the list (or at least put it into "a cannot reproduce" section for archival purposes. 

I did some experimenting and /ALL/ "on hit" procs (such as Journeyman's) cannot proc while damage is being negated (Bramble Shield, Oak's Shield, Groffling Warplate, Orb of Defiance). I'm not certain if this is a bug, but I'd like to get the community's input on it. Note that this does not include Evasion, since you aren't being hit if you evade  

You should also include an extra '0' at the end of all Yeti stats "on accident"

re: "War Score" display at each teams' citadel is incorrect.

I went looking for where this occured once and it wasn't obvious at the time. I'll move it up on my priority list just for you.

re: Poisoned Blood

I'm pretty sure damaging LE was unintended. Before the fix LE could farm himself into artifacts really easily. After the fix he can't farm himself. Healing his teammates is a judgement call. Given that no LE should ever include part of his strategy as dying at location X, I don't feel the potion drop is uncalled for. Furthermore once LE gets the ability he loses the ability to drop mana potions or useful health potions. I picked this way because it reduces micro and allows for a more forgiving game. LE's teammates shouldn't have to worry about him making lethal potions for them either, especially since death effects are meant to give your team a boost. All in all it doesn't matter. The number of deaths that a LE should experience is already a trivial amount, especially if his team is winning.

re: Oak Shield

My understanding was that lag was causing people to think their teleport was still protected by Oak shield (when it wasn't) and then thinking it was buggy when it was interrupted. Your interpretation is that someone is interrupted the cast of Oak shield. I'm not sure which is correctly describing the reported problem.

re: Shield Effects

I looked into the code a while back when this was previously brought up. The code works as expected. If the damage fails to exceed the shield value, then the damage code exits before doing hit effects. This is definitely not a bug. It may be a balance issue, but I'm trying to avoid making balance calls.

re: Tool Tip Upgrades

I had been the one working on the updated SkillInfo Mod you describe. I stopped because it was getting problematic. One problem is that the mod requires a strings_db.lua, a user specific language file (i.e., English, German, French, etc), and mod files that change the actual skills.

strings_db.lua

• Allows me to change the strings without disrupting the game for other language players
• Forces me to use the pre-existing string pointers

mod files

• I can add new strings
  
• I lose the ability to support other language players

As you can see, I can't have both new strings and support for other languages. As it stands now the UberFix is language independent and I'd like to keep it that way.

An example of this is how the Torch Bearer's Fix Aura is coded. It has one string to describe all the levels of the popup tooltip on your current buff display. I can't change it to reflect one specific level, because it is used for all three levels of the buff.

I'm not sure what a good solution is. The best idea I have so far is to go through the strings_db.lua and rewrite everything just for the English file, but it isn't a good solution.

hmm... things were pretty stable w regards to uberfix 1.02 (though I appear to be having some comp issues lately unrelated).  I'm trying to figure out if there is a problem from uberfix 1.00.  hehe.  I noticed that during game, I'd get tracker placed on me by a reg.  The occ would cast brain storm on me, but it I'd still see the icon for tracker... then, maybe 5-10 seconds later, tracker would drop.  The oc player indicated that tracker would drop off of him the second he cast it though.  Not sure if I'm crazy or if its just something weird. 

re: AI sitting in base.

That's very odd, very odd. What Demigod was it?

re: Regulus Tracking

That's also odd. I'd like to have this replicated if possible.

You can reproduce QoT switching target issues by having her pursue a moving target moving  directly away from her then having new targets come within her attack radius in between her attack animations. 

Queen is attacking Enemy and is hitting each time

       |  (creeps)

       |       |     

       |      \/

-----(T)

          <--- Enemy        <----Queen

Creeps move into range, she will start hitting them, or perhaps alternate

       |  

       |         

       |     (creeps)

-----(T)

 <--- Enemy        <----Queen

Creeps are no longer "new" targets and stop being attacked. Tower becomes new target

       |  

       |         

       |    

-----(T)     (creeps)

Enemy     Queen

Queen resumes attacking main target

                 |  

                 |         

                 |    

-------------(T)     

Enemy     Queen   (creeps)

Ptarth - you have my vote for taking uberfix 1.02 out of beta.  If you agree, please do so and we'll use that for the tournament. 

brandon - start reading at about reply 164 - morph and ptarth talked this out.  Here's a snippet:

so the bottom line is that the code to have it turn off on low health is in there, but it wasn't implemented correctly, so a bugfix was required.  If the code to turn off ooze was absent, then it would be a matter of debate as to what the dev's intent was (was it just an oversight or did they mean to allow for ub suicides as an escape).  But the code is there, it just doesn't work right without a fix.

I'm not looking to personally rehash what they discussed 20 replies or so ago (mayhaps one of them will chime in), but just some thoughts that haven't really been discussed regarding the impact of this change and the ability to randomly commit suicides.

From a viable strategy point, using any character, if I go for a kill, say, in a group of enemy towers and pull it off, but then find myself killed by "forces of darkness/light," its not that bad a thing as I got the full money for a kill and the other team got squat as the "forces of darkness/light" got 0 gold for the kill.  It's a reasonable strategy (in certain situations) to let a tower kill to avoid giving someone on the other team a kill.  Anyway, this option is available to all dgs.

Onto the beast - as it stands, the UB can take it a step further by trying to use the method I described or simply by engaging in combat with anyone.  A ub can run up and engage an opponent with ooze enabled.  In order for the ub to suicide, all that needs to happen is for the person that is fighting him is to drop him to around <100 hp or so.  There aren't many scenarios where a ub will get dropped right down to that threshold of <100 hp with the exception of intense combat.  At which point, I'd argue that because the odds that you'll hit <100 hp on a ub and get the "commit suicide" screen are extremely low, its not a viable strategy at all to be willing to have the ub on your team pull that. 

Also, let's talk about committing suicide in dg.  The code in the game (not talking about uberfix) does turn off the ooze at <100 hp.  In short, if you aren't in combat, its impossible to trigger a suicide.  And suicide is the taking of one's own life, yes?  So, as the game is coded its impossible to kill yourself without someone/something assisting.  I'd argue that the mere fact that ooze turns off should make it clear that it is not designed to kill the UB.  Otherwise there would be no point in having that code at all. 

edit - and I'd add, its not that game breaking or even much of a nerf.  The ub is hardly a weak dg and this simply gave players an extremely low % chance (2-5% I'd guess) of "committing suicide" when in reality, 1 additional auto-attack from any dg would have killed him (as his hp has be below 100).  And again, the odds of someone pulling this off as a strategy are extremely low - meaning, its just dumb luck if a player "commits suicide" by taking damage in a fight.

re:awuffable's posts

I'm looking into this still. I promise to have a nice wall of text once I finish trying things.

re:Unclean Beast Ooze Suicide

I had thought that I had finally put this argument to rest, as per the discussion around 164 as referenced by pacov.

• pacov did a good summary of the issue and the documentation of the changes.
• I did not remove the suicide ability from the Unclean Beast. He never had that ability. He did, however, have an ability that under certain circumstances resulted in his death.
• The Unclean Beast had two bits of code that were in the wrong order which allowed Ooze to kill the user under certain circumstances. I switched the two bits to be in the correct order which does stop the Unclean Beast from using Ooze to kill himself.
• If you refer back to those posts you can see the exact change I made.
• The death credit function contains a segment that checks to see if a hero unit (demigod) was killed by itself. If so it then prints the "X Suicide" message. To my knowledge this only occurred with the Unclean Beast. The other common occurrence of a Demigod killing themselves was when Lord Erebus drinks his own Poisoned Blood potion. This event did not trigger a suicide message, instead it triggers a "X kills X" message. This point and more discussion about the suicide message was also discussed a few posts earlier than the code relating to the Ooze Fix.

re: UberFix is changing Game Balance

• I've put a lot of effort into making sure that none of the fixes in the UberFix are anything but bug fixes. It annoys me that you have so quickly come to the conclusion that I am including game balance changes that are not fixes.
• If all of this is not sufficient to demonstrate that this effect was unintended and does not improve game play, what evidence would?

• On the counter side, what evidence is there that Ooze was intended to allow the Unclean Beast to suicide?
  • The presence of the suicide code?
    
    • It is generic to all demigods. The only other case of it occurring doesn't even use the function correctly.
    • It isn't sufficient to demonstrate intent.
  • There are no tooltip messages saying the Unclean Beast can kill himself with Ooze. Even the Ooze ability description says nothing about it.

Also, how do you guys read all this crap??  LoL.  Whatever happened to economics short sweet beautiful answers.  

Just a joke.  

The End.

Eh.  I'm not going to argue a stupid change.

I disagree and I am sure I can keep pointing things out and this can turn into something even more pointless... but there is no point.  I concede to your greatness.

: )

The End.