Dec
19

Survivor 37 Test Version Released

Author Brant    Category All, Simulator Updates     Tags

A test version has been released of the Survivor 37: David vs. Goliath simulator. It’s early in the day, and I’ll be monitoring comments here and on social media to address the bugs. There was just limited testing, so some small bugs are to be expected.

This season is based on the Survivor 33 and Survivor 34 simulators. All three of these seasons now include more display customization options based on user feedback. Depending on your preference, they can more closely resemble the original .net seasons. The Events/Status Pages, Relationship Highlights, Status Page Buttons, Reasoning and Targets, and Relationship Highlights are optional and can be turned on and off with many default options set to false.

New features also include:
– The final four format
– New tiebreaker for winners (also added to S33 and S34)

The finale’s format is assumed but can be adjusted if the actual finale differs.

The hidden advantages are the weakest part of this season and need more work. Overall, this is about 30% closer to the final state I’m aiming for the .com Survivor seasons. There may be lingering bugs from existing seasons with the voting algorithm. The plan is to address these bugs, add the final improvements, and enable “Change Settings Each Episode” before adding saving. With the year coming to an end, it’s my goal to make these updates more regularly and move on to other simulators besides Survivor 33-37 in 2019. There are known bugs, mainly with initial immunity and multiple immunity winners by gender, in the .net seasons that will be addressed as well.

Please report any issues. I’ll list the bugs fixed here. Thank you.

Bugs Fixed
– Immunity text implying a group tribal council in episode 4 removed.
– Exiled castaway joins correct tribe if there’s a quit or medevac.
– Game Changers’ automatic rocks tiebreaker added back.

21 Comments to “Survivor 37 Test Version Released”

  • Request WordPress › Error

    There has been a critical error on this website.

    Learn more about troubleshooting WordPress.