Breakpoint hits don't actually pause execution, so it's necessary to immediately update the disassember view as the core will continue executing after. This isn't great design but whatever
user will be changing those options from hawk side dialog so it's impossible to miss what you're changing (you can look at the dialog again if you're THAT sloppy)
but since we're now initializing with default nonsync settings and changing them on the fly, those UI messages would be appearing all the time
automap messages are left intact since they appear upon in-game button press
worst case scenario, UI messages are moved to hawk side, but then why limit them to only whatever upstream reports and not report every change? which is never done anyway, so I doubt it'd come to this
if we set them on core init that's how it'd remember them in the reference state, so loading states made with different init options would fail to load
instead we set everything to default on init and then change to what the user set during the first frame advance. that way reference state remains the same so states using different options keep working across all variants
need to not show core messages tho when something is changed from default, because now they appear on init and state load rather than only on explicit change
slaughter maps have gigantic savestates so they're not very tasable until we move from wbx to native. so no point in claiming complete support for them right away. okuplok launches, but might crash maybe
passing rngseed didn't fix sync, and passing all the settings is too much work for this release. will support it afterwards.
instead just tell the user BOOM demos are not supported
- probably resolves#4325
built from 1.24.3 tag without router dll (so OpenAL32.dll is effectively soft_oal.dll). As far as I understand this has no implications other than disallowing other openal implementations
YoshiRulz