# \[SOLVED\]Rank in cavern survival

**URL:** <https://discourse.codecombat.com/t/solved-rank-in-cavern-survival/25771>\
**Category:** Bugs\
**Created:** [December 1, 2020, 5:30am UTC](https://discourse.codecombat.com/t/solved-rank-in-cavern-survival/25771 "2020-12-01T05:30:42Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Alexbrand](https://avatars.discourse-cdn.com/v4/letter/a/e9bcb4/32.png) [@Alexbrand](https://discourse.codecombat.com/u/Alexbrand)\
**Post date:** [December 4, 2020, 10:19pm UTC](https://discourse.codecombat.com/t/solved-rank-in-cavern-survival/25771/13 "2020-12-04T22:19:22Z")

</div>

> [@Sharp drop in score when submitting new code?](https://discourse.codecombat.com/t/sharp-drop-in-score-when-submitting-new-code/1629/2):
>
> Your score is made up of a strength value and a confidence value. When you resubmit, your strength value is unchanged, but your confidence is reset (since the ranking system is now very unsure how good your new code is). That’s why you see the ranking blip. It would be nice to not have it, but so far we don’t have workaround ideas for the Bayesian ranking we do: [https://github.com/codecombat/bayesian-battle](https://github.com/codecombat/bayesian-battle)

---

_[View the full topic](https://discourse.codecombat.com/t/solved-rank-in-cavern-survival/25771)._