@casual-simulation/stacktrace - npm Package Versions

V2.0.0

Date: 6/7/2021

:bug: Improvements

• Added the mapPortal.
  • The map portal provides a 3D representation of the entire Earth and allows placing bots anywhere on it.
  • Bots that are in the map portal use Longitude and Latitude for their X and Y coordinates.
  • The map can additionally be customized by setting the mapPortalBasemap tag on the mapPortalBot. See the documentation for more information.
  • Based upon ArcGIS.

:bug: Bug Fixes

• Fixed an issue where trying to focus on a position in the miniPortal would not work.

V1.5.0

Date: 3/17/2021

:boom: Breaking Changes

• Changed the #portalCameraRotationX and #portalCameraRotationY tags to use radians instead of degrees.

:rocket: Improvements

• Added the cameraZoom and cameraZoomOffset tags.
• Added the os.focusOn(botOrPosition, options?) function.
  • Works similarly to os.tweenTo() and os.moveTo() except that it takes an options object instead of a bunch of parameters.
  • Notable improvements includes that it can accept a position instead of a bot, it supports different easing types, and it will return a promise which completes when the camera movement is finished.
  • Additionally the rotation values are in radians instead of degrees.
• os.focusOn() and os.tweenTo() now use quadratic easing by default.
  • Additionally os.focusOn() supports specifying the easing type just like animateTag().
• os.tweenTo() and os.moveTo() are now deprecated and should no longer be used. They will be removed in a future release of CasualOS.
  • To encourage migration, they have been removed from the documentation and autocomplete.
• Added the experiment.beginAudioRecording() and experiment.endAudioRecording() functions to experiment with audio recording.
  • See the documentation for more information.

:bug: Bug Fixes

• Fixed an issue where camera offsets would not be taken into account when calculating the camera focus point.
  • This fixes issues with the focus point becoming more and more wrong as offsets are applied to the camera.
  • However, any calculations which try to calculate a camera position offset from the focus point must now subtract the current offset from the focus point to get the correct result. The example auxCode (cameraMovementExample) has been updated to reflect this change (version 2 and later).

V1.0.24

Date: 4/14/2020

Changes:

• :rocket: Improvements

  • Added a button on the sheet code editor to show errors that the script has run into.
    • It is very basic at the moment. There are no line/column numbers, no timestamps, and no way to clear the errors.
    • Errors are automatically pulled from error space and queried based on the following tags:
      • auxError must be true
      • auxErrorBot must be the ID of the bot whose script is in the editor.
      • auxErrorTag must be the name of the tag that is being edited.
    • The following tags are displayed for each error:
      • auxErrorName is the name of the error that occurred.
      • auxErrorMessage is the message that the error contained.

• :bug: Bug Fixes

  • Fixed the color encoding of sprites to use sRGB instead of linear.
  • Fixed an issue where atoms would be sorted improperly because their causes were improperly treated as different.

V1.0.22

Date: 4/11/2020

Changes:

• :boom: Breaking Changes

  • The player.inSheet() function has been changed to return whether the player bot has a dimension in their auxSheetPortal.
    • Previously, it was used to determine if the player was inside auxBuilder (which no longer exists).
  • Removed assignment formulas.
    • Assignment formulas were a special kind of formula where the tag value would be replaced with the result of the formula.
    • They were removed due to lack of use in addition to other means of achieving the same result being available.
  • Semantics of @onUniverseAction have changed.
    • Previously, @onUniverseAction was run before any particular action was executed but the actions that were dispatched from @onUniverseAction were run after the evaluated actions. This led to a scenario in which a @onUniverseAction call could overwrite values that were updated by an action that had not been checked yet.
    • Now, all actions dispatched by @onUniverseAction are executed before the action that is being evaluated. This makes the behavior of the data produced by @onUniverseAction mirror the runtime behavior of @onUniverseAction.

• :rocket: Features

  • Added a new runtime for scripts and formulas.
    • This new runtime is much faster than the previous system and lets us provide features that were not possible before.
    • Should work exactly the same as the previous system. (There might be a couple of tricky-to-reproduce bugs)
    • Now supports setTimeout() and setInterval().
      • This lets you write your own custom game loop if you want.
      • Note that the script energy will only be restored if a user action triggers a shout.
    • Paves the way for future functionality (not guarenteed):
      • Change notifications (@onBotChanged, @onBotTagChanged(), etc.)
      • Asynchronous functions instead of responseShout. (e.g. const response = await webhook.post("https://example.com", data))
  • Added the error space.
    • The error space contains bots that represent errors that have occurred scripts in a universe.
    • Unlike other spaces, the error space does not load all of its bots into the universe automatically.
    • Instead, they have to be requested via a search query. These queries filter bots by tag/value pairs.
    • Currently, error space is only used for storing errors and there is no way to load bots from the space.
    • In the future, we will add the ability to load errors via scripts as well as display them in the sheet.
  • Changed the renderer to output colors in the sRGB color space instead of linear.

• :bug: Bug Fixes

  • Fixed an issue where a shout argument might be recognized as a bot even though it isn't.
  • Fixed an issue where a shout argument with a custom prototype would be overridden.
  • Fixed a bug in three.js's LegacyGLTFLoader where it was using an old API.