dev//: run startup
dev/hot/colon.exe
- - Out of cheese error - -
Oops, so we started today. Time to make an uneducated guess as to who is a traitor based solely on their avatar.
But I no longer have any kind of grudge against B:L. You, however, I would like to see dead.
Even though it was B:L who recommended me to kill you in the past two games I was playing as vigilante? :P
B:L: I took it as you were planning on targeting me with a vigilante-type power. Regardless, my vote still stands for now. We've got until 11pm tomorrow night to see how this plays out.
Yeah I agree, but last game there were 8. This is already a very weird game with people publicly targeting and everyone having a runtime. Would be nice to know for sure.
Edit, since no one else is posting - Hmm, I would hope the bad guys don't know each other, because if they did then the write access denial role would be pretty powerful for them to have (assuming one of them got one). Plus in the description of it, it uses group... which infers that there are several groups out there that can kill.
This is certainly...difficult. Using powers publicly really changes things.
If I had to guess, I'd say the vigilante style runtime is a private runtime. If it weren't, things would be very difficult, as the vigilante runtimes would have to ensure that they were never the only person using their action against a person, and they wouldn't have much choice in the matter of who they attacked, since the baddies could simply follow the trail of kills back to its source. It's hard to describe, but anyway, vigilante is probably private.
It's frustrating trying to analyze these powers, since any analysis I can think of would undoubtedly help the bad guys identify certain powers, which is bad for us.
Clarification: Does Write Access Denial prevent all uses of powers against the runtime user, or merely deletion? For example, if one were to use WAD against someone who was using the Sweeper runtime on that person, would the Sweep be stopped? Similary, would the use of WAD on an innocent file prevent all runtimes executed against the WAD user by innocent files, even if it didn't stop a nonlethal runtime?
Even I started to lose what I meant there. Okay, if someone uses WAD against a Sweeper who's Sweeping them, does the Sweep still work? If the Sweeper is an innocent, does the use of WAD against that Sweeping innocent prevent all innocent runtimes against that person, lethal and nonlethal alike?
Still overly complex. Can you elaborate on what Write Access Denial prevents?
I mean, gawrsh. This whole thing sure does hurt my head. Somebody come quick!
Posts
I don't respond well to threats.
Gnasty, I will forward you this PM if you don't believe me.
But I no longer have any kind of grudge against B:L. You, however, I would like to see dead.
But if you don't appreciate my help, then so be it.
retract: Grundlterror
vote: Shamus
This is an obvious lie. Clearly my huge file size is due to my humongous E-peen.
Even though it was B:L who recommended me to kill you in the past two games I was playing as vigilante? :P
B:L: I took it as you were planning on targeting me with a vigilante-type power. Regardless, my vote still stands for now. We've got until 11pm tomorrow night to see how this plays out.
Feels like ye olde times.
Edit: Also, B:L has been proven more dangerous then myself. Thus, I will seek to extinguish the threat.
target: B:L
Oops, seems I should not have whined after losing in FWD's phalla
Yeah, is this something we can get clarified?
Edit - maybe not
I agree, it seems awfully unlikely.
retract: del B:L
VOTES GET PLACED AND RETRACTED IN RED.
RUNTIMES GET PLACED AND RETRACTED IN LIME GREEN.
Edit, since no one else is posting - Hmm, I would hope the bad guys don't know each other, because if they did then the write access denial role would be pretty powerful for them to have (assuming one of them got one). Plus in the description of it, it uses group... which infers that there are several groups out there that can kill.
Clarification on something that pertains to the game.
I know, sorry.
You have until tomorrow night.
http://spreadsheets.google.com/pub?key=pyrvy1_YWCAVCld1u5eF-eA
I probably won't continue it, if anyone wants to use it as a starting point for a better spreadsheet.
!target: DevoutlyApathetic
!target FunkyWaltDogg
!remove Vic
He is malware, kill it with fire.
Thanks, maybe?
I'll get in on some of that hot target: FunkyWaltDogg action, too, pk. It's great fun for the whole file system!
Curiously, I'll try rm -rf Drez. So far, though, I love you all.
~lai
~lai
If I had to guess, I'd say the vigilante style runtime is a private runtime. If it weren't, things would be very difficult, as the vigilante runtimes would have to ensure that they were never the only person using their action against a person, and they wouldn't have much choice in the matter of who they attacked, since the baddies could simply follow the trail of kills back to its source. It's hard to describe, but anyway, vigilante is probably private.
It's frustrating trying to analyze these powers, since any analysis I can think of would undoubtedly help the bad guys identify certain powers, which is bad for us.
Clarification: Does Write Access Denial prevent all uses of powers against the runtime user, or merely deletion? For example, if one were to use WAD against someone who was using the Sweeper runtime on that person, would the Sweep be stopped? Similary, would the use of WAD on an innocent file prevent all runtimes executed against the WAD user by innocent files, even if it didn't stop a nonlethal runtime?
Even I started to lose what I meant there. Okay, if someone uses WAD against a Sweeper who's Sweeping them, does the Sweep still work? If the Sweeper is an innocent, does the use of WAD against that Sweeping innocent prevent all innocent runtimes against that person, lethal and nonlethal alike?
Still overly complex. Can you elaborate on what Write Access Denial prevents?
I mean, gawrsh. This whole thing sure does hurt my head. Somebody come quick!