Inventory/Menu navigation (empty inventory)

Open
#360 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c, wasm
Domain
game-dev

Research direction

Two separate UI bugs are reported: inventory tab switching with A/D empties the inventory, and the mouse stops working on the Options > Quit Game menu. The attached savagewind.log is the first place to look for errors around these actions. Reproducing needs the game dump and a Windows build, which a newcomer may not have. Done would mean each menu path keeps its contents and mouse input after the fix.

Written by the indexing model from the issue text.

Description

bug
Before you start
Savage Wind version

0.4.1-alpha.4 (latest)

Game version

1.9.0

Your PC

Windows 11, RTX 4070 Super (driver 621.01), Ryzen 7 7800X3D

Where in the game

in the Inventory/menu

What happened, and how to make it happen again

Bug Report – Version 0.4.1-alpha.4

I completely reinstalled the latest version (0.4.1-alpha.4).

I encountered the following issues:

1. Inventory tabs

When I open the inventory, select a tab, and then press A or D to switch between tabs, the inventory appears empty.

2. Quit game menu

When I navigate to Options > Quit Game, the mouse stops working. I can only interact with the menu using keyboard inputs.

https://medal.tv/games/screen-capture/clips/nQjHcbpabwkXv9rVR?invite=cr-MSxnc3QsMjYzMjI5MDY2

Settings

1440p, unlocked fps, rest is default

savagewind.log

savagewind.log

Before sending
  • This report contains no game files, keys, firmware, generated game code, save files or links to copies of the game.
Dominant language
C
Stars
811
Forks
37
Avg merge
17m
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Revivedx/SavageWindRecomp

All issues in Revivedx/SavageWindRecomp

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.