Skip to content

0.22.0

Compare
Choose a tag to compare
@DaveyBiggers DaveyBiggers released this 02 Jun 17:34
· 688 commits to master since this release

Changes:

The bulk of the work for this release has been centered around adding logging code to both the Mod and platform, which should significantly help us to track down and fix any future issues with Malmo's socket code, etc.

You can switch the Mod logging on by going to the Mod options (in the Minecraft GUI) - be warned, if you turn the detail up too high this will produce a LOT of logging...
The logs are stored in the logs subdir of the Minecraft folder, and are named after the date/time when that Minecraft instance was run.

On the platform side, switch it on by doing something like this:

MalmoPython.setLogging("where_I_want_it.log", MalmoPython.LoggingSeverityLevel.LOG_ALL)

Again, this will generate a lot of noise unless you opt for something like LOG_WARNINGS, etc.

The two log formats are the same - they start with a timestamp formatted the same way, followed by an "M" for Mod or a "P" for platform, so in theory the two files could be merged and sorted together, which should make forensic debugging a bit easier.

Users can append a line to the platform log by calling, eg, MalmoPython.appendToLog(MalmoPython.LoggingSeverityLevel.LOG_INFO, "Here's some important info...")

This is just intended to make debugging easier - it's not intended as a general purpose log for the user's code. It can be used to add signposts to the log - eg "INFO: started episode #242" which should make searching for problems easier.

Other new features:

  • New: ObservationFromRay now returns distance.
  • New: ObservationFromFullStats now returns DamageDealt
  • New: startMission now provides more error details in exceptions; multi-agent samples hardened by using this.
  • New: ObservationFromNearbyEntities now returns entity life.
  • New: RewardForDamagingEntity plus sample. (#537)
    Assorted bug fixes

Breaking changes:

Hopefully nothing...