Felis Noctu

As for the topic at hand, I think my best end-draining characters in the past were an elec/elec defender, an elec/kin controller, and an elec/energy aura brute. Surprisingly enough, despite being the most obvious choice, electricity isn't always the answer. Energy Drain's effect can be pretty devastating, especially once you get your recharge times down.

Forgiven then, and I also apologize. It's a sore spot for me, so I tend to overreact. If the context helps frame my reaction, I've been incredibly frustrated with the situation surrounding CoD. Setting certain subjects of drama aside, it's one of, if not the, most important resource the community has, and it's been abandoned with no communication. Knowing what's necessary to parse that data is such a unique set of knowledge as well. We've been trying our best to ensure Mids is accurate, but doing so is exponentially harder when we have to estimate and guess instead of just having the most recent raw data right in front of us, you know? I keep desperately hoping we'll find someone who can update Ruby's parser for the new data format and headers, even if it's just to have the text files in front of us again.

There's a large number of functionality bugs that we've fixed, sitting and waiting for the next app release. The update itself has been delayed as various frameworks were updated in the background, and the current updater tool doesn't like changing some of what needs to be changed. That being said... If this is an old build that you're trying to load, that may be why some things aren't registering properly. Zed corrected an issue relatively recently that caused certain effects to be toggled incorrectly on old build formats. Resaving the build actually doesn't fix the issue, as it's a hidden boolean value. Adaptation Stances may be related to this, but it may also be something else entirely. If you want to jump the wait for the update, what we recommend is reproducing the build starting from a new file, then see if the inconsistencies still exist. If they do, that may be something we can investigate. Also, don't sit on the green Totals tab! (the pop-up View Totals window is still ok) There are known issues with the tab, seemingly stemming from functionality that predates us, and possibly even Pine's. We're still trying to dig up all the weirdness it causes.

Several things: One, City of Data is coming up on a year out of date, so you can't 100% rely on it either. It is gradually becoming less useful. Two, Mids is pretty accurate, as we were getting our information from the JSON files that first RubyRed, then Uberguy, produced. Human error is always a factor, but that can also be resolved with the next point: Which is Three, there's a lot of data, and only a few of us, so it really helps when people report these errors to us. Especially since Uberguy had the only working means of parsing the hard data directly from the game files, and he's not willing to share his magical tool, so we're back to square one. That is, community input and testing. With the barely veiled frustrated snark out of the way... @Scarlet Shocker did in fact join us in the Mids discord and report it to us, and after a bunch of running around, ranting, swearing, beating our heads against the wall, cursing the gods, and quadruple-checking everything, we verified that this data is in fact missing from Mids. That's likely because these powers have complex formulae for other effects, so these were accidentally forgotten in the mess. So now we're prepped to correct the issue. Thank you Scarlet! https://discord.com/channels/593336669004890113/1363344114866978846

I appreciate it! I would like to add @Zed and @Bopper to that list. Zed's been keeping things afloat while Metalios and I generally experience life in other places, and Bopper has helped with numerous formulas and fixing weird mismatches between the game and Mids.

Thank you for all your hard work with these builds! I've used quite a few of them as templates to make my concept builds have a bit more oomph and stability. I did want to stick my head in here and mention as well: For anyone who grabs the older builds in .mxd format and notices that some numbers from toggle powers or procs aren't working correctly, this is a known issue in the current release version of Mids and how it parses and converts old build files to the new format. Resaving the build as the new format will not correct the issue as it has to do with how certain flags are treated on-load. This has been fixed in the dev version, and hopefully we'll be able to provide this update soon-ish.

If you have a .mxd file, those can be opened the same way as the modern .mbd. For datachunks, we have several ways of importing things now due to the multiple variants. The new format is Build Sharing > Import DataChunk The old format should use Build Sharing > Legacy Share > Import from Forum Post Really old ones you might have to save in a text file and try Open that as a build file Game exports are loaded using the regular Open as well Can you provide a link to a build you wanted to look at that you can't get loaded?

As for a Datalink specifically. Once you submit your build, you want to select the Download URL, and then Paste that as a link into your post. That will allow people to download the build directly, but the link only lasts one month, so we generally recommend including a Datachunk as above. Build Link https://api.midsreborn.com/build/download/FydkdmmeWV4l3Hyl

You can pick any theme you want, though the default for the Homecoming forums is a dark theme, so I suggest picking from that selection. You want to choose the BBCode option. When you click Export, it'll place the build data in your clipboard, which you can then Paste (ctrl-V) into a post. It's recommended to wrap your build in a spoiler tag (the eye in the bottom row of the editor) to save space. If you also want to include a Datachunk, you can switch to that tab and click Export, then Paste at the bottom of your build. In the example below, I wrapped it in a second spoiler tag. Melania Dominic - Hero Controller Build plan made with Mids' Reborn v3.7.5 rev. 21

I'd echo the Mind recommendation. It's considered to be better on doms, and PVP-wise, it utilizes more uncommon mezzes that tend to see less resistance. There's plenty of sources of immob/hold, but sleep res is often ignored, as is confuse res, and repel res is almost unheard of. And like @aethereal mentioned about the mechanics of control in PVP, even though knock res is one of the more common ones, you're still likely to get bounces out of it, even if it's barely knocking them on their butt. It's still disruption! Mind/ has a great deck of cards for PVP.

Haha, no, far from terrible, just hard! Running into an equal level one alone is almost always a death sentence. I guess the best way to put it is they have a high cost of entry, and most people don't have the patience for it.

From what I understand, at 50+ levels, a dominator will destroy most stalkers/scappers/blappers in a straight one-on-one fight of raw DPS. In team fights, you're likely going to be playing more to a controller-style, since if you're in close and glowing as doms tend to do, you'll get dogpiled on. But that's also 50+, when doms really come into their own. Before 50, I'd assume you'll be more of an opportunist, like pre-50 stalkers, looking for lone squishies who aren't prepared to be yanked out of the sky by a hold and blapped. Doms are probably the hardest AT to master, and for optimal performance are also incredibly enhancement-reliant, so many still don't make it to 50 or get retired quickly. Once they get there though they're also one of, if not the, strongest in the game. It really depends on you to know your limits, think tactically, and judge situations accordingly, especially in PVP.

Or just /getglobalname "character_name" If the name's associated to someone, it'll tell you.

Figured I'd skim through posts and check in on this. It looks like the suppression for Field Operative is set to "MissionObjectClick". I generally recommend selection of all of these for in-combat values:

From the Discord: This has been fixed in the Dev environment. A release date for the next update is unknown at this time.