- You don't need BLP you can just use TGA or even just plain PNG - Bugsack doesn't come with Buggrabber that are 2 Addons which need to be installed separately - What do you want Lua Debugging for ? - Addon Usage is neat to have but not really required if you just wanna keep track of your own AddOn as you can just add a little FontString on the screen to see the numbers while testing. - Instead of opening the File in VS Code you should just open the folder so you have a workspace which is pretty useful when working on multiple AddOns to just switch between them. - You also don't need all these lines in the TOC Interface and title is enough for the start (you could in theory even go without that) as the DefaultState should be enabled by default anyways. - ReloadUI() works but that function is just linked to C_UI.Reload() so might as well just use that. - LoadAddOn() is deprecated and WILL be removed in the war within so your Tutorial won't work then, use the new C_AddOns.LoadAddOn() instead - For Frame Stack (which can be accessed with /fstack which is short enough imo) you can also press ALT to move through the list of frames. - Wowpedia is discontinued use warcraft.wiki.gg/wiki/World_of_Warcraft_API - When showing and testing a function from the API it would be nice if you show that you can just click on the function on the page and most of the time get a detailed info what it does and what you can do with it (which would have told you how the classes are indexed and that a number for index is needed) - wow.tools is also not updated anymore use wago.tools - Last of all i think this tutorial sure did show some stuff but i couldn't really see the learn value as you just copy paste
I have tried a few times to learn how to develop or maintain some WOW addons. I have never succeeded. I was an old school developer before oop. I find it hard to catch on. I believe people will use up to 5 ways to do the same thing. If only they would use just one way, the one that is easiest for a noob to understand and standarize the code, I might able to do it. When I first learned smalltalk I was asking my mentor about the already developed code I was working on. I had a bunch of different things I couldn't understand, and what he told me was. Every one of the developers had their own way of doing things, none of them are really coded in proper object oriented way. I thought well I can't learn a thing from this garbage and any changes are just going to create more garbage. Mayron created some good videos, but blizz keeps changing the "libraries / methods" so those videos are out of date. Wind Fish is the only one I found for version 10. If there is an addon out there and I want to take it over because the author has decided not to maintain it any more, how do I know what is depricated and how to swtch the old to what is new.? This is what I usually want to do. The issue can be extended to ask how would I move something forward from version 8 to version 10 or multiiple rounds of blizz depreications in the past.
@@Phoenix-pm2iw Fixing Something that the Author didn't maintain isn't that hard tbh you just need Bugsack + Buggrabber and then just load the outdated Addon and look for bugs if it says that some function doesn't exist just google it and you'll see how the new function works and also how the old one worked you just gotta try to implement the new function and most of the time it will work. If the Addon is already outdated for a long time then I'd just give up patching it and just try to rebuild something with similar functionality from scratch there are a lot of text based tutorials on the wiki and in the discord you'll always get help if you're stuck with something. Also yes Blizzard changes stuff a lot but most of the time you'll be able to use outdated Functions until the next Addon launches and that's only like once in 2 Years ?
Thank you a lot for the video. Learnt a lot from it.
- You don't need BLP you can just use TGA or even just plain PNG
- Bugsack doesn't come with Buggrabber that are 2 Addons which need to be installed separately
- What do you want Lua Debugging for ?
- Addon Usage is neat to have but not really required if you just wanna keep track of your own AddOn as you can just add a little FontString on the screen to see the numbers while testing.
- Instead of opening the File in VS Code you should just open the folder so you have a workspace which is pretty useful when working on multiple AddOns to just switch between them.
- You also don't need all these lines in the TOC Interface and title is enough for the start (you could in theory even go without that) as the DefaultState should be enabled by default anyways.
- ReloadUI() works but that function is just linked to C_UI.Reload() so might as well just use that.
- LoadAddOn() is deprecated and WILL be removed in the war within so your Tutorial won't work then, use the new C_AddOns.LoadAddOn() instead
- For Frame Stack (which can be accessed with /fstack which is short enough imo) you can also press ALT to move through the list of frames.
- Wowpedia is discontinued use warcraft.wiki.gg/wiki/World_of_Warcraft_API
- When showing and testing a function from the API it would be nice if you show that you can just click on the function on the page and most of the time get a detailed info what it does and what you can do with it (which would have told you how the classes are indexed and that a number for index is needed)
- wow.tools is also not updated anymore use wago.tools
- Last of all i think this tutorial sure did show some stuff but i couldn't really see the learn value as you just copy paste
I have tried a few times to learn how to develop or maintain some WOW addons. I have never succeeded. I was an old school developer before oop. I find it hard to catch on. I believe people will use up to 5 ways to do the same thing. If only they would use just one way, the one that is easiest for a noob to understand and standarize the code, I might able to do it. When I first learned smalltalk I was asking my mentor about the already developed code I was working on. I had a bunch of different things I couldn't understand, and what he told me was. Every one of the developers had their own way of doing things, none of them are really coded in proper object oriented way. I thought well I can't learn a thing from this garbage and any changes are just going to create more garbage.
Mayron created some good videos, but blizz keeps changing the "libraries / methods" so those videos are out of date. Wind Fish is the only one I found for version 10.
If there is an addon out there and I want to take it over because the author has decided not to maintain it any more, how do I know what is depricated and how to swtch the old to what is new.? This is what I usually want to do.
The issue can be extended to ask how would I move something forward from version 8 to version 10 or multiiple rounds of blizz depreications in the past.
@@Phoenix-pm2iw Fixing Something that the Author didn't maintain isn't that hard tbh you just need Bugsack + Buggrabber and then just load the outdated Addon and look for bugs if it says that some function doesn't exist just google it and you'll see how the new function works and also how the old one worked you just gotta try to implement the new function and most of the time it will work. If the Addon is already outdated for a long time then I'd just give up patching it and just try to rebuild something with similar functionality from scratch there are a lot of text based tutorials on the wiki and in the discord you'll always get help if you're stuck with something. Also yes Blizzard changes stuff a lot but most of the time you'll be able to use outdated Functions until the next Addon launches and that's only like once in 2 Years ?