Open x123 opened 1 month ago
The trick here is that 1.3.0-353-g7a242f456 is from an experimental branch named id with new changes to ID which is going to form the bases of version 1.4. I have pushed it as a branch and had it build so that other people can test it - which you seem to have done accidentally 😁 - thank you, this is helpful feedback for the new branch. For your purposes though, the latest on the main branch is 1.3.0-350-ga51756908. I don't think there's an obvious way to tell the branches apart from the release title - you need to actually go and compare the commit against the main and id branches.
I've submitted a PR in nixpkgs to correct the automatic update tooling to only hit the latest commit on main
, rather than the latest commit on any branch.
Thanks for the detailed feedback and all the hard work on narsil. I have been enjoying it immensely, despite never having beaten a run.
Thank you! I wasn't even sure anyone was playing it, please feel free to submit any other bugs/requests.
This looks likely to be because known objects aren't handled correctly (or at all?) in smithing
Should be fixed in 491a3ed5f
Working through the tutorial (compiled on macOS with 'make -f Makefile.osx OPT="-O0 -g -DUSE_STATS -fsanitize=address -fsanitize=undefined"), creating the base item at the forge for the requested boots of speed works, but there is NULL pointer access when trying to add the speed enchantment. The top of the call stack at the point of the crash is:
At line 124 of ui-smith.c, i is 0 and obj->known is NULL.
When reviewing the nixpkgs PR https://github.com/NixOS/nixpkgs/pull/349999 to update from 1.3.0-234-g228c4f0cb -> 1.3.0-353-g7a242f456 I noticed during playtesting that the use of a forge would reliably crash/panic narsil. Not sure of a way to reliably bisect without having to play through at each step to get to a forge.
Steps to reproduce:
The game immediatly crashes with:
System info: