[New Users] Please note that all new users need to be approved before posting. This process can take up to 24 hours. Thank you for your patience.
Check out the v.256 - The Dark Ride: Limbo Patch Notes
here!
Closed Star force chance suspicion
Is the rate of succession and failure shown on enhancing star force true? I seriously think they actually might have altered the chance of % shown there. I blew up 5 tyrant capes and 2 Tyrant boots within days going from 6-7 and 7-8 stars when it's only 1.5-3% chance of booming. Comparing to using CSS and star force is enough proof to show the difference of the actual percentage of succeeding that low of a chance. I would really want to see proof directly from Nexon that they haven't rigged the percentage shown and the "real" percentage. It's hard enough to find Tyrants around MYBCKN and disappointing to find repeated booms with chances lower than a CSS.
I am now finished with my pent up anger.
Comments
It's 100% fake. They even admitted that star catching doesn't actually raise the chance of success. It's just there to keep you take things slower.
And they will never show you a proof that star enhancement system isn't rigged, because there's not such thing. It is completely rigged. Crap ton of people have destroyed their equips with 0.7% chance of destruction on the first try. That's actually statistically impossible to happen, but it did.
There was an 8th anniversary event scroll scandal where Nexon was actually caught red handed that they rigged the percentage system. The scroll had 20% success rate and 100% chance to destroy upon faiilure. A lot of rankers spend money on protection scroll to use it, but failed in so many ways that suspicion about rigged chance came up. Then a guy ripped open Nexon client server and showed a section where the success chance drops by 2% every time enhancement succeeds (20%->18%->16% and so on). When the community went super outrage about this and demanded answer, Nexon just kept their mouth shut and said absolutely nothing about it for years until the issue cooled down.