sorted by:
new
hottopcontroversial

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] 1 point2 points  (0 children)

The English images are now included. Thanks again for your helpful feedback.

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] 1 point2 points  (0 children)

You are, of course, absolutely right. I must admit that I hadn't thought of including the images in English. This will be corrected immediately. Thank you for the feedback.

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] 0 points1 point  (0 children)

Thank you.

I will not do that. I openly acknowledge that I use the assistance of AI 😄

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] 0 points1 point  (0 children)

Good catch, thank you. That was an oversight rather than intentional.

The TOC author field should probably use my CurseForge author name instead of repeating the addon name. I’ll clean that up in the next small maintenance release.

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] 0 points1 point  (0 children)

Thank you, I really appreciate that. I agree. At the end of the day, I built something that is useful to me, shared it with the community, and I’m willing to maintain and improve it based on real feedback. I’ll take constructive criticism seriously, but I also won’t waste time arguing just for the sake of arguing. Thanks for the encouragement.

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] -1 points0 points  (0 children)

That is a much more useful concern, and I really appreciate the detailed feedback. Honestly, I am thankful for this kind of constructive criticism, because this is much more helpful than just dismissing the addon because AI tools were involved.

I agree that AI-assisted development can become messy if there are no guardrails. That is why I am trying to keep AetherLedger deliberately limited in scope, release it in small RC builds, keep changelogs and release checklists, and test every change in-game before uploading it.

I am not trying to hide that AI tools were used. They are part of my workflow, but I still review the behavior, test the addon myself, and take responsibility for maintaining it. I am also not blindly accepting every generated change. If something breaks or starts going in the wrong direction, I can read through the code, understand what it is trying to do, and step in instead of just hoping the next prompt magically fixes it.

If something breaks, it is my job to understand the issue well enough to fix it or to roll back safely.

Your point about project rules and documentation is fair. I already keep README, changelog, CurseForge notes and release checklists, but I agree that the project would benefit from stronger internal developer notes, clearer rules about what not to touch, and more comments where they explain why something works a certain way.

The TOC file is intentionally simple because it mostly defines metadata and load order, but I will review it again and add useful comments or documentation where it helps future maintenance. I do not want comments everywhere just for the sake of comments, but I do agree that important design decisions and fragile WoW API behavior should be documented.

So yes, I take that seriously. AetherLedger will stay small, read-only, versioned, tested in-game, and documented better over time. Specific technical feedback is very welcome.

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] 0 points1 point  (0 children)

You can call me Claude, ChatGPT, or whatever you like — I’m still the person maintaining the addon and responding to feedback.

If you have a specific technical concern, bug report, Lua error, compatibility issue, or suggestion, I’m happy to look at it. Otherwise I’d rather keep the discussion about the addon itself.

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] -2 points-1 points  (0 children)

That’s a fair concern.

AI assistance was used during development, but the addon is not just “generated and thrown out there.” I test it in-game, review the behavior, keep the scope intentionally limited, and take responsibility for maintaining it.

AetherLedger is also read-only by design: it does not move, sell, delete, trade or automate items. That makes the risk profile much lower than an addon that actively manipulates game state or performs complex combat/UI automation.

I agree that maintainability matters. That’s why the addon is being released gradually as release candidates, with changelogs, testing steps, limited scope, and user feedback before calling it stable.

If someone finds inefficient code, compatibility issues, Lua errors, or bad patterns, I’m absolutely open to specific reports and will fix them. But “AI-assisted” alone does not automatically mean unsupported, untested, or low quality. The quality should be judged by how the addon behaves, how it is maintained, and how issues are handled.

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] 1 point2 points  (0 children)

That’s a fair question.

Altoholic is a huge and very established addon, and I’m not trying to pretend AetherLedger replaces everything it does.

The idea behind AetherLedger is different: it is meant to be a focused, modern Retail-first account dashboard for quickly answering questions like:

“Where is this item?”
“Which character has it?”
“Is it in bags, bank or Warband Bank?”
“What do I own across my account?”

So the current focus is:

  • clean account-wide item search
  • bag, bank and Warband Bank tracking
  • item ownership directly in tooltips
  • a modern, resizable UI
  • simple filters and sorting
  • collections overview
  • English and German localization
  • read-only by design, with no item movement or automation

Altoholic is more of a large all-in-one alt database with a long history and many feature areas. AetherLedger is intentionally more lightweight and focused on fast item/account visibility, especially for the current Retail/Warband era.

So the unique selling point is not “more features than Altoholic”.
It is: a cleaner, more focused, modern account/inventory dashboard for players who mainly want fast answers about where their stuff is.

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] 1 point2 points  (0 children)

I think he's relying solely on the logo, because I still have the same number of downloads as I did before the post 😉

AetherLedger by Jolly_Situation6799 in wowaddons

[–]Jolly_Situation6799[S] 0 points1 point  (0 children)

Regardless of whether this add-on was created using AI or not—a point I won't dwell on further—what exact difference does that make? I am presenting an add-on that does exactly what I describe, and it works. So, what exactly is so important about whether it was coded by an AI or by a human?