Dekapai

Every vote is a "match". On each match, the winner skins gets some points and the loser skins loses some points. The idea is that after enough matches we should get to a stable ranking where bigger tits float to the top.

Skins with very few matches may have an inaccurate rating, so that might be why. I added a warning to skins with less than 20 matches to make that clear. It could also just be that most people disagree with you.

The only thing I store that is kind of (not really) personal is your IP. On every vote I store the current time, the IP where the vote came from, the two skins in the match, and the skin voted for. I only really store your IP so I can block/remove votes if someone malicious tries to mess up the rankings or something.

There are no cookies.

That's just the default skin of the ship.

Yes, as of December 30th 2025. Unfortunately, this isn't set up to update automatically when new skins/ships come out, so I'll have to update it manually when that happens.

No promises, but as long as I'm not too busy and I'm still interested in the game, I plan to keep this updated.

You can vote as many times as you want, mostly. Still, there is a limit of how much you can vote in a 24-hour period. This is to prevent a single person from influencing the ranks too much. How this limit works will remain undisclosed, but most people should never reach it.

That's not a question. Also, while I respect your opinion, it is, unfortunately, wrong. There's no such thing as tits that are too big, and the bigger the better. I welcome the Azur Lane breast inflation we've been seeing for the last recent years and pray every night for a new shipgirl who breaks the current record. May this game be dominated by titty monsters 🙏

Jokes aside, if you really like flat why are you even playing this game?, the rankings are still useful to you, you just have to scroll all the way to the bottom.

Comes from でかいおっぱい, Japanese slang for "huge tits".

Bremerton is best girl. Also, whoever is at the top of the ranking, it depends on how horny I am.

Hello fellow nerd. This is hosted on AWS and runs on a totally serverless architecture (S3, CloudFront, API Gateway, Lambda, DynamoDB), mostly so because I don't expect it to be used that much and that's exactly where serverless shines.

Front-end is 99% vibecoded because I hate CSS with a passion and uses no frameworks because I can't be bothered to learn any of them; pure HTML/CSS/JS is good enough for this. Back-end was written by hand and autistically optimized to save as many DynamoDB RRCs/WRCs as possible because it's fun and I'm cheap.

How are the pairs chosen?

The first skin:

• 40% of the time: is picked randomly from all skins.
• 60% of the time: is picked randomly from the 500 skins with the least matches (bigger weight to the ones with less matches). Skins with less than 50 matches have an even higher boost and will get picked way more often.

The second skin:

• 15% of the time: is picked randomly from all skins
• 85% of the time: is picked randomly from the same/adjacent buckets as the first skin

The bucket of a skin is just skin["rating"] // 50.

How are rankings calculated?

I'll just copy-paste the relevant code:

ZERO = Decimal("0")
ONE = Decimal("1")
TEN = Decimal("10")
SCALE = Decimal("400")
TWOPLACES = Decimal("0.01")
MINIMUM_K = Decimal("16")
MAXIMUM_K = Decimal("96")

def get_k(skin):
    matches = Decimal(skin["matches"])
    k = MAXIMUM_K / (matches + ONE).sqrt()
    return max(MINIMUM_K, k)

def update_elo(first, second, vote):
    rating_first = Decimal(first["rating"])
    rating_second = Decimal(second["rating"])

    difference = rating_second - rating_first

    expected_first = ONE / (ONE + TEN ** (difference / SCALE))
    score_first = ONE if vote == "first" else ZERO

    expected_second = ONE - expected_first
    score_second = ONE - score_first

    k_first = get_k(first)
    k_second = get_k(second)
    new_first = rating_first + k_first * (score_first - expected_first)
    new_second = rating_second + k_second * (score_second - expected_second)

    # Only store 2 decimals to save space
    new_first = new_first.quantize(TWOPLACES)
    new_second = new_second.quantize(TWOPLACES)