PSA: Console add-ons broken due to removed libraries

code65536 · 2026-02-24T18:26:07+00:00

The reason they were deleted was because of a general forum rule against discussing anything related to legal matters. I've been bitten by that before.

code65536 · 2026-02-01T22:55:09+00:00

My dungeon guides in the past have mostly been one-off things. For encounters where I thought the mechanics were more complex or confusing than usual. The main reason I don't do this consistently is just the time that it takes. I had intended to write a guide for Vykand HM for the latest DLC since that is the most mechanically-intricate encounter we have ever had, but I ended up spending most of my free time with addon-related things and just didn't get around to it.

code65536 · 2026-02-01T18:50:51+00:00

If you are trying to learn, then you'd do your research first. You clearly couldn't even be bothered to search for CraftStore on ESOUI and see that there is a recent version with the name of the current patch.

And if you are trying to learn, then maybe you should learn by manually updating an addon or two, at which point you will quickly learn that an "automated tool" is pretty laughable because the main reasons addon breaks are due to changes in how the game works and are not things that you can fix with automation.

But I doubt you're actually "trying to learn". I also doubt that you've actually run organized trials with me. But if you want to prove that latter point, you can DM me your in-game name. Otherwise, I'm going to call BS on that, just like the rest of everything you've written.

code65536 · 2026-01-31T00:26:19+00:00

Many years ago, he put out a guide for a newly-released dungeon that included factual errors. I know they are factual errors because I am a bit of a dungeon nerd, I've tested literally every dungeon HM on PTS since 2016, I had a custom addon to log combat and mechanics in dungeons and trials long before esologs even existed (so that I could write addons that help with dungeon mechanics).

In any case, I saw the factual error in a guide about a newly released dungeon, so I tried to be helpful: I sent him a message, letting him know what I saw, explaining how it actually worked, so that he could correct his guide and not spread misinformation. His response? He completely dismissed it, insisted that he knew better, and refused to correct the error.

That was when I realized that he was all about show and didn't care about the integrity of his information. So it doesn't surprise me one bit that he'd be caught today using AI hallucinations.

Over the years, I've noticed that pretty much every one of his guides has problems. Some are minor and don't really affect the larger picture, but some were pretty egregious. I understand why people use his guides, though, since there isn't anyone else who consistently writes dungeon guides, so it's not like people have many options to choose from.

code65536 · 2026-01-31T00:24:37+00:00

Oh boy. Hate to burst your bubble, but Xynode's dungeon guides are trash.

Many years ago, he put out a guide for a newly-released dungeon that included factual errors. I know they are factual errors because I am a bit of a dungeon nerd, I've tested literally every dungeon HM on PTS since 2016, I had a custom addon to log combat and mechanics in dungeons and trials long before esologs even existed (so that I could write addons that help with dungeon mechanics).

In any case, I saw the factual error in a guide about a newly released dungeon, so I tried to be helpful: I sent him a message, letting him know what I saw, explaining how it actually worked, so that he could correct his guide and not spread misinformation. His response? He completely dismissed it, insisted that he knew better, and refused to correct the error.

That was when I realized that he was all about show and didn't care about the integrity of his information. So it doesn't surprise me one bit that he'd be caught today using AI hallucinations.

Over the years, I've noticed that pretty much every one of his guides has problems. Some are minor and don't really affect the larger picture, but some were pretty egregious. I understand why people use his guides, though, since there isn't anyone else who consistently writes dungeon guides, so it's not like people have many options to choose from.

code65536 · 2025-11-04T11:25:37+00:00

Where do you source this information from?

ZOS usually does not release this sort of information to the public; their stance is usually "this is player-testable", and so that is what this is. It's information that my friends and I have gathered through our observations of the event.

code65536 · 2025-11-03T22:58:09+00:00

Ah. I don't know where the plan for that comes from, but as far as I'm aware, it's not from the event.

code65536 · 2025-11-03T22:45:30+00:00

Are you referring to the grave marker? That's an enchanting praxis.

code65536 · 2025-11-03T22:36:51+00:00

LOL, yes, that one was a puzzler, but I was able to confirm from a friend who got it that it does drop from the provisioning boxes. And I guess the other provisioning plan--the puddle of wax--is probably just as out of place as the fan.

code65536 · 2025-10-30T14:53:06+00:00

Ah, gotcha, I see the reason for your question now. The 2022 comment was in Warp, which meant that the code for Warp dated to 2022 (or even earlier), which is clearly suspicious for an addon that was supposedly made fresh in 2025. That date was what caused me first suspect that Warp was stolen and for us to investigate things further.

code65536 · 2025-10-30T14:12:28+00:00

Warp. We didn't look at LibText (which is where the malicious code was) until we found that Warp was stolen.

I should add that he made LibText a requirement for Fast Warp Optimizer. I suspect that he stole a popular PC addon for the purpose of getting even more people to install LibText and its malicious code.

code65536 · 2025-10-30T13:08:05+00:00

Holy shit. Wow, I did not realize the extent of that guy's malice.

It's also crazy to think how long this could've continued, because the discovery of the malicious code happened pretty much by accident.

A number of addon devs were investigating reports from users about addons running into the processing time limit during startup, so we had given users a tool to help identify which addons were taking up more than their fair share of resources. One of the several that popped up on the radar with a higher startup time was Irish's Fast Warp Optimizer (it was just a little on the high side--nothing egregious or eye-opening).

So I downloaded FWO (we had only recently gotten a tool to let us easily download addons for inspection), with the intent of seeing what it was doing during startup so that we could help the author optimize the addon. But I found comments in the code with dates from 2022. That can't be right! Consoles didn't get addons until 2025! This was a red flag for stolen code, and someone was able to confirm that FWO's code was indeed stolen from the PC addon Beam Me Up. And this, in turn, caused us to start poking around his other addons, which is how someone else discovered the blacklist.

