As a French person I feel like it's my duty to explain strikes to you. - AdrienIer

Create an account  

 
WW #41. New Horizons.

WW # 41 - New Horizons

Life Support Status
1. Goreripper was killed on night one. He was a Human Expansionist League member.
2. BRickAstley has been lynched on day one. He was a Human Expansionist League member.
3. Bacchus
4. Serdoa
5. Rowain
6. Lewwyn
7. AdrienIer
8. Gazglum
9. Novice
10. Zakalwe was lynched on day two. He was an Earth First Liberationist.
11. Azarius ----- Killed Night 0 by saboteurs in an opening move to take over the ship.

There have been inventions throughout the history of mankind that changed forever the direction of its evolution. The wheel, the written word, the smelting of bronze and iron, the splitting of the atom. The perfection of fusing atoms came nearly too late in the human story. By the time it was perfected, providing cheap and clean power, it was nearly too late for the race that dominated their world. The skies were clogged with pollution, the seas high, nearly apocalyptical weather a regularity. Fusion power prevented things from getting much worse, but was deemed insufficient for turning back the clock.

So instead the nations of the world gathered together to create great ships that would travel to distant worlds, forming the Human Expansionist League. Through the use of cryogenic suspension the best and brightest of the world were bundled together to take humanities legacy to the stars, to keep the history of Homo-Sapiens Sapiens moving forward. To some however, the abandonment of Earth was the wrong decision. These groups decried not only the loss of humanities intellectual future, but also the sheer cost of the projects that took them away on one way trips. The most aggressive of these is known as the Earth First Liberationists.

It was Captain Azarius of the New Horizons that first discovered that something wasn’t completely right aboard the majestic kilometers long ship. Odd items showed in various places throughout the ship’s cargo manifests. Odd lines of code appeared throughout the ships central computer. In depth analysis of the 10,000 plus bodies on board showed outliers in unexpected numbers. Something was clearly amiss.

Not knowing who he could trust however, the Captain prepared alone, keeping his suspicions from the ten other members of the crew that were keeping the ship running as it ramped up speed and surged towards an orbital maneuver with Jupiter. Half hoping he was just being paranoid, he isolated various sub-systems of the computer and retasked them to perform similar, yet somewhat different tasks than they were normally supposed to do. His goal was the investigation of every member of his active crew, in order to either put to rest his suspicions, or have someone to lay them on.

It isn’t clear if he somehow tipped his hand, or if the plan intended for him to be killed, but less than a month into the 50+ years journey, the crew was startled out of their ennui by the jettisoning of the captains habitation pod, something that wasn’t due to occur until their arrival at a distant star. Knowing he didn’t have much time available, and presuming the conspiracy was limited to a few, Azarius broadcasted not only his suspicions, but also a listing of the programs he had prepared for his investigations. Not long after that, the constantly accelerating New Horizons moved beyond the range of the limited transmission capacities of the pod, and the Captain was consigned to the deep dark of space to die alone.

Following the captains announcements, the crew scrambled to secure the programs he had prepared. During the scramble however, many of the programs were damaged, as multiple people tried to access the same functions. The result was only a few copies of most of the programs being made, and none of them stable beyond a single use. To further complicate matters, the systems the programs were stored in by the crew were themselves unstable, never intended for the purposes they were being used for. Each pair of sub-routines was located on individual servers, and any time a crew member used one of them, the other stored in the same system would also be lost.

Despite having access to a number of programs, each crew member was functionally left with only half the number they had managed to secure. In order to find the traitors on board, the crew would have to work together. The greatest tool they had available was the ability to override the security measures for the various pods each crew member worked out of, once per day, and jettison that pod as the captains had been jettisoned. Once initiated, the pod that received the most commands to be jettisoned would follow the captain into the empty depths of space.

Thus, the crew is left to conduct the investigation the captain had intended on conducing himself. Those tasked with protecting the lives of tens of thousands would be reduced to taking the life of one at a time until no members of the Earth First Liberationists were left on the ship. Should they fail in their task however, the traitors would be able to use the ship to make a statement so horrific that the governments of Earth would be unable to ignore it, and would be forced instead to focus on their dying planet. The fate of humanity's future lies in your hands.

Crew Members
1. Goreripper
2. BRickAstley
3. Bacchus
4. Serdoa
5. Rowain
6. Lewwyn
7. AdrienIer
8. Gazglum
9. Novice
10. Zakalwe

The following is a list of all sub-routines Captain Azarius had managed to create before his death.

Tracer
This sub-routine is used at night, and will follow the actions of the chosen target throughout that night. The user will receive a list of all individuals their target interacted with during that night.
Auto-Doc
This sub-routine sends an auto-doc to the targets pod. Should the target be assaulted during the night, the auto-doc will act to save their life, as long as the damage was not too severe.
Lockdown
This sub-routine is used at night, and initiates an emergency lockdown on the targets pod. Most actions cannot go into or out from that pod during the night. This includes standard night kills. The lockdown ends at the start of the next day.
Repositioning
This sub-routine is used at night and causes the users pod to be shifted to another location on the hub. This process takes the entire night, and as such the user cannot be targeted for anything until the following day.
Spyware
This sub-routine is used at night, and will spy on a single target. Anyone that interact with that target will be reported to the user.
Weighted Voting
This sub-routine is used at night to provide additional weight to the users vote the following day. The use of this subroutine will result in a vote of 1.3, but this information will not be disclosed until the end of the day.
Jettison Interruption
This sub-routine is used at night to allow a manipulation of the jettison order the following day. When activated, the user can state in open communication “Jettison Override” in green text, and there will be no lynch that day.
Code Redirection
This sub-routine is used at night and allows the user to pick two targets. All abilities that would have affected the first name chosen are instead redirected to the second name. This includes all sub-routines and night kills.
Sensor
This sub-program can be used at night to analyze the number of votes cast the previous day and determines how many of the people on the successful lynch were Earth First Liberationists. An example result would be “Of the five people who voted to jettison Azarius, one was an Earth First Liberationists.
Hackproof
This sub-routine is activated at night and reinforces the security guarding access to the users pod, making it impossible for Earth First Liberationists members to kill them that night.
Polygraph
This sub-program can be used at night to analyze a statement made by another member of the crew on the previous day and determine whether or not it was true. Due to the nature of the examination however, any statements made under duress will provide unreliable results, and the operator will receive a statement reading undetermined.
Anchored
This sub-routine is activated at night and provides protection for the user by preventing their pod from being jettisoned on the following day. This ability can be activated before day one.
Background Check
This sub-routine is used at night, and can determine whether or not the target is a member of the Earth First Liberationists
Code Blocking
This sub-routine is used at night and allows the user to pick a target that will be unable to conduct any night actions, including night kills.

Standard RB Werewolf Rules:
  1. Days are 48 hours long. Nights are 24 hours long.
  2. Days and nights end at 10:00 PDT/18:00 UTC. The forum clock is used as the official clock. Votes and actions posted at xx:59 count, votes and actions posted at xx:00 do not.
  3. Posting is not allowed after the day and night deadlines until the GM has posted a phase resolution.
  4. In the event of extended forum downtime or downtime that occurs in close proximity of the deadline or some other event that disrupts the game, the day may be extended 24 hours at the GM's discretion.
  5. During the day each player may cast one vote for someone to be lynched.
  6. Votes must be posted in red text or they will not count. Votes with spelling errors of names do count so long as it's unambiguous in the GM's opinion whom is being voted for. Votes embedded in quotes do not count.
  7. The player with most lynch votes at the end of the day is lynched and eliminated from the game. Tiebreaks: The first person to reach their vote total will be lynched in the event of a tie.
  8. Anyone failing to vote for 2 consecutive game days or 3 days total will be mod killed and removed from the game with a loss.
  9. Dead players may make one posthumous post that doesn't contribute to discussion.
  10. Forum profile camping is not allowed.
  11. To prevent confusion that may arise in the case of cross posting, posts may not be edited for any reason.
  12. Players may not communicate with other players about the game outside the thread via PM, email, chat, quicktopics etc. unless told otherwise.
  13. Players must check their PMs and make sure they're alive each game day before posting.
  14. If all players are simultaneously eliminated, or the game reaches a stalemate situation, the game is a draw.
  15. Directly quoting role PMs or other communication from the GM isn't allowed unless otherwise specified.
  16. Breaking rules will result in penalties ranging from warnings to loss of abilities to being mod killed, depending on the severity of the infraction and the GM's discretion.
Reply

It is now currently night zero. Any night zero commands can be initiated until 18:00 UTC Thursday the 17th. Posting is restricted until that time. Game start is pending the response by Pindicator.
Reply

I still have not heard from Pindicator, and if I do not by 1800 UTC, I will be issuing a single 24h postponement of day1. If anyone has alternative methods for contacting him and can do so, it would be appreciated.
Reply

Allright. No pindi. Because of the small size of this game, I really want all players present. I'll be placing a 24h hold on the start of the game. Game will start tomorrow, Friday the 18th at 1800 UTC with or without Mr. Pindicator.
Reply

[Image: ezoOffI.jpg]
Reply

Well, I had time when I signed up to play a month ago tongue
Not so much lately, sorry for not checking in on time.

Anyway, here I am
Suffer Game Sicko
Dodo Tier Player
Reply

Due to time constraints Pindi is stepping down (the wuss) and Zakalwe is taking his place. Game start occurs as previously planned.
Reply

Day one begins.
Reply

Novice because he rests at the apex of the first triad of scum victory. Combining mobility flexibility and initiative.
Reply

Ahhh we're back. BRick any weird gambit you'd like to try this time ?
Reply



Forum Jump: