SoR2's code (Evil side)

SoR2's code (Evil side) Bingo Card
Preview

This bingo card has a free space and 29 words: Gigantic switch‑case w/ strings, Vehicle is a subclass of Agent ——— OR ——— Agents ARE vehicles, Status effects are still traits, Banana and Voucher workaround is still there, Virtual methods that should have been interfaces, Unrelated code, Binary serialization, Optimization-blocking for-loop over a collection stored in a field, Relationships still use both strings and enums, isAgent, isItem, isFire, isBullet, isObjectReal fields, Enormous if-chain, Dozens of incredibly specific fields, A method with 10+ parameters, Start(), Start2(), Start3(), StartReal(), StartReal2(), sprite, spriteH, spriteWB, spriteWBH, Locked doors are still one-directional, Custom localization problems, X and Y instead of Vector2, Random-Selection is still ridiculous, Expensive string concatenation in a loop, Loop-switch sequence, Improper list population w/ excessive copying, Switch statement on direction string, 24 directions are strings, tk2d, Undisclosed exceptions, realName, realName2, fakeActive, Inefficient vector math and Data clumps.

More like this:

Invisible String Bingo | Invisible String Bingo | Ukulele Bingo | Ukulele Bingo | VIOLIN BINGO 🎻🎻

Play Online

Share this URL with your players:

For more control of your online game, create a clone of this card first.

Learn how to conduct a bingo game.

Call List

Probabilities

With players vying for a you'll have to call about __ items before someone wins. There's a __% chance that a lucky player would win after calling __ items.

Tip: If you want your game to last longer (on average), add more unique words/images to it.