Skip to main content
 Warning: Unmaintained Version
Version: 0.6.1

Create Entries

Creating extensions for the TypeWriter plugin involves working with various entry types, each serving a specific purpose in crafting immersive player experiences. This documentation explains the roles and functionalities of these entry types, providing clear guidance for developers on how to effectively use them.

Base Entry Interfaces​

There are four base interfaces that all entries extend one of. These are:

  1. StaticEntry: Represents static pages. These are used for content that does not change dynamically or trigger any actions. Examples include static text or images.
  2. TriggerEntry: Designed for entries that initiate other actions or events. These entries can trigger one or more additional entries, making them crucial for interactive sequences.
  3. CinematicEntry: Used for cinematic experiences. These entries are ideal for creating immersive story-driven sequences that engage players in a more visually dynamic way.
  4. ManifestEntry: Used for creating manifest pages, which are used to display statful content to the player.

1. StaticEntry​

  • AssetEntry: Handles external assets, like images or files.
  • ArtifactEntry: Manages plugin-generated assets, such as JSON files.
  • EntityEntry: Serves as a base for static entities in the game.
    • SpeakerEntry: Extends EntityEntry for entities capable of speaking, with defined display names and sounds.
  • FactEntry: Represents static facts or data points.
  • SoundIdEntry: Holds identifiers for specific sounds.
  • SoundSourceEntry: Deals with the sources of sound emissions.

2. TriggerEntry​

  • EventEntry: A base for entries that are event-driven.
    • CustomCommandEntry: Extends EventEntry to allow for the creation of custom in-game commands.

2a. TriggerableEntry (an extension of TriggerEntry)​

These are entries that can be triggered by other entries. They are the most common type of entry, and are used for creating interactive sequences.

  • DialogueEntry: Specialized for dialogues with specific speakers, enhancing NPC interactions.
  • ActionEntry: Executes actions based on player interactions, capable of modifying facts or triggering events.
    • CustomTriggeringActionEntry: A variant of ActionEntry, allowing for custom trigger mechanisms and manual triggering of actions.

3. CinematicEntry​

  • Primarily used for crafting cinematic experiences in-game, this base interface doesn't have listed specialized interfaces, but it's pivotal for creating story-driven, visually dynamic sequences.

4. ManifestEntry​

The biggest ManifestEntry is the AudienceEntry. It is used to define audiences that can be used to show stateful content to players. Almost all other ManifestEntry are sub-types of AudienceEntry. Though this is not required. An example of an entry that is not a sub-type of AudienceEntry is the EntityDefinitionEntry.

The following are the sub-types of AudienceEntry:

  • AudienceFilterEntry: A variant of AudienceEntry that filters the audience passed to the children of the entry.
  • QuestEntry: Specifies quest types.
  • ObjectiveEntry: Base for objectives in quests.
  • LinesEntry: Displays lines of text in things like sidebars or tablist.

A whole nother category of ManifestEntry is meant for Entities. This has it's seperate page in the documentation.

Implementation and Usage​

Each interface is designed with specific tags and methods to facilitate unique interactions within the TypeWriter plugin. Implementing these interfaces allows developers to craft a wide range of player experiences, from simple static displays to complex, multi-step interactive quests and dialogues.

For instance, a TriggerableEntry can be used to set up a quest that only activates under certain conditions, while a DialogueEntry can bring an NPC to life with personalized dialogues. Similarly, an ActionEntry can be used to create dynamic effects that change based on player actions, and a CinematicEntry can be used to create a visually dynamic story sequence.

Defining a Entry​

Typewriter takes care of the heavy lifting when it comes to creating and using entries. Developers only need to define the entry's class and its fields (and sometimes additional methods). The rest is handled by Typewriter. From scanning the extensions jar file for all the different entry classes to triggering them.

To define an entry, it needs to meet the following requirements:

  1. It must be a class that implements one of the base entry interfaces.
  2. It must have a no-args constructor.
  3. It must have a @Entry annotation with all the required fields.

The @Entry annotation is used to define the entry's type, name, and other properties. It has the following fields:

  • name: The name of the entry. This is used to identify the entry.
  • description: A short description of the entry.
  • color: The color of the entry in the editor. It can be one from the Colors class or a hex color code string.
  • icon: The icon of the entry in the editor. All available icons can be found on Iconify. It needs to be the name of the icon.

To find out specific requirements for each entry type, check the documentation for the entry's interface.

 caution

Enties are not allowed to have any state. This means that there can't be any fields that are not final. If you need to have state, use a AudienceEntry.

In summary, these entry interfaces form the backbone of the TypeWriter plugin's functionality, offering a robust framework for creating immersive and interactive content within Minecraft. By understanding and utilizing these interfaces, developers can greatly enhance the player experience, making it more engaging and dynamic.