#debvlog

Part of the magic of Uru was being able to actually talk to the characters in the game (if you were lucky enough to be around at the right time, of course). Unfortunately, using that as the primary mechanism of keeping players involved in the story just can’t scale to the size of a player base that would also make the game financially viable. That said, it’s a key component that made Uru very different and very special, and I want to find ways of keeping it around, while also recognizing its limitations.

Additionally, I want to give players more of a relationship with the various characters in the game, so that they have a better understanding of them and their roles in the cavern. Because the DRC and company were only ever “live” NPCs, the only way to get to know them at all was by being lucky enough to meet them in person. Otherwise, you were relying on word of mouth (or worse) to even know who they were. I know having deeply personal relationships with them is unrealistic and impractical, but there should at least be guaranteed opportunities for every player to meet them all and interact on some level.

To that end, the various main characters in the game (the DRC, Watson, etc.) should be able to exist as both traditional NPCs and Uru’s “live” NPCs – Actor-Controlled Characters, or ACCs, if you will. As ACCs, they would operate much the same way they did in Uru, occasionally wandering through various areas of the game, conversing with bystanders, and carrying out day-to-day business (the “palace intrigue”, if you will) with other ACCs to nudge along the finer points of the game’s current narrative. (As a side note, there will need to be some way to cover and report on this stuff in game for those who are interested but can’t be online 24/7.)

As ordinary NPCs, these characters would also exist to give and/or receive quests – for lack of a better word. Players may be tasked with bringing Kodama equipment to help shore up a chamber in the Aquarium, for instance, or be dispatched by Dr. Watson to talk with another NPC “explorer” who has information about the bahro. These tasks may be assigned directly by other NPCs, or come in the form of a KI message. Some quests may even only be possible if the player has a certain reputation with the character(s) in question. Anger Kodama, for instance, and you won’t get asked to help him anymore (or maybe you’ll get asked to help him by somebody who also dislikes Kodama and wants to annoy him). Or, if you blow off too many of Watson’s messages asking you to help vet information, he stops asking. Be diligent in completing marker mission tasks, however, and Laxman may take a shine to you and recruit you for more regular Lattice maintenance operations.

The challenge to this approach is marrying the ACC and the NPC so that they feel like a cohesive experience. First, ACCs should have access to the underlying metrics about their relationship with each person they interact with. This helps inform their tone and attitude. Players who have angered a character should expect to have their questions ignored at town halls, for instance. Similarly, ACCs should be able to feed the outcomes of live interactions back into the NPC’s metrics, so that if they substantially alter their standing as the result of an in-person interaction, the computer-driven NPC can take that into account going forward.

Second, characters should only ever exist in one location in the game at any given time. An ACC should never appear in Negilahn at the same time as their NPC counterpart is waiting patiently for you to arrive at a drop-off point in the City. When an actor logs on to control a character, the NPC counterparts should always link away (unless that would cause them to link out while actively speaking with a player, in which case we can let the mask slip a little, so to speak).

On a related note, as NPCs the main characters should generally not be visible in-game unless they are part of a player’s quest. In that case, they will be visible only to that player (and anyone else in their party currently engaged in the quest). Lesser characters that will not have an ACC counterpart can generally exist within the game 24/7, it will simply be the responsibility of the story department to know which characters are currently engaged in an activity so that they’re not used in another one somewhere else at the same time. Generally, NPCs that get used as elements in a personal quest shouldn’t also be used for ambient narrative to avoid conflicts. In the event that a special live event is in progress (like Wheely’s rescue), it should be possible to completely suspend the assignment of new quests relating to the NPCs involved, and active quests should also be suspended for the duration of the event, in order to prevent potentially incongruous interactions (we don’t want Laxman to be giddy with excitement over a new KI function while the cavern is in mourning, for instance).

To help keep players from getting frustrated or confused by receiving instructions to meet an NPC somewhere, only for them to be missing because their ACC is yucking it up in a pub downtown, players should be given temporary insight into a character’s location via the KI when they need to interact with them, along with receiving a ping when the ACC logs out (causing the NPC can return to their post) so that they know the character is available to speak with in the appropriate context. ACCs should stagger their availability so that players are not consistently locked out of progressing a quest because they can only play when the character is in ACC mode (having ACCs operate on 30-hour D’ni days would help with this). Additionally, players should only be able to receive a single assignment to locate a particular character, to prevent them from running into the same person in multiple places. If a quest line would conflict with this, an alternate branch should exist that puts the player off until they finish whatever quest currently has the NPC active. Then, after a delay, another quest can re-activate the NPC in another location.