The Forever homepage on @Wowhead now shows the most recent data uploads for quests and items from players that are using the looter/client. As soon as a change is found via the client, it will show in this list.

We're going to update a lot of the bot protections on @Wowhead in the near future. This is mainly because of the number of websites/addons that basically just scrape written content/guides from Wowhead and then add "From Wowhead". Some don't even put any reference to Wowhead, but we can literally see that it's taken from Wowhead. I'm hoping to avoid causing disruptions to resources that use Wowhead in a positive way for the community, instead targeting those that are just scraping content to avoid having to write/create guides themselves. If you or your team historically uses Wowhead data (not tooltips), please reach out so we can have a chat. We'll also release some formal guidelines once we've done some more prep work - we won't just shadow drop the full set of protections. We've been watching the data throughout Forever beta and I really don't want to deal with Forever launch when hundreds of websites suddenly need to "update their guides" by scraping whatever the latest versions are, multiple times per day.

It's been around a week now since we introduced the new comments system on Wowhead news. Any feedback, we're happy to hear it - have you used it, do you like it, is there anything you'd want to see improved, etc. We're already working on bringing in reply notifications!

We're making a change on @Wowhead to the commenting system on news. The comments will now function as they do on the database, with the option to upvote/downvote replies, and replies with enough downvotes will be hidden. You will now also see replies to comments nested inside the original comment, rather than it just being lost in the other comments. The final new addition is being able to sort the comments by age, "top comments", or comments that have a Wowhead reply on them (if it's one of THOSE posts). You'll need to be logged in and have an account in "good standing" - that's 125 reputation to upvote, 250 reputation to downvote, same as elsewhere on the website. If you find any bugs or see anything you'd like improved in the new system, let us know.

We're working on stuff - hoping to bring more of this to the retail side of the site. If anything's broken or you have feedback, let us know. More to come! wowhead.com/forever/changes

📣GIVEAWAY Don't have beta access for WoW Forever? Want it? ▶️Reply with your best Main + Secondary Name and Class/Race combination ▶️ Repost & Like this ▶️ Follow me I'll pick 5 winners of a 🔹Skyborne Epic Pack🔹at 23:59 CEST on 21st September. Good luck :)

We are starting to move beta data from Forever into the Wowhead database. Up until now, the database on /forever has been placeholder "base Classic" data. There will likely be things that we need to update, change, cache issues, etc. - but we're getting there!

Wowhead will be datamining Forever and posting about it. We will spoiler tag anything that is massively important or "experience-destroying".

We've made some major improvements to the WoW Forever talent calc. It's probably the best version in terms of data accuracy that we can get before beta. If you find anything weird, let me know. More features on the calculator will come in the future. wowhead.com/forever/talent-c…

One of the comments that popped up on the statement post this week, and a thread from there, was regarding moderation. I had every intention of having the upcoming Darkspear Dash & Running of the Trolls posts not be locked when they are posted and basically give people a chance to act like decent human beings to one another. Both myself and Sas aren't going to be available to actually monitor the threads due to IRL commitments, which poses somewhat of an issue - I don't want to put a volunteer moderator in the position of having to make the decisions necessary to keep the thread open. I fully anticipate it will be extremely volatile and it's a lot to ask of a volunteer. Instead, I will be locking both of these posts before they go live. This might be seen as going back on my word, but I'm not going to put a volunteer or a member of my team in that position, because it's also going to likely have a lot of fallout from users that receive bans/warnings. I made the decision to keep these posts unlocked in the future, but for the first one at the very least, it should be me and Sas dealing with the moderation of it to actually see what happens. Next time. Sorry folks.

The fact that some of you can't even read the post I made because of ads is... yeah. I get it. I don't think that's fair, because if you're willing to actually go and take the time to try and read a post about wanting to fix things for our users, well, you shouldn't bloody be stopped from doing that by one of the issues I talk about. Here are the main parts of the article for those of you that can't access it. On behalf of myself, the team, whoever is part of this - sorry you can't read it. We're going to fix things.