Skip to content
Tags give the ability to mark specific points in history as being important
  • 1.12-1.0.0
    be0f797f · Bump version number ·
    Version 1.12-1.0.0
    
    Changes:
    * A new system call, `freeRAM`, has been added to the `computer` module.
      This returns the amount of free memory, in bytes, accounting for the
      size of the module code, the size of the linear memory, and the
      current runtime stack and local variable usage. Thanks to DCNick3 for
      this addition.
    
    Fixes:
    * Free memory used to be accounted incorrectly when performing a linear
      memory resize. This would potentially allow a module to declare a
      linear memory with a small initial size but a large maximum size, then
      grow the linear memory up to the size of RAM installed in the computer
      at runtime, while still leaving space free for the runtime stack and
      local variables. Growing linear memory now correctly subtracts from
      the amount available for the stack and locals. Thanks to DCNick3 for
      this fix.
    * Calling the `methodsNext` syscall no longer crashes if
      `methodsStartComponent` or `methodsStartValue` was previously called
      on a component or opaque value that has no methods. Thanks to Buzzec
      for this fix.
    
  • 1.12-0.5.0
    741f0148 · Update README ·
    Version 1.12-0.5.0
    
    Changes:
    * When submitting CBOR to a syscall, binary-encoded UUIDs stored as byte
      strings can now be tagged with tag 37 (UUID), which is more correct
      than tag 39 (Identifier). Tag 39 is still supported for backwards
      compatibility, but tag 37 is preferred.
    * When submitting CBOR to a syscall, Unicode strings and byte strings
      can now be stored out-of-line and referenced via a small descriptor
      tagged with the tag 32,769 (External Reference).
    * A configuration option is added which causes a stack trace to be
      written to the Minecraft debug log when a syscall fails.
    
    Fixes:
    * Unallocated and reserved CBOR simple values (i.e. major 7 values 0
      through 19, 28 through 30, and 32 through 255) now cause a CBOR decode
      error rather than being interpreted as `null`.
    
  • 1.12-0.4.0
    9ea56ae5 · Bump version number ·
    Version 1.12-0.4.0
    
    Changes:
    * The `computer` module contains a new syscall `debug`, which, when
      enabled in the mod configuration, writes a message to the Minecraft
      debug log.
    
    Fixes:
    * CBOR numbers larger than 32 bits are now supported, being decoded to
      Java `Long` objects.
    
  • 1.12-0.3.0
    0330c0be · Bump version number ·
    Version 1.12-0.3.0
    
    Changes:
    * The `component` module contains two new syscalls,
      `lastExceptionMessage` and `lastExceptionIsType`, which allow getting
      more details in the event that a component method call ends with
      `BAD_PARAMETERS` or `OTHER` error codes.
    
    Fixes:
    * Some missing information in `mcmod.info` is now filled in properly.
    
  • 1.12-0.2.0
    bd448467 · Bump version number ·
    Version 1.12-0.2.0
    
    Changes:
    * The pullSignal system call in the computer module now encodes the
      signal as a CBOR sequence of two elements, the first being a string
      holding the signal name and the second being an array holding the
      parameters. It used to encode signals as a single array containing the
      name followed by the parameters. This makes decoding signals easier,
      as an application can decode the string, dispatch on signal name, and
      then decode the array to a typed structure as a single whole CBOR
      item.
    
    Fixes:
    * Modules that declare a maximum linear memory size no longer get 65536×
      too little memory.
    * Modules that declare a maximum linear memory size greater than the
      amount of RAM installed in the computer now display a more useful
      error message.
    
  • 1.12-0.0.1.0
    876bc6de · Add README ·
    Version 1.12-0.0.1.0