Site Tools


character_randomization

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
character_randomization [2022/03/25 19:18] – Updated for 4.5: Cnofree, Cnoearned, Crestrict wylemcharacter_randomization [2025/05/31 22:25] (current) – Added note about Cnodupes behavior with paired character checks wylem
Line 44: Line 44:
 If playing ''Cvanilla'' (ie. without randomized characters), using ''Cstart:'' will simply replace Cecil. If playing ''Cvanilla'' (ie. without randomized characters), using ''Cstart:'' will simply replace Cecil.
  
 +==== Partner ====
 +
 +By default, the starting character's partner is not subject to any additional logic or weighting. If ''Cnodupes'' is enabled, the randomizer will attempt to choose a character other than the starting character. (Similarly, with ''Cnodupes'' the two Mysidia characters will generally be different, as will the two Zot characters).
 +
 +With ''Cnodupes'' enabled, the partner will not be a duplicate of the starting character.((Unless other flags force that to be the case, e.g., ''Cstart:porom'' with ''Conly:porom''. In this case, you will be unable to take the duplicate character.))
 +
 +With ''Chero'' enabled, the starting character is removed from the character pool before other characters are placed((Unless the hero is the only character in the pool, or finding the hero character is an objective. In these cases, duplicates of the hero can only be taken if the ''Cnodupes'' flag is not enabled. See: [[character_settings#hero_challenge|Hero Challenge]].)), so the partner cannot be the same character.
 ===== Placement ===== ===== Placement =====
  
character_randomization.1648235880.txt.gz · Last modified: 2022/03/25 19:18 by wylem