I've been looking a lot but haven't been able to find an addon that can hide the big text that pops up in the middle of your screen when you enter a new zone (example: "Ratchet, The Barrens, Horde Territory"). I would love to see such and addon, or simply one that could atleast change the font, scale, colour etc. of the text.
Maybe it's impossible, maybe it's so easy I should do it myself, but hey! Asking for stuff like this is what this section is about, isn't it? :)
The text strings are on ZoneTextString and SubZoneTextString.
The frames that contain the strings are ZoneTextFrame and SubZoneTextFrame.
The events that trigger the showing of the text strings are ZONE_CHANGED, ZONE_CHANGED_INDOORS, and ZONE_CHANGED_NEW_AREA. These events are registered to ZoneTextFrame.
More details are in the files FrameXML\ZoneText.lua and FrameXML\ZoneText.xml
Sooo... I make an addon and just put that text in, or do I type it in chat in-game or edit some textfile or something? I'm a newbie when it comes to stuff like this, could you please explain a bit?
Thanks for your fast answer btw, I love you :)
Sooo... I make an addon and just put that text in, or do I type it in chat in-game or edit some textfile or something? I'm a newbie when it comes to stuff like this, could you please explain a bit?
Thanks for your fast answer btw, I love you :)
Here, I did it for you. I call it nOzoneSpam
unzip it into your addons folder.
btw, feel free to look and see just how the text became an addon.. needed a folder, and the a .toc file with the same name as the folder, and the lua file contains the actual code, and is referenced from the toc file so wow knows where to find it.
btw, feel free to look and see just how the text became an addon.. needed a folder, and the a .toc file with the same name as the folder, and the lua file contains the actual code, and is referenced from the toc file so wow knows where to find it.
Yeah, I have some clue about how you make addons, but I didn't really know if I wanted that code in an addon or in some textfile in the WoW folder, now I know! Thanks a lot for the help everyone and special thanks to you break19, not only me but also one of my friends will love your addon (we're tired about the zonetext that keeps spamming when you're ganking at the border Duskwood/Deadwind Pass hehe).
And if you don't plan on updating the addon yourself, keeping it up to date is as easy as changing the numbers in the toc-file, right?
Again, thanks a lot :)
And if you don't plan on updating the addon yourself, keeping it up to date is as easy as changing the numbers in the toc-file, right?
Wrong. Changing the .toc number is not recommended, and not necessary. Just check the "Enable out-of-date addons" box in the addons screen. Not only is changing the .toc number not necessary at all, but it also makes it much harder to figure out what's causing a problem after a patch if you have no idea which addons were actually updated and which ones weren't. It also makes it harder if the addon ever needs an actual update... if you know which patch (.toc number) the addon was last updated for, you can easily tell what's changed in the API since then that you need to accommodate in the addon; if you've changed the number, you have no idea what's changed since the addon was written. The only time a .toc number change is ever necessary is after a major version like WoW 2.0, when major sections of the API have been changed, but in cases like that it's likely the addon will need actual updates as well.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Maybe it's impossible, maybe it's so easy I should do it myself, but hey! Asking for stuff like this is what this section is about, isn't it? :)
The frames that contain the strings are ZoneTextFrame and SubZoneTextFrame.
The events that trigger the showing of the text strings are ZONE_CHANGED, ZONE_CHANGED_INDOORS, and ZONE_CHANGED_NEW_AREA. These events are registered to ZoneTextFrame.
More details are in the files FrameXML\ZoneText.lua and FrameXML\ZoneText.xml
ZoneTextFrame:UnregisterAllEvents() ZoneTextFrame:SetScript("OnShow", function() this:Hide() end) ZoneTextFrame:Hide() SubZoneTextFrame:UnregisterAllEvents() SubZoneTextFrame:SetScript("OnShow", function() this:Hide() end) SubZoneTextFrame:Hide()Sooo... I make an addon and just put that text in, or do I type it in chat in-game or edit some textfile or something? I'm a newbie when it comes to stuff like this, could you please explain a bit?
Thanks for your fast answer btw, I love you :)
Here, I did it for you. I call it nOzoneSpam
unzip it into your addons folder.
btw, feel free to look and see just how the text became an addon.. needed a folder, and the a .toc file with the same name as the folder, and the lua file contains the actual code, and is referenced from the toc file so wow knows where to find it.
Yeah, I have some clue about how you make addons, but I didn't really know if I wanted that code in an addon or in some textfile in the WoW folder, now I know! Thanks a lot for the help everyone and special thanks to you break19, not only me but also one of my friends will love your addon (we're tired about the zonetext that keeps spamming when you're ganking at the border Duskwood/Deadwind Pass hehe).
And if you don't plan on updating the addon yourself, keeping it up to date is as easy as changing the numbers in the toc-file, right?
Again, thanks a lot :)
Wrong. Changing the .toc number is not recommended, and not necessary. Just check the "Enable out-of-date addons" box in the addons screen. Not only is changing the .toc number not necessary at all, but it also makes it much harder to figure out what's causing a problem after a patch if you have no idea which addons were actually updated and which ones weren't. It also makes it harder if the addon ever needs an actual update... if you know which patch (.toc number) the addon was last updated for, you can easily tell what's changed in the API since then that you need to accommodate in the addon; if you've changed the number, you have no idea what's changed since the addon was written. The only time a .toc number change is ever necessary is after a major version like WoW 2.0, when major sections of the API have been changed, but in cases like that it's likely the addon will need actual updates as well.