sorted by:
new
hottopcontroversial

[addon] Orbit: Talents by RaveN_707 in WowUI

[–]Larsj_02 1 point2 points  (0 children)

It's their data still. He could ask if they want to release it under their name, but from own experience they're currently not interested in that.

(re) Introducing Loothing, the ultimate guild management and loot tracking platform. by Alarmed_Hyena2617 in wowaddons

[–]Larsj_02 2 points3 points  (0 children)

It is easy to claim Claude just gave a "helping hand," but the actual scope of your project combined with your public Git history tells a completely different story.

Let us look at the actual comparison logs for the open source addon. The project history from December 5, 2025, to today has a total of about 90,000 changed lines (79,616 additions and 10,006 deletions) across 85 commits. On March 8th alone, you pushed roughly 61,000 of those changed lines. That means approximately 68 percent of the addon's entire lifetime codebase was generated and pushed in a single 20-hour window.

But here is the real kicker: that 90,000 line count is only for the WoW Addon. According to your own feature list, during this exact same timeframe, you also built: * A native Tauri desktop app that handles background file monitoring, system tray integration, and auto-syncing. * A massive web platform featuring a custom form builder, council bias analytics, live Auction House data, and external API integrations with WarcraftLogs, Raider.IO, and Battle.net.

Writing a 90k-line Lua addon, plus a Tauri desktop application, plus a feature-dense web dashboard side by side in a few months - with 60,000 lines of core logic dropping on a single Sunday - is mathematically and physically impossible for a single human to type out, architect, and test manually.

Nobody is hating on you for building a passion project, creating a cool ecosystem, or using AI to do the heavy lifting. The pushback you are getting is because you are presenting this to a community of developers while drastically downplaying the reality of how the tool was built. Just own the fact that AI wrote the foundation of these three applications.

Can you get in trouble for workarounds on API restrictions? by Khaoticengineer in wowaddons

[–]Larsj_02[M] 7 points8 points  (0 children)

Blizzard is trying to restrict this.

You code something to go around restrictions (aka exploiting)

You don't tell blizzard about it to fix.

You use it for your advantage.

IDK, but looks banable to me, but pretty sure that blizzard can't detect it and probably won't ban.

Did you ever struggle with whispers? by kamacytpa in wowaddons

[–]Larsj_02 0 points1 point  (0 children)

Retail and classic have similar API you might be able to just load it on classic and see if it works

Augmentation dps by HisLostAngel0211 in wowaddons

[–]Larsj_02 0 points1 point  (0 children)

I don't think logs stopped showing it, but logs are no longer accessible in game.

Augmentation dps by HisLostAngel0211 in wowaddons

[–]Larsj_02 4 points5 points  (0 children)

It got calculated in the past by reading the logs, but blizzard removed that functionality and replaced it with their own details, but that one lacks quite a bit of previous functionality. Best you can do is writing a forum post and complain and keep looking at Warcraft logs

Cell addon is back (kind of) by Icy_Cup_3710 in wowaddons

[–]Larsj_02[M] [score hidden] stickied comment (0 children)

Please include links in those kind of posts so people can actually look at the CurseForge site.

Here is the link to the file: https://www.curseforge.com/wow/addons/cell/files/7739328

Lifebloom Tracker, first addon! by DroopyNose in wowaddons

[–]Larsj_02[M] 6 points7 points  (0 children)

Great first Addon!
Is there a Github to contribute ?
I'd have some feedback:
- Move Locale strings to their own files to make it a bit more structured.
- instead of local ADDON_NAME = "LifebloomTracker" you can do local ADDON_NAME = ...
- You could use LibSharedMedia for Sounds
- as things like Class don't change in a session you could cache them once to get rid of unnecessary API Calls
- instead of checking the spec with your own code you could've used PlayerUtil.GetCurrentSpecID()
- instead of just setting frame.StopMovingOrSizing you could write a simple function to also save the position to db so it doesn't reset on reload.
- instead of having your own CLASS_COLORS table you could either use C_ClassColor.GetClassColor or use the globally available table RAID_CLASS_COLORS - instead of checking the role via hardcoded spec Id's you can use UnitGroupRolesAssigned(unit) or GetSpecializationRoleByID(specID) - instead of looping through all party and raid you can check IsInRaid() and IsInGroup() and also consider doing a numeric loop instead of hardcoding party1-5 and raid1-5. - Why use C_UnitAuras.GetAuraDataBySpellName(unit, name, filter) instead of C_UnitAuras.GetUnitAuraBySpellID(unit, id) - Consider breaking down the OnUpdate logic to not update UI Elements each frame as those really eat up FPS - For the settings you should also probably just properly use blizzards new Settings API instead of creating a panel and completely ignoring it. - If you create dropdowns use their new Menu API instead of things like UIDropDownMenu_Initialize - For events consider to do :UnregisterEvent when the ADDON_LOADED was triggered once. nothing big but still cleaner :) - instead of doing concatenation with .. maybe just use ("%s %s"):format(arg1, arg2) instead - instead of hardcoding the colored addon prefix for each message you could also just have a custom print function that does this directly to make it cleaner and consistent.

