How To Use Chat Triggers Mod

forthebadge
ChatTriggers is always in development. Although we try to follow standard version conventions and deprecate old methods before removing them, at that place may be times where we need to restructure something to the signal where deprecation is impossible. Modules can and will break at whatever fourth dimension.

Most

ChatTriggers is a framework for Minecraft that allows for live scripting and client modification using JavaScript. Nosotros provide libraries, wrappers, objects and more than to make your life as a modder as piece of cake every bit possible. Even without the proper wrapper, yous tin can still apply exposed Minecraft methods and variables simply you will demand knowledge of FML mappings. The entire ChatTriggers engine is built on Rhino using Java 8 and so you have access to any Rhinoceros methods and functions. Rhino supports some ES6 features, every bit can be seen here.

The basic premise of ChatTriggers is that everything is based around Triggers. From a modding standpoint, Triggers tin be thought of as event listeners. These tin can range from a conversation Trigger that runs on a specific chat outcome matching criteria to a render overlay Trigger that runs when the crosshair is being rendered. We are constantly calculation more Triggers and Trigger types equally the mod evolves for more integration with Minecraft.

              register              (              "chat"              ,              part              (              name              ,              message              ,              result              )              {              abolish              (              event              )              ;              ChatLib              .              chat              (              name              +              ": "              +              message              )              ;              }              )              .              setCriteria              (              "<${proper noun}> ${bulletin}"              )              ;              register              (              "renderCrosshair"              ,              function              (              event              )              {              cancel              (              effect              )              ;              Renderer              .              drawRect              (              0x50ffffff              ,              Renderer              .              screen              .              getWidth              (              )              /              2              -              ane              ,              Renderer              .              screen              .              getHeight              (              )              /              2              -              1              ,              2              ,              2              )              ;              }              )              ;

You can learn the basics of scripting with ChatTriggers from the Slate tutorial and once you get the basics, check out the JavaDocs for a more than in depth wait at all of the available methods.

Releases

The ChatTriggers website will always be kept up to engagement with the latest release. Every bit of beta version 0.6.4, we take started to move the release changelog along with a .jar download (mirror of the website) to the GitHub releases page.

Feature changes

Any major features are moved to separate branches before existence merged into master. This volition avoid the issue of waiting afterward a release to set up bugs when we want to exist working on new features. Any contributors will have to abide past the same standard. New features get their own branch and bug fixes crave a pull request on the master branch.

Issues

Whatever issue can be opened using the normal GitHub outcome folio. Issues tin exist anything from bug reports to characteristic requests. For us to consider an consequence to be valid, it needs a uncomplicated simply constructive championship that conveys the problem in a few words and a well thought out and well written clarification.

Issues Report

Should be reproducible
Needs a step by step guide on how to reproduce
Whatsoever evidence of the bug occurring (east.k. images or video) is welcome

Feature Request

Needs a general clarification of the characteristic requests
Specifics on what is being requested (e.chiliad. what class you want it in or what information technology should practise) is highly recommended

Duplicate issues will be merged to avoid too much clutter. If an outcome is moved to "next" we will usually annotate on it to explain how nosotros await to implement or fix that issue.