WCL logs are now accessible via calendar.You can now remove your characters from their teams on your profile page.You can override default realm timezones for events.Auto generated upcoming events now have a default creation time which can also be overridden. To celebrate 9.2.5, giving away annual tier 3 memberships to 5 lucky users 🥳🥳🥳.Guilds of WoW now supports adding members from opposite factions to teams and events. This development also shortened the load times. 90 ratings) with Chrome Lighthouse within all categories. There's been many under the hood UI updates. Sync client now automatically minimizes itself if there's not any issue on startup. Event date duration now also displays 15 minute intervals.This's crucial for biweekly and monthly recurrence but also can be useful for delaying creation of events to a certain date. There's now a start date input for auto created upcoming events.Creating upcoming events on selected timewalk events' active weeks only. You can tell the system to create upcoming events only on certain WoW weekly events.Į.g.

A new recurring event setting now supports WoW in-game events.Recurring events now support biweekly and monthly repeats.RSVP dates are now being displayed on roster table and excel export.There'll be an optional approval stage in the future. With this type of events anyone in your region can set their RSVP. Public events are now a new audience type.Apart from visual updates you can now filter recruits by raid, M+ and PvP achievements. Recruits search list is now more talented.If the first group bought more things than the second group, now you can be confident that clicking the button caused them to buy more things. After some time, check how much each of the two groups bought. Show half of them the bigger, redder button, and change nothing for the other half. This is very simple to set up - put a subset of your users into two equally sized buckets, at random. The only way to know what impact the button has on your users is to perform an experiment. Maybe the fiscal year ended around the same time and all of your users got big tax returns. Sales may go up after the embiggening of the button, but you still can’t attribute that to the changes you made to the button. More people click on it, and sales go up, right? In reality, there’s no reason to believe that this is the case. Maybe you make it even bigger and even redder. Because of this conclusion, you want more people to click on the button. It’s very tempting to conclude that clicking on the button made them more likely to buy something. The analytics tell you that users who click the big red button in the middle of the home page buy something 6% more often than users who don’t. The reality could just as easily be that some of your users have an attribute Z that causes them to do A and B more often.Īs a practical example, let’s imagine that you run an ecommerce site. Saying that doing A causes them to do B is adding more information to the story. The information you actually have is very simple - users who do A are more likely to do B. It seems correct on the surface, but in reality you’re making up information. This is not the correct conclusion, and is very easy to miss. I hear it all the time while working, too - users who perform action A do thing B at a rate that’s higher than the baseline, so action A must increase the probability that people do B. Young people who have moved overseas may have higher salaries, but there’s no reason to believe that the moving caused their salaries to be higher. It claims that moving overseas when you’re young boosts your salary. This bloomberg article is a classic example. Every nerd worth their salt knows this, but falls victim to it all the time. A classic example of this is “correlation does not imply causation”. Christian Scott Christian Scott twitter github email me Big Red ButtonsĪ lot of “good advice” that’s easy to internalise is also easy to ignore.

The big red button wow