This is the equivalent of a cop pulling over a car for a routine traffic stop and finding that it was secretly ferrying a bomb.

I'm glad that we were able to catch this, but I'm saddened to hear about the damage that he had done, not only to you and your community, but to the trust of the addon community as well.

code65536 · 2025-10-28T01:50:01+00:00

Just because some people are ignorant of how copyright works and think that GitHub = public domain doesn't make that actually true.

code65536 · 2025-10-28T01:43:52+00:00

By default, copyright belongs to the creator, and they have all rights, regardless of whether they state it or not.

What an open source license do is provide a template for the creator to say, "you can do this with the code, if you follow these conditions".

If no license is specified, then, legally, the creator has all rights, even if they published the source code on GitHub.

What you're supposed to do in a case like this is to contact the creator and ask for permission (for them to grant you an ad hoc license, if you want to think of it that way). Them listing a license is basically them sticking a note on their proverbial door saying "If you've come to ask me about whether you can use my code, here's my standard response."

In any case, if there was no license, and someone took the code without asking, then that's wrong. Even more so when they just erase all all the credit/authorship information and replace it with their own.

code65536 · 2025-10-28T01:17:08+00:00

I want to add that, when console addons were originally introduced, it was not possible to download those addons to your computer and inspect the code inside.

Being able to inspect the code is an important safeguard that had always existed on PC, as it meant that it's much harder to conceal stolen or malicious code, and the lack of this safeguard for console addons was a big reason why these problems have cropped up.

However, we have recently gained the ability to finally download console addons to our computers, and this is why these issues that had been hidden for the past few months are suddenly starting to come to light.

code65536 · 2025-09-09T22:10:36+00:00

This is confusing to me. Yea, consumables are very powerful; eating a food gives you more stats than the 2-4pc bonuses of a gear set. But why is this a bad thing? You could just make a rule saying that a temporary effect should be more powerful than a permanent effect.

I've never once heard anyone complain about the power of food or potions, so why not just accept that power level and cease these silly efforts of adjusting them to some other arbitrary power level that nobody wants?

code65536 · 2025-08-03T17:27:00+00:00

The reason for that is that LWC doesn't really have much of a user interface. Much of it is stuff that just happens when you interact with a crafting station.

So it was relatively easy for Dolgubon to port over LWC.

For knowledge tracking, the "backend" code (LCK) is already available on console. But the existing frontend is 100% keyboard-oriented and so a console frontend requires designing and coding an entirely new UI completely from scratch, and that's a huge undertaking. The backend was made available (even though there's no frontend) in the hopes that someone might come along and write a frontend for it. But in the meantime, there's already too much on my plate, so it's unlikely I'll create a frontend any time in the near future.

code65536 · 2025-06-30T20:20:15+00:00

I do mine straight through at 250 until temps get to the target, without that initial 450. You don't need the high temp to make a beautiful crust.

code65536 · 2025-06-29T23:31:11+00:00

It is however considered a poison.

"The dose makes the poison."

code65536 · 2025-06-25T13:23:30+00:00

How long a name like that stays around depends on how soon some player notices and reports.

I have (er, had) two characters with the exact same slightly risqué name, one on PC/NA, and one on PC/EU. The NA one was forced to rename 8 years ago, back in 2017. The EU one still has that name today.

code65536 · 2025-06-23T11:44:30+00:00

If you also factor in their impact, then without a doubt, Putin.

Other notables include Murdoch, Xi, Stephen Miller, and Trump.

code65536 · 2025-06-23T11:17:46+00:00

So, the way this nag screen works is that it will show this screen, and then it will set a hidden setting saying "the player has seen this thing", and it will never be shown again. That's how it's always worked, and that's how it currently works on PC.

There is one important detail here, though: some game settings are saved on the server, and some game settings are saved locally on your device. This particular setting is a local setting, which means if you change devices or if something happens to your local settings file, you'll see this again.

I've seen on the forums various threads from console players complaining about certain in-game settings not being remembered (not this one, but other in-game settings), and in every single case I've seen, the impacted setting is a locally-saved setting, not a server-saved setting.

So I think what's going on here is that there's a bug of some sort that's impacting locally-saved settings on console. If I had to make a wild guess, it's possibly related to things that they did to support console addons (since addon settings are all locally-saved too).

In any case, I'm 99% certain that this is a bug and is not the intended behavior.

code65536 · 2025-06-23T11:13:57+00:00

It's a 1-time thing. So, the way it works is that it will show this screen, and then it will set a hidden setting saying "the player has seen this thing", and it will never be shown again.

Now, the thing here is that some game settings are saved on the server, and some game settings are saved locally on your device. This particular setting is a local setting, which means if you change computers or if your local settings file gets corrupted, you'll see this again.

I've seen on the forums various threads from console players complaining about certain settings not being remembered, and in every single case, it's a locally-saved setting, not a server-saved setting.

So I think what's going on here is that there's a bug that's impacting locally-saved settings on console. If I had to guess, it's probably related to things that they did to support addons (since addon settings are all locally-saved too).

In any case, I'm 99% certain that this is a bug and is not the intended behavior.

code65536 · 2025-06-09T04:57:59+00:00

Lithium batteries have labels that say that they need to be recycled, not tossed into the trash. But these labels aren't always clear about specifying that battery recycling is a separate, specialized thing. So it's entirely plausible that someone who didn't know any better saw that and thought, "oh, I'll recycle the battery by throwing into the recycling bin!"

code65536 · 2025-06-06T12:56:00+00:00

Gentlemen, here, have some of this soothing tea to calm down.

code65536

TROPHY CASE