Commit Graph

3063 Commits

Author SHA1 Message Date
0465923992 Fix some images that became ridiculously large due to unnecessary metadata 2025-03-02 01:33:01 -05:00
7cd48a44ee remove -> void where unnecessary 2025-03-02 01:15:53 -05:00
03b9bf5abf Confirm before debug-switching scenario 2025-03-02 01:15:53 -05:00
92f698cc57 Debug actions to quick-launch core scenarios 2025-03-02 01:15:53 -05:00
1d63e76c26 More buttons for debug help window 2025-03-02 01:15:53 -05:00
b4af09c548 Fix debug help menu crash 2025-03-02 01:15:53 -05:00
94b5bcae53 throw catchable error from unsupported charToKey 2025-03-02 01:15:53 -05:00
068e87ea39 Debug enter town: Move outdoor location. Fix #664 2025-03-02 01:15:53 -05:00
a7ba60a6d5 Allow limited debug mode in startup menu 2025-03-02 01:15:53 -05:00
f464526d0d preview_dialog_xml don't try to load empty filename 2025-03-02 01:15:53 -05:00
aa36b6cefb previewing dialogs, don't crash the game 2025-03-02 01:15:53 -05:00
ad43e8ab81 Draw item scrollbar in boom_space. Fix #650 2025-03-02 01:13:53 -05:00
8973618dff Wait action: always print to buffer when can't 2025-03-02 01:13:30 -05:00
91f28d3c9d Fix menubar alchemy clicking 'Ask About' in talk mode 2025-03-02 01:13:30 -05:00
9dfc9e7287 DRY a frequently used buffer string 2025-03-02 01:13:30 -05:00
0afed5db59 A feature flag denotes whether a scenario uses the new or old format for its metadata. With the old format (legacy scenarios and openBoE scenarios created prior to this PR) everything displays in the scenario picker as before, and scenario designers get 2 text fields to display however they want, and 2 text fields that are pretty much useless.
With the new format, Author and Contact info are formatted onto the first line in the scenario picker display. The scenario designer gets 1 line to write a teaser.

Fix #593

Also fix a bug where scenario ratings were appearing as integers ingame instead of the correct "G", "PG", etc.
2025-03-02 01:09:03 -05:00
0f4b1124f6 reorder make-scenario1 2025-03-02 01:03:21 -05:00
06abd20f8f make 'i' show inventory 2025-02-27 08:55:56 -05:00
a862c362fb Switch debug keys for clearing souls 2025-02-27 08:55:56 -05:00
b7b595590d Fix loading trapped monsters 2025-02-27 08:55:56 -05:00
04183c7fbe Fix summoning exported monsters 2025-02-27 08:55:56 -05:00
bbddbefa99 Debug action: clear trapped souls 2025-02-27 08:55:56 -05:00
f2869494bb Buffer message when no souls for simulacrum 2025-02-27 08:55:56 -05:00
36a9c237d7 fix pick buttons in simulacrum menu 2025-02-27 08:55:56 -05:00
126245180a Replay scrollbar changes in dialogs' scrollbars 2025-02-27 08:55:26 -05:00
756415aeb2 record scrollpane name 2025-02-27 08:55:26 -05:00
5d3dd844ba scrollbar store reference to pane 2025-02-27 08:55:26 -05:00
a01c9d6e2a All controls store their name/keyO 2025-02-27 08:55:26 -05:00
f5f157c2ea Make cContainers handle relative elements within 2025-02-27 08:55:26 -05:00
c061ed4b0f Retarget Windows SDK for Visual Studio projects 2025-02-27 00:29:58 -05:00
b200dc2e20 Fix special item Use button 2025-02-23 21:04:32 -05:00
ca8da469e1 Debug give item: try give to active PC. Fix #635 2025-02-23 19:19:42 -05:00
c7ec0e3a85 Debug action: fill active PC's inventory 2025-02-23 19:19:42 -05:00
23adcac665 Debug mode: infinite PC turns 2025-02-23 19:19:42 -05:00
756324ad05 Exclude more invalid indices from damage_target 2025-02-23 19:11:30 -05:00
b505dc5852 Don't double-adjust boom text pos. Fix #127 2025-02-23 19:11:30 -05:00
942442ab26 Refactor: use damage_target() to remove repetitive if-else 2025-02-23 19:11:30 -05:00
3689adcc12 Fix text bar flicker. Fix #602 2025-02-23 19:09:53 -05:00
f92e7abe56 Only redraw textbar when text changes 2025-02-23 19:09:53 -05:00
d4675ed4c7 Refactor text-bar text calculation 2025-02-23 19:09:53 -05:00
11f5ab179d Merge pull request #657 from NQNStudios:replay-fixes
A round of replay system fixes and improvements.
* replaying the debug help window was broken in 2 ways which I fixed
* Fix #559 -- When we observe bugs in random sessions, we no longer have to regret that we didn't pass `--record` at the command line. The replay data is kept in memory and writing it out can be enabled with debug action Z.
* Recording replays into the working directory by default is pretty wonky, because the working directory is usually a build output folder that might be clobbered by a `scons -c`, wiping out important replays. Also, if the working directory is the Visual Studio project folder, you end up adding untracked files to your repo folder which can get annoying. So - I've made the default replay directory a folder alongside the tempDir that already exists. On Windows, this is in AppData, on Mac it's in Application Support, etc. But if you pass an explicitly relative or absolute path, it is resolved as expected.
* I made a mistake a while ago that made the Debug action N (end scenario) not get recorded. Fixed!
2025-02-23 19:09:27 -05:00
6ff155434c don't access uninitialized sf::Event 2025-02-23 15:09:32 -06:00
32e644b9f5 some actions shouldn't be recorded in every context 2025-02-23 15:09:32 -06:00
f601678f33 replay handle_victory must pass force 2025-02-23 14:09:52 -06:00
13532fe09a update unused key list 2025-02-23 09:38:26 -06:00
651348cf7e record debug end scenario 2025-02-23 09:38:25 -06:00
8ba173e5eb Record replays into AppData 2025-02-23 09:38:23 -06:00
60b178d6e8 Debug action to save out (and keep saving) the log in memory 2025-02-23 09:38:23 -06:00
64702b3a88 support for recording replay in memory 2025-02-23 09:38:22 -06:00
5ee8f91f5d fix replay show_debug_help 2025-02-23 09:38:22 -06:00