devtrackers.gg
Serious question,.. do the mods say cert because of reading the code, or because they all play WoW and not RS primarily?
Code and they were called certs in RSC :)
Serious question,.. do the mods say cert because of reading the code, or because they all play WoW and not RS primarily?
Code and they were called certs in RSC :)
It's definitely human psychology and not the fact you've already messed up the drop rates once prior on this exact piece of content. What was the thing that pointed out your content was broken? Oh yeah, human psychology and a decent sample size.
Yeah we screwed up, missed a zero, and when checking missed the fact that me missed a zero, but woah dude chill.
I'm not saying its not rare just trying to point out that rare occurrences do happen, especially with a large sample size like you say. And most of the time even the brain of a rational mathematician can make weird assumptions about probabilities and statistics.
There are lots of people who have run ED2 and going dry for 750 kills while rare isn't impossibly hard to fathom.
[deleted]
n..no we sell in large quantities, at the mall.....
>_>
TIL 0.0013% isn't rare. Good to know.
just a bit rarer than the lucky dragonkin coin from a lucky charm, but that's happened already. This is the problem with probabilities, they do not blend well with human psychology.
Thanks
So the 750 dry guy has had 2250 rolls at a 1/200 drop rate. Using Binomial Probability that leads to 1/79,080 which while its a rare occurence, it isn't astronomically rare.
EDIT: Where are mini-bosses classified for Lucky Charms Proc Rate (1/25 or 1/50)?
Sidebar, can we get this for Solak too, would be considerably simpler and its been over 4 months
Minibosses have the same proc rate for lucky charms as regular bosses 1/25
[deleted]
I talked to u/shaunyowns about maybe dropping this info on the drop rates page in a more official manner some time soon. I wrote this up right now because I noticed that concern about the codices was coming up often here.
Out of curiosity, when the one codex had a bugged drop rate, what was it? 1/50 group 1/20 solo?
yeah
What's the rationale behind having such low drop rates for the codices?
we felt like the awesome pogchamp drop moments were missing in ED1 because of the fractional nature of the t92 materials and onyx dust, so kept those and added the rare codices on top for the awesome factor.
We worked with the combat council who got some inspiration from players for the abilities to find a an ability mutator per boss that was desirable, but all melee.
Hiya,
Because the rates in ED2 seem to be concerning a lot of players, specifically the ability mutator codices, I’m dumping some of the important drop rate info!
My understanding from what I last saw was that he recorded donations and didn't convert it to pounds, and essentially overstated the donation amount on stream/afterwards before being called out.
I'm not necessarily stating that's exactly what happened, just what I saw last after this whole situation. All I care about now is that Macmillan is getting the full donation amount recorded/announced, and that there'll be mitigation to this type of situation in the future. It wasn't handled well at all, and hoping we don't end up here again for any charity streams.
This is a fairly good point and this was one aspect of the communication breakdown between donations, pledges and currency conversion. As one of the people who met and spoke with both Luke and MacMillan, we are confident that there was no ill intent and that the result was one of lack of experience in how to effectively handle charity issues.
At RuneFest this year we're planning a short Q&A at the end of our main stage lore talk. For technical simplicity we're not going to be taking questions live on stage. Instead we're going to gather some questions in advance and answer as many as we have time for.
If you have a lore question you'd like answered, please post it in this thread.
General upkeep shouldn't be too bad. Most of the hard work is already done, we hope. Of course, there's always the possibility of hiccups, which I guess is what letting people access previews of the sites early allows us to prepare for.
In terms of editing - we have a fair few active editors and we can usually update our content within 24 hours or so of an update. We don't expect that to change, if anything it should improve.
Edit: Regarding your edit, that's just Jagex protecting their trademark because of the word "runescape" in the domain. It's a scenario that neither us or Jagex ever expect to happen, but even if it did, it doesn't prevent us from simply moving our content elsewhere.
Again, riding on the coattails of Jayden's previous statement. Jagex do not want, expect or desire any control over the wiki. We have complete faith that the team heading up the new wiki will be experts in their field and deliver a top class experience for players.
We're working on this project in partnership with Jagex, so you can expect to see links from the official website and other mediums when we're ready to launch.
Just to follow up on what Jayden has stated, you will all see links in the very near future on our websites supporting the new wiki.
We have a contract in writing with Jagex about what they can and can't do. Rest assured, they don't want to hinder the site, and we're not prepared to let them.
Agreeing with the above.
This account is very new but I am the new Director of Community at Jagex and our team have been working with the guys closely the last few weeks on signing contracts and getting all of our ducks in a row. In a nutshell, Jayden and the team will be handling all aspects of the Wiki and we are here to support and help the guys deliver a top tier experience.
Hey!
This should have hopefully been fixed with a hotfix this morning. When you log in again double check if its unlocked and let me know if the issue isn't solved! :)
Hey there! Mod Noodles from Player Support here. So I've had a look into your account and I can see that although you've mainly been active on RuneScape, it looks like a third party was recently logging into your account and botting on Old School, which is why you received the ban. It seems that the hijacker had access to your previous password, which I can see you've since updated, so that's great! Just as an extra heads up, it doesn't look like you you've enabled the authenticator yet, so I'd highly recommend doing so to avoid having your account compromised in the future. I can see that you've submitted a ban appeal for account, which is currently waiting in the queue and will be investigated by a Mod as soon as possible. Hopefully this helps to explain the situation and why the ban was applied. :)
Heey Allstar, been a while.
I dealt with HTTPS in the lazy way - set up an Apache2 reverse proxy for my services with SSL via Letsencrypt. I imagine RuneScape's website with load balancing and such is quiiite a bit more complex. :p
So I can’t really go into our infrastructure in that much detail but we have a better solution in the pipeline - watch this space!
That's not quite true. If you log into the website home page, you can access account settings without having to log back in. If you log into the forums though, you'll be logged into the main website alongside but not be able to access account settings without another login attempt.
This is because you are umping from http to https - something which we are also changing gradually. This week the hiscores module now joined the https list. :)
How do u get it to load on Internet Explorer? On IE11 I only get this:
Please upgrade your browser Unfortunately your browser does not support this feature. Please upgrade to the latest version of Firefox or Google Chrome.
In case any JMod cares: the rendering has been messed up with missing textures etc since Dec 2016 after the NXT update that brought anisotropic filtering and uncompressed textures (same update also caused glitched forum avatars).
it will never work on IE11 due to a lack of support for various web standards and the complicated initialising process of the renderer. Same for Opera, Safari and Edge. The browser must support webworkers with websockets, webgl and localstorage :)
As for the rendering issue you are correct. However that requires engine time of which they are a tad busy with Mobile now :)