UberGuy

The child effect which applies the cold damage has conditional statements attached to it and they're being displayed at least for me when I look at the live site. This seems like the constraints you mention. Is this not visible for you?

Looks like a display bug. The raw data sent to the site has them in the correct order. I'll have to check the code, but my guess based on spot checking them is that the web page code is sorting them by level then name. If so, I can just remove that and the current data will show the right thing.

Can you give me an example of this? I believe powers are ordered in CoD the way they are in the game data. If there are powersets where the first power in the data is not the T1, then that's probably what's up. The in-power info should still say correctly what level it becomes available at, though, and I could probably sort based on that if I'm not already.

Given what's on CoD comes straight from the game files, I'm inclined to agree with @Uun. Both powers are single-target, target self and have self as the only affected entity. While some effect lines say things like "all affected targets", what that actually boils down to is controlled by the Target and Entities Affected lines.

CoD updated with today's Homecoming patch.

CoD doesn't have this sort of capability today. It'd be possible to add, but you should understand that the lists involved would be pretty huge. There are many hundreds of player powers, and some set types have very pervasive application. (Think the various damage type sets and how many powers they would slot in.) It's extremely rare for folks to look at IO sets in this direction. Usually they want to know what sets their powers can take, not what powers can take a set. On the off chance that you actually could work within a small set of powers, like "what powers my character has that could take defense sets", you can see that on each power page's top right side. The icons up there show what enhancement types and set categories a power accepts - the icons with the IO-like hexagonal borders are for set categories. If you hover over the icons, the float text will show you the name of the thing that icon represents, and if you click on a set category icon, it will take you to the list of the sets in that category. I've attached a file containing the current list of player powerset powers that accept IOs in the "Defense Sets" category. Defense_Set_Powers.txt

Hey, gang, CoD has been updated, both live and beta! Very sorry for the late updates here. I have tooling that monitors the manifests looking for patches so I know to get on the update train, but there were two problems with them. I never switched that tooling from checking for updates to the old closed beta server to the new HC beta server. The tooling follows the login flow for the patcher, but as you all know the HC patcher relies on a valid login on these forums. My login had expired and the tool stopped checking anything. I've fixed both issues, plus made it so that if the tool's login is failing I get a notification and can go fix it. By the time I realized I needed to be working on updates, I had a bunch of stuff going on at home that needed to come first., Hopefully the improvements above will keep me on the ball better.

Hey, Tic. I remember you.

From what I can tell by looking at the git history, this never worked right. I guess no one ever noticed because either (a) they didn't move the slider, (b) they were looking at powers where child effects don't scale with level, or (c) they just plain didn't notice numbers that should change did not do so. I think I have to fit in option (c). The bug was incredibly simple. The hierarchy of child effects is literally a parent/child tree structure, where each effect group web display element is a child component of the parent effect group's element. The effect group widget has inputs that control how it displays its contents - things like AT tables, level, etc. Parent elements have to forward relevant inputs to their child elements. The web code has never passed the display level to the child components, so they always displayed at a default level of 50. This has been fixed. 😝

That doesn't seem to be any sort of display error. That's how it's actually set up. Even if those numbers were backwards (every 4.5s for 10s), it would only tick twice. Edit: I got confirmation from @Booper that this is WAI. It's got an interval so the attribute will stick around. The desired duration for that is 4.5s, If you check the flags, it's kept around to prevent a 2nd knock effect for that period. The 10s interval is arbitrary - it just has to be longer than the effect duration to ensure there's only that one tick. Edit2: I'll see about making the display more intelligent when the interval is longer than the duration, since this seems like an implementation trick we'll see in other places.

I just pushed a fix for the "Unknown Stacking Type" situation. I reused an existing icon for now - I need to noodle a bit on what makes sense given how small the icons are. I improved the "Unknown X" logic so it actually tells us the unknown thing's name in the popup. It always had the flag name, but just didn't know what icon or description to display. I also added the "Unknown X" behavior to several other attribmod icons that had a possibility to fall through without picking something to display, which could happen if a new value is added that the logic is not updated to handle.

I just posted a data update that contains fixes for things like "Δ K'ong". The issue was was in original Rust bin parser code, in parts of it that I have never actually touched before. There was logic that stripped out non-ASCII text from display strings of all kinds. I removed this logic entirely, so now everything in the clientmessages-en.bin is parsed as it's stored. There's a chance this will introduce control characters that were not previously present, though I mostly would not expect the website to care about such things. If you see something that looks off, let me know, as always. I also updated Brainstorm's data.

I just made a quick edit to the site meant to save people from being stuck on blank pages if they last had things configured to look at Cryptic/Alpha data. Since that's gone now, the site was busted for those folks, and it busted badly enough that they could not reasonably get to the settings page to fix it. I just pushed code that redirects folks trying to hit Cryptic data to Brainstorm instead. This should also handle folks using direct links to a specific dataset that targeted data=cryptic. The new code lets me add future data redirects like this in case they're needed again. I'll also look for ways to remove this lookup from the critical path for page load. Since there is code referencing the dataset in the header of every page, targeting a bad path breaks every page on the site early, which is, ah, not ideal.

The Live site should be updated for this week's patch. I'll work on the UI bugs mentioned above (and some older ones too) this weekend. References to data from the "Alpha" / Cryptic environment have been removed / updated to refer to "Beta" / Brainstorm.

