Solarverse

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.

Meh, my primary issue is that we have enough already soaking up the Melee room. The problem that nobody seems to be acknowledging is that being in melee range is like a game of musical chairs. There is only so much room for players in that circle of chairs. One too many creates a chaotic experience when your character is being pushed around by the flawed collision mechanics. If those collision mechanics were to be say...fixed, to where characters do not bump around other characters, then I wouldn't care one way or another how many players all want to be in the middle of a mob. However, until that changes, it will continue to be an annoyance to Tanks who are trying to stay centered with the Mobs and maintain aggro without being pushed outside those mobs. "Blappers" add salt to the already open wound on this issue. A Blaster was supposed to be a Ranged Damage AT, but because of the sad design flaw that Blasters are, players have been playing them as if they are a Melee AT. I don't see that part ever changing, too many people would have a fit if that were to change, so the only logical solution here is to fix all the bumping around we are seeing with the flawed collision mechanics. If that gets fixed, problem solved.

Curious. Why is that? Are the modern cards too sophisticated for this game? Say...the GTX 4080?

That's pretty much my point, if a Blaster has potential to out play a Scrapper, that goes far beyond their potential and tells me that Blasters are a completely broken AT.

First, I was facetious, that is why at the end I said, "Seriously though" meaning, all joking aside... Now, having said that, I have to ask, you don't play Tanks much on teams, do you? I am guessing you have never been pushed almost clear across the room due to too many players all trying to get in to the middle of mobs. If Blasters are doing more damage than Scrappers, or even doing as much damage as Scrappers, that is clearly a sign that the AT is broken. The last thing a Blaster should be wanting is to get in to melee distance of mobs. The fact Blappers exist tells me the fundamental problem is with the AT itself. The Mob area gets pretty darn crowded, adding Blasters to the list of ATs that gets within melee range is overkill IMO. Especially since it is an overkill that goes beyond the AT design.

I don't doubt it, lol. I can hear you now, "Hold on, switching to my BLAPPER!@!!!@!!!" lol

As a Tank, stay out of my mobs... There are too many players in melee range as it is, far too many. You get shoved all over the place by the collision mechanics, always fighting for position. Add Blasters who think they are scrappers to that mix, the problem becomes even worse. When that happens, I stop taunting and turn off taunt auras and watch the so called blappers die. Seriously though, please stay out of melee, it's too crowded already.

Even that I would think be painfully obvious. Two characters, doing the exact same thing at the exact same time. It might even be more obvious than somebody having an alt account follow them using the same power over and over. The person who accused me did nothing more than look at our builds, discover they were the same, seen that our characters matched outfits and looks, and then of course, we know what transpired from there...nothing good. However, like Ghost said, chances are they simply had a bad day. At least I hope that is all it was.

I would think alt boxing would be too obvious.

Now why on Earth do you have to play the theme song to the only movie to ever make me cry? P.S. I take that back, A.I. made me cry too, heh. And look, I'm a big burly tough dude, I don't cry easily, but damn...those two movies, if they don't jerk tears in your eyes, you simply aren't human, lol.

Thanks, Ghost, really appreciate that. I checked the global name and like you, I had run with this one before. Kind of a serious type from what I can recall, but as you said, smooth. Odd thing is, if they wanted us to prove we weren't botting, I am sure we could have thought of something to prove that it was two separate people playing. Could've should've but didn't, heh.

I forgot all about that part on Mudd's Women, lol.