Releases: zencq/libNOM.map
Releases · zencq/libNOM.map
0.13.9
0.13.8
Updated mapping for Voyagers.
0.13.7
Updated mapping for Beacon.
0.13.6
Updated mapping for Relics.
0.13.5
Updated mapping for Worlds Part II. There is now a first collision within the mapping for save data, which are now handled by having a main mapping and the duplicates (manually maintained) are only used if they are within a certain section of the JSON.
0.13.4
Nothing new, just a minor mapping update and changed target frameworks according to the .NET release lifecycle.
Changed
- Now also targeting .NET 9 according to supported versions in the .NET release lifecycle
- No longer targeting .NET 6 and .NET 7 (can be still used thanks to .NET Standard)
- Updated mapping to 5.25.0.1
0.13.3
Just an updated mapping including a new legacy one.
Changed
- Updated mapping to 5.21.0.1
0.13.2
Not much but an awaitable async update and a fix.
Changed
- Make
UpdateAsyncawaitable
Fixed
- Unhandled exception when updating but not internet connection
0.13.1
Just a small one which adds dedicated mapping methods.
Added
- New dedicated methods as alternative for
GetMappedKeyOrInputwhich works in both directions
0.13.0
This one adds the possibility to map a single keys and changes the settings behavior.
Added
- New method
GetMappedKeyOrInputto map a single key
Changed
- Existing mapping.json is now loaded when changing the
Settingsand therefore the property has been replaced by a getter and a setter