Repository navigation
Conversation
…NotificationType::animatedObjectSetWalkPath
…rgin ( five percent) not exactly last point
…frag Channel0.png
…ght closed doors) fixed
… around the prison
New TileVisual types for all the rooms, and tileset.cfg modifed to allow proper config of neighbouring tiles, for example for TileVisual::hatcheryRoom the code shall compute the neighbouring index e.g. 1010 and give an appropriate tile
Minor bug not allowing the destruction of rooms also fixed
Missing room meshes added, treasury tiles should now display ok
TileVisuals can now impose setting the position ofa creature diffrent than z=0
…t from visual and index fixed
….e. the tile is unreachable the usual way
Now all ground tiles meshes should use Room.mesh
…k around celler or fight there when they are being dropped there
CMakeList.txt modfied due to paroj fixtures, all tests are now passed
tile info for debugging information -- seat, position, visualTileType, tileType, floodFillValue, floodfill bug introduced at 5409832
…laimed by any seat
Rename to OpenDungeonsPlus in readme
…editor-improvements
…ttons Say what the quit buttons do, and add one that actually exits
The editor offers two rooms of its own, a dungeon temple and a portal, so a wave portal could only ever be edited in a level that already had one. Add a third button for it, next to the portal, drawn with the portal's glyph in red so the two cannot be confused. Claude-Session: https://claude.ai/code/session_01JiKh7f4nenYBTjhJfAGa3y
…ments Editor improvements: creature levels, help window, wave portal editing and more
Clear the client game map before loading a level into it
Embed per-monitor DPI awareness and maintain the verified OGRE 13.6.5 renderer patch required for context-safe window replacement, runtime GL options and correct fullscreen client geometry. Validation: clean Release build, DPI and 3440x1440 fullscreen probes, three GL3Plus variants and the patch reverse check passed; version 0.7.1 remains unchanged because this is unreleased work and the project has no changelog.
Apply display, input, audio, gameplay, minimap, shadow and negotiated nickname changes to the running session while preserving rollback for failed window or input transitions and keeping the 3440x1440 navigation visible. Validation: clean Release and Debug builds, packet tests, DPI, layout and GL3Plus probes passed; the user confirmed the reported resolution, fullscreen, cursor, flicker and navigation failures are fixed. Version 0.7.1 remains unchanged because this is unreleased work and the project has no changelog.
The spells tab put its ten buttons in a single row of 60 pixel squares running out to x=700. The pane they live in is the window width minus the 200 pixels of minimap, so at the 800 wide minimum window it is 600 pixels across, and the last two spells, Weakness and the Eye of Evil, hung past its right edge where they could be neither seen nor clicked. Only a window at least 900 wide showed the whole row, and nothing said so. The rooms tab solved the same problem long ago: two rows of 40 pixel buttons. The spells tab now uses the same shape, five spells to a row, ending at x=300 with room to spare at any size the game accepts. The cooldown bar inside each button now covers exactly its button too, instead of overhanging 20 pixels on both sides, which with narrower buttons would have bled half way across the neighbours. The rooms tab had the tail of the same bug: the temple and portal buttons the editor uses sat at x=570 to 690, past the same edge. They join the end of the second row instead. (cherry picked from commit 10db1cb)
This was referenced Sep 24, 2026
Replace the auto declarations introduced by this branch with explicit types, as requested in issue tomluchowski#42 and required by CLAUDE.md. No behavioural change.
Rokk001
force-pushed
the
pr/room-navigation-cycling
branch
from
September 27, 2026 17:19
e72ab90 to
a5883f3
Compare
This was referenced Sep 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Right-clicking a room action now moves the camera to an owned room of that type. Repeated right-clicks cycle through multiple matching rooms in stable map order, including bridge rooms.
This contribution depends on #83 for camera flight and input blocking. It does not modify that pull request. The focused four-file change can be reviewed at Rokk001/OpenDungeonsPlus@feature/map-navigation...pr/room-navigation-cycling. Related to #11, but it does not fully resolve the broader camera-navigation issue.
Validation: