Uses of Package
edu.uky.cs.nil.tt

Packages that use edu.uky.cs.nil.tt
Package
Description
Tandem Tales is a platform that enables short, paired storytelling exercises between two agents over a network.
The IO (input/output) package defines the various message types that can be sent between a server and client and provide some utilities for serializing and deserializing objects as JSON.
Story worlds define the objects, concepts, and actions that exist in a story, and story world models define the logic for when actions can happen, how actions change the current state of world, when endings happen, etc.
  • Class
    Description
    An agent represents an individual connection to a server that can server as one of the roles in a session.
    A client connects to a server to find a partner and play a role in a storytelling session.
    A command is a type of operation that can be parsed by a command parser and executed on a server.
    An operation represents a single command that can be executed on a server based on a series of arguments that define how it behaves.
    A database is a server's persistent store of information about the story worlds and agents available for sessions.
    A database entry represents an individual elements in the database, including its meta-data, such as its title and description.
    A listable entry is one that can either be set as clearly publicly available (listed) or not clearly available (unlisted).
    A log is used to record system messages and session data.
    A named object has a unique name that specifically distinguishes it from other objects of the same type in the same context.
    Represents the two roles in a collaborative storytelling session: the Player, who typically controls a single character, and the Game Master, who controls all other characters and the environment.
    The server listens for new connections from the network, reports which story worlds and agent types it supports, and makes matches between agents so they can collaborate in storytelling sessions.
    A session records the events of a story, any reports of the story's quality, and the final result at the end of a storytelling exercise between a player and game master.
    An event represents a single turn during a storytelling session as well as the actual state of the story world after the turn and the state of the world as perceived by the player.
    A report occurs when one participant in a session sends their response to a question about the narrative.
    A result explains how the session ended.
    A timestamped object records the moment at which it was created.
  • Class
    Description
    An agent represents an individual connection to a server that can server as one of the roles in a session.
    A database entry represents an individual elements in the database, including its meta-data, such as its title and description.
    Represents the two roles in a collaborative storytelling session: the Player, who typically controls a single character, and the Game Master, who controls all other characters and the environment.
  • Class
    Description
    A named object has a unique name that specifically distinguishes it from other objects of the same type in the same context.
    Represents the two roles in a collaborative storytelling session: the Player, who typically controls a single character, and the Game Master, who controls all other characters and the environment.