In-game DoD Studio window: revisit the whole window's UI (tabs, Settings tab, layout) in one PR for 0.2.1 #899

For 0.2.1, two changes to the in-game DoD Studio window (goldsrc-hooks/src/studio_panel.rs, goldsrc-hooks/ui/*.res):

1. Remove the Studio tab

It's a leftover from when the window first got real tabs (Playback, Demos, Studio, b2be492) and holds only a "Hook status (console)" button (ds_debug_status) and the build-mode hint. Move the Hook status button to the Console tab, drop studio from the tab names ds_ui_panel <tab> accepts, and update docs/dodstudio_commands.md, Commands.txt and the README. A Studio.res a user edited in build mode stays on disk; it's simply no longer loaded.

2. Put every user-facing ds_* setting on the Settings tab

Today the tab has 16 boxes. These are missing:

• on/off: ds_spec_deathcam, ds_hud_hide_voice_menus, ds_hud_hide_map_text, ds_hud_hide_clan_text, ds_hud_show_scope, ds_view_use_cl_bob, ds_view_hide_headshot_red_screen, ds_view_hide_screen_shake, ds_map_allow_shaders, ds_demo_other_drives, ds_demo_seek_skip_between (check against the tab), and any others the tab lacks (compare with Commands.txt);
• not plain on/off: ds_demo_fast_load (0 / 1 / ms), ds_hud_overview_players (0-4), ds_hud_overview_team_marker (0-1, 0-2 after Hide the spectator mode label, Press DUCK, centre text and two overview icons (part of #677) #714), ds_hd_style (a name), ds_demo_ex_interp_max (ms). These need dropdowns or fields.

Leave out what Studio sets itself (ds_spec_lock, ds_capture_*, ds_player_overrides) and ds_debug_*. Group the boxes by area (spectating, HUD, view, players/map/sound, demo, windows), with plain labels (the house style: say what happens). Probe the layout on PRE and POST at 1280x720 and 2560x1440; the tab must still fit, or scroll.

How the tab's values are kept (for the docs and tooltips)

A click saves that one setting to dod_addon\dodstudio_ui\settings.cfg (dod\dodstudio_ui\ without -addons), never config.cfg. The file is applied once when the game starts. Studio's Initial Commands, and any .cfg they exec, run at every demo load after that, so they win for the session, and they never rewrite settings.cfg. A box shows the live value, so clicking one after a .cfg changed it saves the new value. Say this briefly in the tab's help line or the docs.

🤖 Generated with Claude Code