Solarverse

All other sets have resistance to Debuffs. Regen? Gets one. One Debuff resist to Regen at 25% (assuming mids is correct) which that all in of itself is a huge backseat to other sets.

This is the problem. I can take any build in this game and add IOs to it and make it look impressive on paper, but what is not being taken in to consideration is all of the magnificent ways the NPC's (especially considering a LOT of the NPC's have been given buffs, or new versions to make them stronger; IE Super Stunners, or some of the new Paragon Protectors) which rips to shreds all of those pretty little stats, since you have absolutely zero resistance to debuffs. In a split second, your Defense can go to -50 and your resistance can be crippled to almost 0 or below and your Regeneration can be brought to its knees. You have nothing to fight back on this. Also, you are using a Tank build, which gets the absolute best version of Regen to prove some point. That is doing exactly as I asked not to do. I did say, "Please, do not take the absolute best possible build and prove a point based on the absolute best possible builds." or something to that effect. Using the best possible class and using the best possible build while ignoring the fact that there are a LOT of NPC types that would rip that to shreds paints a pretty little picture of a power set that is absolute garbage. Regen is not known for being trash for no reason. It's not some myth people make up, it's not some mass hysteria. It is a very real thing and everyone in general understands that the set is garbage and needs work. If we really want this set to be looked at and fixed, we have to stop trying to paint pretty little pictures of the best possible version of the sets while ignoring how easily that can be destroyed. For example, I can take you in to a PvP match against a Rad/Dark Defender and have you at your knees in mere seconds. You have nothing to resist it with. I don't PvP, but I sure as hell did not forget how to PvP, and it wouldn't take much to make those impressive numbers look like child's play.

I'm probably going to end up deleting it and reinstall it, since I keep getting pop-ups to download the update, but the link to the update is a 404 error code; meaning page not found.

Hmmm, I really dig @Bopper's ideas on the first page of the first link. Whatever happened to Bopper, anyway? I would 100% welcome his input on this.

Yeah, but I am wrapped up in chocolate! 😄

Other sets gave full effectiveness, where it did not get the full effectiveness was with the status resists. So not as much -Recovery/-Endurance Resists. As far as keeping it a click heavy set, remember, IH was once a toggle, it was not always so click heavy. I would like to get the set back to that again, where it is not so click heavy and not so click dependent.

Sorry, don't be mad at me but I just had to fix that. It makes zero sense that Regen would not have -recovery/-endurance resistance. It shouldn't have Elec levels of resistance, but at very least it should have Rad Armor levels of resistance. The only way I would find this something needed is if the Devs are going to still make the set a click heavy set. Which needs to change, it should be added to Fast Healing. The reason they initially did not get Quick Recovery was because it was not built to be a staying power class, it was a stick and move class. Now it is very much a Scrapper'y class that would now benifit greatly with Quick Recovery built in to Fast Healing. To be blunt, because IH was made a click and no longer a toggle, dare I say Integration could use another 100% on top of the current 100%, on top of the 50%. I disagree. Half effectiveness? If the class was still a stick and move class, I could agree, however, Stalkers are not that class anymore. They require the same stats as a Scrapper. They already don't have the same hitpoints, so therefore they already do not Regen near as much HP/Sec because of this, now if you hit them with a lesser Regen, it will hit Stalkers twice as hard. I express caution in this type of thinking, Stalkers are not the sub-class they once were.

