deus-ex-randomizer icon indicating copy to clipboard operation
deus-ex-randomizer copied to clipboard

Outside of WaltonWare, some bingo goals can be impossible on non-M01 starts because their max is too high

Open MQDuck opened this issue 1 year ago • 5 comments

For instance, "KnowYourEnemy" on an M03 or M04 start. The requirement will be 6, but only 4 or 2 can still be read.

MQDuck avatar Oct 03 '24 07:10 MQDuck

It's possible GetBingoMax() could eventually be combined with BingoGoalImpossible().

MQDuck avatar Oct 03 '24 10:10 MQDuck

Bingo goal scaling works on non-WaltonWare modes as well (this is a mission 3 start). Is there some scenario where you didn't see this? NG+ loops after a non-M01 start that could be later in the mission? image

theastropath avatar Oct 03 '24 12:10 theastropath

You're on Liberty Island still. If you start later, there are only 2 "Know Your Enemy" bulletins that can be read, or 0 until PR #966 is merged.

MQDuck avatar Oct 03 '24 13:10 MQDuck

Right - your initial description implied the scaling didn't work at all ("The requirement will be 6"). This issue is for later start points within a mission then, rather than just "non-M01 starts".

theastropath avatar Oct 03 '24 13:10 theastropath

your initial description implied the scaling didn't work at all ("The requirement will be 6").

You're right. I actually considered changing the wording on that line after I tested the goal more thoroughly but decided it was clear enough. I should have seen otherwise in retrospect.

This issue is for later start points within a mission then, rather than just "non-M01 starts".

No, the issue is not just for later start points within a mission. It's for any start point past M01. For instance, with an M02 Battery Park start there's no way you can read 6 "Know Your Enemy" bulletins.

MQDuck avatar Oct 03 '24 14:10 MQDuck