While I can't say with certainty, I do not believe so. Edit: My understanding was that RedTomax had the info they did because they were close to one of the Paragon Studios powers devs. The original site was based on text info for the powers, rather than squeezing it out of client files. In fact, originally, most of this info did not exist in the client. I was only after "Real Numbers"™ was added to the client UI that powers data started being shipped with the client bins.

Oh, no, now let's be clear. While I do maintain it, I built what CoD's powers data extracs on top of @RubyRed's parser work. It's grown significantly since then, but I likely would never had undertaken it without that codebase. Also, the updates I am able to make when the Homecoming team releases updates is because they help me to know what changed at a data level. CoH's game files are extremely opaque in nature. They are almost literally a memory dump of the C data structures. If you don't have either source code or someone to tell you what has changed about them ... well, I won't say figuring it out would be impossible, but I'll just say there's totally no way I could do it as a side hobby project without the help of others. Even Ruby based their original work on original source code leaks. The one thing I can mostly take credit / blame for is the website presentation. Even there, while the codebase is wholly my own creation, I used the original City of Data as a UI inspiration and I regularly get feedback from folks like @Captain Powerhouse, @Booper and @Number Six (and many folks in this thread) when I display things poorly (or not at all) and/or things need better labels / descriptions.

This one should be easy to track down. I'm glad at least the logic for "tell us when you don't know what to show" works, rather than the old behavior of just not showing anything!

🤔 Yeah, that's not right. It clearly gets that the effect is based on an damage table, but it's not adjusting it. That probably means not just this power is affected. I'll dig into that ASAP.

Since the "Alpha" environment is apparently deprecated, the already out of date info for it on CoD will, most likely, never be updated again. As such, I plan to remove it from the site this weekend. The "Beta" and "Live" links will remain accessible in the header's revision text popup.

This is probably some oddity of browser-side and/or server-side caching. I haven't deployed any site updates since about 20 minutes after I posted about the I27 changes. (I had missed some data fields in powers and redeployed to add them, but they were just new JSON fields on powers - not powersets or their names - and that's the only place they appear.) That was like 18 hours ago, and the cache settings on CoD stuff are supposed to be 10 minutes. And I supposedly invalidated the server side cache as part of the deploy. So... 🤷‍♂️?

I do see the new Epic sets on the AT pages. I don't see the updated names. That seems to be legitimate - the old names are in the data. I am not sure what's up/missing/wrong there. Edit: Actually we can see the right names in those screenshots. I may have been confusing my browser (and myself) using the back and forward buttons across server boundaries, silently switching between views of Homecoming and Alpha.

🤨That is surprising. Those have always had well-defined means of relationship to the ATs that can use them. If these were created with some new way of building that relationship, the code that stitches them together probably doesn't account for it. I'll have to go data diving to figure that out.

Interesting. That sounds like I'm not handling unicode characters somewhere in my data processing chain, which is both surprising and not. Once I figure out where it's happening it probably won't be hard to fix. Finding it might be "fun" though. 😅

So... where has UberGuy been? Life has thrown me quite a few curves over the last 9 months or so. I'm happy to say that most have just been part of getting married and picking up two kids (not counting the two cats). Needless to say, my free time is sometimes consumed by new things - this is not a complaint. The kids are mostly grown and not really living at home any more, but there was a chunk of the last 9 months where they very much were, and that still takes time and attention. And after that we've still been celebrating graduations, helping move them into dorms, and so on. There have also been a couple of crises along the way, but overall the kids have weathered them admirably. My wife, who is a high school teacher, works far from our home, so she stays by the school during the week and is only home on weekends and during breaks. That means that, since last August, I mostly only get her home on weekends. Now, she has her own stuff to do, so it's not like we're hanging out every hour of every weekend, but when she wants to do stuff together, that's my priority right now. We also have been planning / executing some significant updates to the house - the kind that involve contractors. This often involves moving exiting stuff around or just throwing old stuff out. (Not nearly as much as my wife would like, but she accepts that I'm only a little bit of a hoarder. That my dad is one like, for real helps set the bar. 😛) And there have been a number of deaths in my relatively immediate family. Nothing dramatic, per se, just old and / or sick folks passing on, but that doesn't make it easy. And some of my time has been spent being there for other family members, particularly my dad. The good news is that there is a light at the end of the tunnel as far as time to work on CoD (and maybe play CoH again) goes. My wife is leaving teaching after this spring, and will (like me) work out of our home full time. (I work in IT and am a remote corporate employee, but she'll be self-employed.) Both kids will be away at college, and probably not home much except for holidays and whatnot. And while I can't know that folks won't stop passing away, but if they don't, I'll run out of relatives soon. (That sounded darker than I mean it to...) As usual, every time I come back to this to work on a big release I find stuff that makes doing it hard, question why the hell that's the case and try to improve it. So that was part of why getting back in the saddle for this update only took a couple of calendar days. Hopefully that'll mean I am even more productive when I get more "real" bandwidth to do this. I'm wasn't planning to go anywhere and stop working on it so long, but sometimes the plans come for you anyway.

CoD is updated with today's release! Please note that only the "Live" section has been update but the "Alpha" section is out of date. Since Alpha wasn't where most of the late testing for I27 was happening, it was left in a no-man's land where it was ahead of what the old parser code but behind the latest Beta / Live layout. There is a "Beta" data section, accessible by clicking the . Right now it probably looks just like "Live" so it's not very useful. There were quite a few "structural" changes to AT and power data for this release, so there is definitely a chance things have gone wrong. I did some basic spot checking but I was working pretty fast so I probably missed things. 😛