I can take a turd, (Regen) roll it up in chocolate (IO's) and call it a tootsie roll, but we both know it's still just a turd. You're right about one thing, Regen isn't for everyone. Neither are turds.

I found myself frustrated last night because often when I set my Task Forces to either +1 or +2 on PUG teams, sadly, none of that seems to matter when all that has to happen is another player on the team zone in to a new zone first, next thing you know I am now being forced to do a Task Force at -1. Here is how this works, if you are running a Task Force in Brickstown, then suddenly the next mission is in Atlas Park, whichever player zones in to Atlas Park now becomes the anchor for what level the mobs spawn at. Another player once tried to argue with me over this when we were running a Posi 2 and suddenly after zoning to Faultline the mobs were spawning at +4, he says that bug was fixed, however, clearly it was not fixed since I was set at +1 to that mission. Just to clarify, I am one of the rare players who knows that if a mission is set to +0, the spawns will be +0 and +1's. If it is set to +1, the mobs will be +1 and +2's. Yeah, not many players in game know this and even when you try and explain it to them, they don't believe you and they say things like, "That's never happened on any of my missions." Yeah, sure...okay there, Mr. Wizard. So no, mobs being occasionally +1 to my setting is not the issue I am having, the Task Forces are actually setting to whomever enters the zones first upon a zone change. Can we please get this fixed? I'm assuming there was an attempted fix once already? Judging by in game conversations anyway.

Where on Earth have you been? This set has been picked apart molecule by molecule over the years. I think a hell of a lot more has been said than just "not strong enough" over the years too. You come in here like a bull in a china shop thumbing down everything, not even having a single clue that this topic has been discussed to hell and back, then tell us that we are being vague? Here, here's a thumb down right back at ya. The set has been debated to death and it's time for action to be made with the set, not time for more debates. Agreed. One thing that ticks me off is that Regen was the first set that gave you +Recovery. Yet I have to tuck tail and run every time a Super Stunner rezes....while watching other newer sets not even be phased by the -Endurance of Super Stunner Rez. Recovery most certainly needs a high level of -Recovery and -Endurance Drain Resistance. I will say, you are correct, the animation times for the Heals often end up with me dead because I clicked, and then by the time the animation actually hit and the heal applied, it was too late. This happens when there is zero mitigation. Telling people that a post that brings light to a set that has been destroyed and then overlooked for 15 years a "whinepost" isn't going to garner support for your idea. A quick look through your history and we can see you yourself are guilty of "whine posting," (how about those Force Fields?) so let's not do that, shall we? Do not undermine problems in this way, it's a cheep shot and undermines your character. Agreed, it was given far too many clicks, remember, one of those clicks was once a toggle. I'm not saying that is the fix, but what I am saying is that it wasn't so bad that way when it come to how many powers needed to be clicked. Add on top of that, how long it takes those clicks to activate, which is the leading cause of my in game deaths since I have zero mitigation to keep me in the fight while waiting for the eternal animation to fire off for that precious heal... Couldn't agree more. Very nicely done. I am not a fan of scaling regen to number of NPCs. That has to be tweaked perfectly. The last thing I want is to be staying my ground against large mobs, but run my tail off if I see an AV. There are so many sets that can just go afk while AVs are hitting them, not sure why Regen has to be any different. That sounds to me like AVs need a buff, why balance one set around AVs while leaving all the other sets completely OP? The answer should be to buff AV's, they die way too fast anyway. Agreed, it needs -Regen Resist, but not anything ridiculous as 95%. Again, agreed. Not trying to turn this set in to a copy paste of WB, Bio or Rad. Again, I fully agree. The set does not need a fully functional Dull Pain and Absorb shields. Nah, I think anyone who has played this game long enough to know what it was like to play Regen before the Nerf in 2004, is very aware of how hard it can be.

Oh, I love the memes that poke fun at necro'd threads, I myself have made a few on these very boards. However, they are tongue in cheek, made to get a laugh memes. What I do not do is come in to a thread like some hall monitor and thumb it down without explanation what-so-ever. And to be honest, I always thought Bill was better than that. That's the thing, the Devs have never sought our permission before implementing something, if they had, Sonic's Cone power would not have a repel function right now...I think sometimes the Devs are just trying to get the players in to serious arguments when they implement shit like that. But, what is done is done, it's their game, they can do whatever they like and I accept that. So if I can accept that, then others should also be able to accept whatever changes the Devs deem fit for Regen. We as players have thrown out a lot of great ideas over the years, it's up to the Dev team to decide which ones, if any, they wish to implement. However, the set as it stands now...well, as @Captain Fabulous has stated, it's a fantastic set for Debt Badges and that in itself is overpowered. /nerfregen. 😄

I feel like if Regen were to be reverted to its original state, it still wouldn't stack up to other sets these days against some of the mobs we see in higher level stuff. Some of the people who were posting on this thread back in 2019 had some decent ideas, turning Quick Recovery in to a Fast Healing/Quick Recovery hybrid while giving it a 25% unenhanceable boost, then making Fast Healing act more like a Heal+Absorb Shield. There were a lot of good ideas thrown around in here. As far as Willpower being Regen...I simply will never accept that, even if I grow old and die or have a heart attack and die today, I will go to my grave never accepting that. 😄

It was relevant, and if my post didn't show that, then I don't know what to tell the guy. The thread had to be necroed to show cause. Also, I don't give a damn about necroed this or that. You necro a thread people get their panties in a bunch, if you post a new thread people get their panties in a bunch because there are already existing topics on it, you can't win and I am not here to make people happy, I am here to discuss a topic that is almost as old as this game is. If that is really what that was all about, he can get over himself. Not to mention, the whole "don't necro threads" is just dumb anyway. There is no reason what-so-ever to get upset about that. It is some unwritten rule that only forum elites try and enforce. The earliest iteration of this is when people wanted a particular subject to go away because they didn't want it being talked about, hence forth necroing topics suddenly became "bad" yet nobody can give a viable reason why it is considered bad. Truth be told, I did a google search on the topic and this thread came up. So since my issue with Regen is relevant to how long people have been asking for a fix to it, it became relevant to post the topic. There is absolute nothing wrong with posting on an old thread...that whole, "don't necro threads" rule is just completely made up and there is no merit to it what-so-ever other than to try and control people...and I have never been one that you can control.

It was relevant.

@Greycat Are you really going to disagree? So tell me, if Regen is just so damn perfect, why do so many people feel like it's just such a trashy set? Back in 2019, it seems everyone agreed it needed help, now suddenly it's fine? Come on, my man...

My God, such great ideas on this thread way back in June of 2019, and the set is still garbage and only best in PvP/Theme. Practical use is just subpar at very best, with only the absolute best builds. This set should not depend on an absolute best build to perform well. I play Regeneration, but let's make no mistake about it, it has absolutely nothing to do with the set being good, it has everything to do with nostalgia and theme. Now, here we are in 2023, almost 2024, and Regen is the same crap that it was on Live. Why the set needed to go from one of the best to one of the worst is beyond me...and why it still remains the red headed stepchild for almost 15 years later is even further beyond me. Now that a new Dev team is in control of this game, I am shocked they did not place some type of a priority on fixing this utterly useless set. The set was nerfed in 2004...it has sucked ever since then. Isn't it about time that changes?

I play human form and feel it could use some love, however, I seen what tri-forms can do these days and was like, "Holy shit....there is no way human form will ever see a buff when Warshades are pulling that crap off." So hopefully they fix what is broken and buff what they feel needs to be buffed at the same time. I can hope anyway. 😄

************** Exception Text ************** System.Net.WebException: The remote server returned an error: (404) Not Found. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result) at System.Net.WebClient.GetWebResponseTaskAsync(WebRequest request) at System.Net.WebClient.DownloadBitsAsync(WebRequest request, Stream writeStream, AsyncOperation asyncOp, Action`3 completionDelegate) at MRBUpdater.Update.Updater_DownloadUpdate() at MRBUpdater.Update.OnShown(Object sender, EventArgs e) at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state) ************** Loaded Assemblies ************** System.Private.CoreLib Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Private.CoreLib.dll ---------------------------------------- MRBUpdater Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/Wraiv/AppData/Roaming/LoadedCamel/MidsReborn/MRBUpdater.dll ---------------------------------------- System.Runtime Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Runtime.dll ---------------------------------------- System.Windows.Forms Assembly Version: 6.0.2.0 Win32 Version: 6.0.1523.11702 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.WindowsDesktop.App/6.0.15/System.Windows.Forms.dll ---------------------------------------- System.ComponentModel.Primitives Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.ComponentModel.Primitives.dll ---------------------------------------- System.Windows.Forms.Primitives Assembly Version: 6.0.2.0 Win32 Version: 6.0.1523.11702 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.WindowsDesktop.App/6.0.15/System.Windows.Forms.Primitives.dll ---------------------------------------- System.Runtime.InteropServices Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Runtime.InteropServices.dll ---------------------------------------- System.Drawing.Primitives Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Drawing.Primitives.dll ---------------------------------------- System.Collections.Specialized Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Collections.Specialized.dll ---------------------------------------- System.Threading Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Threading.dll ---------------------------------------- System.Diagnostics.TraceSource Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Diagnostics.TraceSource.dll ---------------------------------------- System.Collections Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Collections.dll ---------------------------------------- System.Text.Json Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Text.Json.dll ---------------------------------------- System.Drawing.Common Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.WindowsDesktop.App/6.0.15/System.Drawing.Common.dll ---------------------------------------- Microsoft.Win32.Primitives Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/Microsoft.Win32.Primitives.dll ---------------------------------------- System.ComponentModel.EventBasedAsync Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.ComponentModel.EventBasedAsync.dll ---------------------------------------- System.Threading.Thread Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Threading.Thread.dll ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 6.0.1523.11702 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.WindowsDesktop.App/6.0.15/Accessibility.dll ---------------------------------------- System.Collections.Concurrent Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Collections.Concurrent.dll ---------------------------------------- System.Private.Uri Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Private.Uri.dll ---------------------------------------- System.Reflection.Emit.Lightweight Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Reflection.Emit.Lightweight.dll ---------------------------------------- System.Reflection.Primitives Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Reflection.Primitives.dll ---------------------------------------- System.Reflection.Emit.ILGeneration Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Reflection.Emit.ILGeneration.dll ---------------------------------------- System.Memory Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Memory.dll ---------------------------------------- System.Text.Encoding.Extensions Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Text.Encoding.Extensions.dll ---------------------------------------- System.Text.Encodings.Web Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Text.Encodings.Web.dll ---------------------------------------- System.Runtime.Intrinsics Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Runtime.Intrinsics.dll ---------------------------------------- System.Numerics.Vectors Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Numerics.Vectors.dll ---------------------------------------- System.Runtime.CompilerServices.Unsafe Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Runtime.CompilerServices.Unsafe.dll ---------------------------------------- System.ComponentModel.TypeConverter Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.ComponentModel.TypeConverter.dll ---------------------------------------- System.Resources.Extensions Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.WindowsDesktop.App/6.0.15/System.Resources.Extensions.dll ---------------------------------------- System.Drawing Assembly Version: 6.0.2.0 Win32 Version: 6.0.1523.11702 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.WindowsDesktop.App/6.0.15/System.Drawing.dll ---------------------------------------- System.ObjectModel Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.ObjectModel.dll ---------------------------------------- System.Linq Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Linq.dll ---------------------------------------- Microsoft.Win32.SystemEvents Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.WindowsDesktop.App/6.0.15/Microsoft.Win32.SystemEvents.dll ---------------------------------------- System.Collections.NonGeneric Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Collections.NonGeneric.dll ---------------------------------------- System.Diagnostics.Process Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Diagnostics.Process.dll ---------------------------------------- System.Threading.ThreadPool Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Threading.ThreadPool.dll ---------------------------------------- System.Net.WebClient Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Net.WebClient.dll ---------------------------------------- System.Net.Requests Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Net.Requests.dll ---------------------------------------- System.Net.Primitives Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Net.Primitives.dll ---------------------------------------- System.Net.WebHeaderCollection Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Net.WebHeaderCollection.dll ---------------------------------------- System.Net.Http Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Net.Http.dll ---------------------------------------- System.Diagnostics.Tracing Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Diagnostics.Tracing.dll ---------------------------------------- System.Net.ServicePoint Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Net.ServicePoint.dll ---------------------------------------- System.Net.Security Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Net.Security.dll ---------------------------------------- System.Security.Cryptography.X509Certificates Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Security.Cryptography.X509Certificates.dll ---------------------------------------- System.Diagnostics.DiagnosticSource Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Diagnostics.DiagnosticSource.dll ---------------------------------------- System.Net.Sockets Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Net.Sockets.dll ---------------------------------------- System.Threading.Overlapped Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Threading.Overlapped.dll ---------------------------------------- System.Net.NameResolution Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Net.NameResolution.dll ---------------------------------------- System.Security.Cryptography.Primitives Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Security.Cryptography.Primitives.dll ---------------------------------------- System.Security.Principal.Windows Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Security.Principal.Windows.dll ---------------------------------------- System.Security.Claims Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Security.Claims.dll ---------------------------------------- System.Security.Cryptography.Encoding Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Security.Cryptography.Encoding.dll ---------------------------------------- System.Runtime.Loader Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Runtime.Loader.dll ---------------------------------------- System.Diagnostics.StackTrace Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Diagnostics.StackTrace.dll ---------------------------------------- System.Reflection.Metadata Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Reflection.Metadata.dll ---------------------------------------- System.Collections.Immutable Assembly Version: 6.0.0.0 Win32 Version: 6.0.1523.11507 CodeBase: file:///C:/Program%20Files/dotnet/shared/Microsoft.NETCore.App/6.0.15/System.Collections.Immutable.dll ---------------------------------------- ************** JIT Debugging **************

I remember when the Devs first released the information that Heroes and Villains would be swapping roles; that they were allowing for Heroes to be Villains and vice-versa. I remember emphatically expressing how that would be a very bad idea, that it would create balance issues beyond belief to a game that was just starting to feel balanced and that no matter what, it would be a constant struggle battle between Tanks and Brutes, all to appease a crowd that quite frankly, doesn't know their ass from a hole in the ground. I remember telling them it would be completely chaotic and that all these instant gratification players would no longer have a driving reason to play Villain side. (Looks around) I wish they had listened to me.

Why is he putting DoTs in the letter U?

That can't be intended? That looks like a straight up broken mechanic. Could that even be considered an exploit? I mean, no Warshade should be doing that kind of damage. I am shocked this has not already been called out, so I assume the Devs are good with this? What are the thoughts? Not your biased thoughts...come on fellas, what is your honest thoughts bias aside?

Have you tried Ninjas Lately? I'm telling you, they eat through mobs like a powerhouse now. I'm not an MM fan, but I gotta tell ya, that buff Ninjas got was a whopper.

Honestly, knock back doesn't bother me, single target knock back anyway. A blaster has the ability to destroy the target he/she knocks back. It's the AoE that scatters the mob that ticks me off. The mentality of, "You not wanting me to knock back takes from my enjoyment of the game" tends to trump, "Your knock back takes from my enjoyment of the game" for some strange reason that I have never been able to wrap my mind around. Even worse than that though, because knocked back targets tend to run back to the tank if they are allowed to do so, trollers often lock those targets in place AFTER those targets have been scattered. I never say anything in team because...well, somehow my opinion has become the minority over the years, even though at one time my opinion was in the strong majority. I just let it go and play accordingly whenever it happens. I might bitch about it to my wife, or she will bitch about it to me, but neither of us says a word outwardly unless it is on these forums, and only I post the forums, so you only hear half the bitching, lol. She sees what I write and sees the responses, she doesn't want any part of these forums, lol...but when talking to each other, she hates the knock back and random locking down of mobs just as much as I do. I myself have a Blapper (I know, out comes the lynching of, "After all that you said to us and YOU have a Blapper!?!?" comments) however, I don't work my way in to center of mobs and intrude upon the small Space that is being occupied by the Tank, I don't try and annoy the Tank with my unwanted presence in the center of those mobs, I go to the edge of those mobs and unleash my terror. Oddly enough, I do just as well outside the mobs as I have seen Blappers do inside the mobs. Big AoE and all. So I play as respectful to other players as possible. So it's not so much the hate of knock back or blappers, but more of how I have seen players utilize that knock back and blappers.

I am convinced that there is some City of Heroes happy drug being passed around that literally nothing bothers anybody, lol. I hear ya, man. I truly wish I could be as care free about everything as you are...if you guys are on some happy drug, please send it my way so I can not only be okay with problems, like being shoved around and having mobs scattered all over creation, to where the only person who gets enjoyment out of scattering the mobs, is the first person who does it, everyone else gets to hit one, maybe two NPCs with their AoE, or be okay with controllers locking those mobs down AFTER they have been scattered, and not only be okay with it, but love it...then give me that drug too. I know you guys and gals have this drug...stop being so secretive with it! And yes, Sents imo never made sense to me and was the biggest mistake the Devs made in this game second only to knock back, PvP and the aggro cap being lowered to such an extreme low. But, if I too had this wonderful care-free drug you all are taking...maybe I could like that too? lol 😜

Meh, I think most AT's were rushed. Remember, when this game was first shown to us, there were no AT's, there were no power sets. You picked whatever power you wanted. When the last minute change was added in to have AT's and power sets, I think they, in a rush, just threw it all together using the existing powers they had available, they were after all under a deadline. However, like you said, that is an old dusty road and there isn't much point in pushing the flip side to it, since it doesn't matter, we have what we have and it won't be changing. The only thing we can change is the collision mechanics so that it stops being a problem, until then, Blappers will continue to annoy me.