carl-hamlin / gylf Goto Github PK

The 'think' command needs coding.

1. The command should be available to all users, regardless of privilege.
2. The command should broadcast to the area a supplied message when invoked without a target parameter.
3. The command should roll against skill to broadcast to a specified target, with a chance of overflow on failure.

While a dig is occurring, other participants in the area, having noticed the dig, should be able to help the digging participant with the syntax:

'dig help '

Doing so should shorten the time required to complete the dig.

Participants should be able to follow the Help command with the argument 'egg' to get help with the Egg command.

If Dig succeeds, then the process of creating the new area should take some time based on environmental factors.

The digging participant should not be able to perform most other actions during the time period without first stopping their dig.

If the command is successful, the implantee should be given a notification indicating that they're expecting.

File locking and semaphoring for double login prevention not functioning correctly - users may login multiple times without generating an error condition.

1. The command should be available to anyone, regardless of privilege level.
2. The command should take the initial parameters 'set' and 'clear', indicating what to do with the third argument.
3. Third argument indicates a behaviour category that the AI performs while the player is offline.
4. Fourth argument indicates what to do with that category.

The 'look' command displays garbage data when invoked with default parameters.

Participants should be able to follow the Help command with the argument 'shutdown' for help with the Shutdown command.

The Gylf command will take the supplied coded DNA info and parse it in the DNA Lab against the performing entity's own encoding as the primary source parent.

Participants should be able to follow the Help command with the argument 'dig' to get help with the Dig command.

The 'help' command needs to be coded.

Requirements are as follows:

1. The command should be available to all users, regardless of privilege.
2. The command without argument should attempt to take into account the user's current situation and display help accordingly.
3. The command should take an argument in then form of a specific command and display syntax help for that command.

Currently the participant data in the test directory does not match up with the defined participant data structuring algorithm. This needs a remedy before our admin-level commands will work, for one thing, and really should be done sooner than later.

Barring contraindicators arising from environmental factors, the Dig command should create a new area in the direction specified as an argument by the participant.

The 'logout' command needs coding.

1. The command should be available to everyone, regardless of privilege.
2. The command should safely revert control of the invoking avatar away from the participant to the artificial intelligence.

The Egg command should have, as it's first argument, the name of a participant within whom the egg shall be implanted.

If the named participant is already carrying an egg, the command should detect that condition, and respond to the initiating participant with an error message to that effect; current egg carriers are not eligible to be implanted in this way.

The shutdown command hangs on execution instead of shutting down the server.

Help command should take a look at the performing entity's situation and make a determination as to how to best help when no arguments are present.

Participants should be able to follow the Help command with the argument 'logout' for help with the logout command.

Logout command does not currently revert the impacted entity to AI mode.

The command loop in adress.active.status.asm was terminating incorrectly due to improper stack manipulation.

Participants should be able to follow the help command with the argument 'broadcast' for help with the Broadcast command.

Participants should be able to follow the Help command with the argument 'gylf' for help with the Gylf command.

The Dig command should parse incoming directional arguments and check against the hosting environment to ensure that it makes sense within the parameters thereof for a participant to dig in the specified direction.

If it does not make sense, then the command should provide specific messaging indicating the reason the participant may not dig in that direction.

Currently, we're getting data from the socket, and then manually stripping carriage returns. There is no use case wherein we should receive data from the socket and not strip carriage returns, so why not have the receiving code do it by default?

Participants should be able to follow the Help command with the argument 'look' for help with the Look command.

The DNA Lab isn't working at optimal efficiency.

The README is currently incomplete. Complete the README.

Yet another in the series of WTF moments surrounding the return to production; the 'area' command is flowing into memory that doesn't belong to Gylf.

Logout command should clean and restore connection socket to unused socket repository.

The 'dig' command needs completion.

Requirements:

Command should take a direction as an argument,check to ensure that fulfillment of the command make sense within the parameters of the environment, and if so, execute, creating a new area at the specified direction with a timer on user activity during execution.

Other users in the area where execution is occurring should be able to see the executing user digging a path, and optionally be able to help the digging user with 'dig help '.

There should be no pragmatic delay between the point in time whereupon the data is created and the point in time whereupon the data may be used to activate an open socket.

Commands planned but not as yet implemented cause the client system to hang.

After having been added to the repository, much of the code came through out of standard, with tab stops improperly defined. Current plan is to fix this in tandem with the completion of the README - as each file definition is added to the README, the file itself will be assessed for conformance to standard and prettified.

Currently, the code makes use of symbols that developers have to manually track down to comprehend what's going on. Let's put an alphabetical cross-reference in the code headers indicating symbols used and where they can be found in the codebase.

Logout command does not currently disconnect the invoking user.

The current area filename discovery mechanism is bloated and simple. Let's build a recursive mechanism instead.

The login algorithm is incorrectly identifying returning participants and bouncing them with an error.

The 'gylf' command needs coding.

Requirements are as follows:

1. The command will be available to administrative personnel only.
2. The command will take no arguments, instead, the performing user will be presented with a series of dialogues asking for clarifying information on DNA information to be used in the creation of the target profile, in addition to credential infomation on the target user.
3. The command will assume the performing user is one of the source parents.
4. The command will use the existing DNA Lab structure to create the target profile.
5. The target profile will be available for immediate use.

While a participant is digging, other participants should be able to see that the dig is occurring if they are within the same area as the digging participant.

Right now, we're manually figuring out arguments for commands within the code for the command itself.

Let's not do that. Instead, let's have a function to parse command arguments into a predictable format so we know what argument is where before executing command code.

Participants should be able to follow the Help command with the argument 'area' for help with the Area command.

The Gylf command should be restricted by privilege.

Participants should be able to follow the Help command with the argument 'AI' for help with the AI command.

The Dig command should take a direction as an argument, supported by the argument clustering mechanism.

The Egg command should only be available to users with administrative privileges.

On the client end, when the area command is received without corresponding arguments, it prints an error and does not provide a prompt to the user.

The Gylf command should take a single argument comprised of a string of numeric data representing coded DNA info to be parsed against the performing entity's own profile by the DNA Lab to create the finalized profile data.

The 'egg' command needs to be coded.

Requirements are as follows:

1. The command should be restricted to participants with admin privileges only.
2. The command should take an argument in the form of the known name of a participant, within whom the egg shall be implanted.
3. The command should inform the implantee that they are the carrier of a fertilized egg in such a fashion as is consistent with the nature of the environment; i.e. 'in character'.