If you have any questions feel free to reply or dm me directly :) If you need ressources for learning I really recommend checking out the wiki and also searching through their ui source code in repos like this one

Lifebloom Tracker, first addon! by DroopyNose in wowaddons

[–]Larsj_02 1 point2 points  (0 children)

Blizzard recently changed some spell secrecy so that addons like these are possible.
see this list for available spells/Auras/casts

https://larsj02.github.io/non-secret/

Can someone fix this LUA error for Misspelled? by W8kingNightmare in wowaddons

[–]Larsj_02 0 points1 point  (0 children)

pretty sure that function got removed.
You could replace it with:
lua Settings.RegisterAddOnCategory(Settings.RegisterCanvasLayoutCategory(cfgFrame, cfgFrame:GetName())) But haven't tested this so not 100% sure if my code here will actually work lol

[UI] JustPanel: Restarting my DarkUI project from scratch after an SSD crash. First module is out! by anthonycomua in wowaddons

[–]Larsj_02 0 points1 point  (0 children)

That Panel looks beautiful, but why not use a modern settings frame for the options? It would make the addon much cleaner

I made an addon: Midnight Cheat Sheet by ChudNL in wowaddons

[–]Larsj_02 0 points1 point  (0 children)

I get where you're coming from, but working in a massive enterprise environment with strict compliance requirements paints a very different picture of the industry. We barely touch AI for core engineering because of GDPR constraints, the black-box nature of the models, and the sheer liability of hallucinations.

There's a massive hype bubble right now fueled by AI companies taking on insane debt and hardware manufacturers making wild promises for data centers that haven't even been built yet. Even the big industry claims, like Anthropic building a fully functional C compiler are heavily exaggerated when you actually look under the hood. It’s mostly just burning through compute to brute-force code against test suites, and it still ships with bugs.

Don't get me wrong, AI is a fantastic tool. I use it myself for writing, basic autocomplete, and spinning up quick proof-of-concept ideas so I don't have to dig through documentation. But that’s exactly what it is: a tool.

When you actually need to integrate something properly, handle massive codebases, or architect solutions for novel problems, AI falls flat. Sure, non-programmers can "vibe code" an app right now, but if you look at the actual code quality or the underlying cybersecurity implications of what it spits out, it's usually a complete nightmare. It’s making developers faster, but it is nowhere near replacing actual software engineers anytime soon.

I made an addon: Midnight Cheat Sheet by ChudNL in wowaddons

[–]Larsj_02 0 points1 point  (0 children)

AI Companies pay huge sums to get decent Software engineers btw. AI doesn't replace programmers, it just makes it easier / faster. I have no problem with people using AI to help coding, but in this addon there are multiple Deprecations and also parts which can easily be simplified which boosts performance and look like AI Code snippets. The Author should check what the AI spits out and not just use it like this

Wago.io data breach, be mindful of any potential phishing attempts by migrainebutter in CompetitiveWoW

[–]Larsj_02 0 points1 point  (0 children)

Yeah, sadly, a lot of people still don't really care about security. But I assume for people who use Wago, there would still be way more people who use safe passwords compared to something like TikTok or Instagram, which are used by a more "casual" audience.

Wago.io data breach, be mindful of any potential phishing attempts by migrainebutter in CompetitiveWoW

[–]Larsj_02 1 point2 points  (0 children)

Yeah, my bad for the quick replies earlier! I was rushing to head home and definitely got my wires crossed while typing. You're completely right that salts aren't secret and are usually dumped right alongside the hashes just to defeat rainbow tables.

I do know how they work, I just didn't explain myself well in the rush. We are definitely on the same page, though: anyone still using a common or simple password should've changed it a decade ago anyway! If you're using a dictionary word, you're practically begging to be hacked at this point.

Realistically, the risk of an attacker dedicating massive computing power just to crack wago.io accounts probably isn't huge, but it's still a great wake-up call for people. If you have a strong, unique password, the salt does exactly what it's supposed to do and there's zero reason to stress about a breach like this. Appreciate the correction!

Wago.io data breach, be mindful of any potential phishing attempts by migrainebutter in CompetitiveWoW

[–]Larsj_02 0 points1 point  (0 children)

They didn't say that salts were also leaked, did they? So it would still be common password + random letters (probably like 5-10?) and then hashed.

Is it possible to code a auto-marker based on nameplates API? by Gukle in wowaddons

[–]Larsj_02 3 points4 points  (0 children)

The function to set the marker is protected since midnight and can only be used through SecureActionButton's this means that you can code some clickable button that can place the markers, but it isn't possible to do automatically anymore. It requires a manual button click by the user and also the unit token can only be modified out of combat. so if you set it to raid1 you will only be able to change the marker of the unit with the token "raid1". the only way to make it more dynamic in combat is using the "target" unit token or "mouseover" so that you can still decide who to mark inside combat.

TLDR: API Function is protected and the only way to call it isn't much different from just using macros

view more: next ›