Releases: GW2ToolBelt/GW2ML
Releases · GW2ToolBelt/GW2ML
2.0.1
Overview
This is a maintenance release only and does not contain any behavioral change.
2.0.0
Overview
With 2.0.0
comes a major maintenance release that removes previously
deprecated functionality and - most importantly - migrates to the gw2tb.com
domain to bring GW2ML in line with upcoming libraries.
Breaking Changes
- Switched from the "gw2toolbelt.github.com" URL to "gw2tb.com". (This affects
all package names, module names and imports.) - Removed the mislabeled
UIState#isInLoadingScreen
.
1.5.0
1.4.0
Improvements
- Added support for specifying file handle explicitly when opening a view via
MumbleLink#open(String)
.- This is meant to be used with the
-mumble <name>
command line argument that was added to Guild Wars 2 on 28. April 2020 to better support multiple game clients on a single PC.
- This is meant to be used with the
- Added
UIState#isInCombat
bit check. - Added
MumbleLink.Context#getProcessID
which returns the ID of the game process that has most recently updated the data.
1.3.0
Improvements
- Added support for MumbleLink views of custom source ByteBuffers.
- Added
MumbleLink#copy
operations to cover from the entire MumbleLink buffer (instead of just the context). - Added ByteBuffer overloads for
MumbleLink.Context#copy
operations.
Fixes
- Fixes an issue that caused
MumbleLink.Context#copy
operations to copy from
the start of the buffer instead of the start from the context.
1.2.0
1.1.0
1.0.0
Improvements
- Throw descriptive exceptions for errors in native code. [GH-10]
- Documented all remaining undocumented fields. [GH-2] [GH-3] [GH-4] [GH-5] [GH-6] [GH-7] [GH-8]
- Added
UIState#isInLoadingScreen
to check whether the game is currently in a loading screen.
Breaking Changes
- Changed return type of
MumbleLink.Context#getShardID
fromlong
toint
0.1.0
Overview
This is the first pre-release of GW2ML, a library for accessing data provided by
the Guild Wars 2 game client via the MumbleLink mechanism.
This is a initial version is published for easy public consumption and the API
might change in the future (although that is unlikely).