Comments

• Tru3 has frequently stated that he feels that the developers of this game fell into success and are fortunate because of their inability to make good decisions. Sure that isn’t the worst thing someone has said about BHVR, but I doubt they are looking into working with him closely when he says stuff like that. 

  in Tru3 wasn't chosen?! Comment by Chiaki16 September 18, 2018

• Orion said:

  @Chiaki16 said:
  You aren’t reading what I am saying and you are still straw manning... I might as well be discussing this topic with a tree at this point. Regardless I will try one last example. A company exists to please its fans and make money right? If this situation has costs them both the enjoyment of their fans and money in what way was this the “correct” path for them to take? 

  Trick question. They couldn't have known the result beforehand. Hindsight is 20/20, as they say. Regardless, it's not on developers to dispel each and every rumor their fanbase can come up with.

  
  

  Orion said:

  @Chiaki16 said:
  You aren’t reading what I am saying and you are still straw manning... I might as well be discussing this topic with a tree at this point. Regardless I will try one last example. A company exists to please its fans and make money right? If this situation has costs them both the enjoyment of their fans and money in what way was this the “correct” path for them to take? 

  Trick question. They couldn't have known the result beforehand. Hindsight is 20/20, as they say. Regardless, it's not on developers to dispel each and every rumor their fanbase can come up with.

  I would argue that anyone who has been a child knows what the reaction to disappointment is, especially when you string people along with comments of “soon” instead of “not today”. I would also argue that it is the responsibility of the developers to manage their  community and address issues as they arise (not referencing queen here, every comment I make is directed at BHVR as a whole).
  
  This is also not the first major faux pas made by BHVR during this dlc cycle. They were banning people on the twitch stream when they were upset we got to watch amateur hour dbd gameplay instead of getting info on the new killer and/or more answers for popular questions. That ALSO could’ve been avoided if they announced that it was going to be a “watch the devs” stream earlier then an hour beforehand. 
  
  I have supported the game both through buying the game with all dlc 3 times and also donating/subscribing to multiple twitch channels. I obviously like the game, all I ask is that the devs actually handle PR like they should so I don’t feel like I’m supporting a company that doesn’t respect its community.

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018

• Orion said:

  @Chiaki16 said:
  People have different levels of understanding, he is straw manning for multiple posts. If I am banned for saying that he seems to be incapable of understanding after he fails to understand then I would rather stay in other communities to be honest.

  You are to blame; not the devs. The official information was available for all to see, and there was no date attached. They're not obligated to waste their time dispelling every single rumor. You are to blame.

  You aren’t reading what I am saying and you are still straw manning... I might as well be discussing this topic with a tree at this point. Regardless I will try one last example. A company exists to please its fans and make money right? If this situation has costs them both the enjoyment of their fans and money in what way was this the “correct” path for them to take? 

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018

• @Orion said:

  @Tizzle said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:
  The whole situation with this dlc is unprofessional at best and disrespectful to your community at worst. I get "hyping up" a game or dlc, but letting a false release date sit for 2 weeks and then beating around the bush with an actual announcement is just bad PR.

  There was no false release date. There was speculation and nothing more.

  There was a date posted on the dbd wiki for 2 weeks. This date was based upon the schedule for clown. A company letting that sit there for 2 weeks and not giving us at least a release date today is "unprofessional at best and disrespectful to your community at worst".

  The wiki is not run by the devs, and it was made very clear that it was speculative.

  And I was very clear, leaving up a false date on the wiki without a plan to give a date was (say it with me) "unprofessional at best and disrespectful to your community at worst". Bonus points for having their community manager flaunting around the forums saying "soon" to all the hype posts. Maybe she isn't supposed to give us information, but then why is she increasing expectations?

  Imagine if they had just said a week ago (or shoot, even 5-6 hours ago) that they have no release date yet, they would've avoided this mess.

  None of the devs left a false date on the wiki because they have no control over it. You have based your argument on a faulty premise.

  You run a game company and have an upcoming dlc that you know many people are excited for. You see a false release date based on your previous releases pop up on the wiki for your game and decide to NOT correct that date in any way. All the negative emotions that stem from that are directly on the devs, they allowed people to be misled when a small "release date TBA" would've stopped this entire situation. Just because they didn't put the date there doesn't mean their negligence in correcting the date was an "okay" way to handle the ordeal.

  They allowed nothing. You assumed a fansite's information was an official statement from the developers - despite the fact that the fansite made it very clear the information was speculative - and are now looking for someone to blame other than yourself. You and only you are to blame for your false assumption.

  Careful with the fallacies there, I assumed nothing. I knew the date was speculative, but that doesn't change the fact that it was based on release patterns and left up without any plan to correct the information. To be honest I don't even know why they are letting this happen, it is killing their hype and is going to easily lose them sales.

  So you knew it was speculative and still claim the devs are at fault for your acceptance of speculation? I'm going to ignore you now lest I say something that gets me banned.

  Apparently the roadmap is pure speculation...

  Most are upset because for some odd reason BHVR just cannot fathom it appropriate to communicate with their community about releases.

  It's mind boggling.

  Because when they did and the releases were delayed, they got ######### for it. Now the official release date is "when it's ready", though they do give a specific interval of when it's due for release.

  "Because when they did and the releases were delayed, they got ######### for it". Welcome to the world of business, meet deadlines or take the flak. Everyone gets this, they usually handle it by paying someone to be the punching bag. > @Michiko said:

  Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  The whole situation with this dlc is unprofessional at best and disrespectful to your community at worst. I get "hyping up" a game or dlc, but letting a false release date sit for 2 weeks and then beating around the bush with an actual announcement is just bad PR.

  There was no false release date. There was speculation and nothing more.

  There was a date posted on the dbd wiki for 2 weeks. This date was based upon the schedule for clown. A company letting that sit there for 2 weeks and not giving us at least a release date today is "unprofessional at best and disrespectful to your community at worst".

  The wiki is not run by the devs, and it was made very clear that it was speculative.

  And I was very clear, leaving up a false date on the wiki without a plan to give a date was (say it with me) "unprofessional at best and disrespectful to your community at worst". Bonus points for having their community manager flaunting around the forums saying "soon" to all the hype posts. Maybe she isn't supposed to give us information, but then why is she increasing expectations?

  Imagine if they had just said a week ago (or shoot, even 5-6 hours ago) that they have no release date yet, they would've avoided this mess.

  None of the devs left a false date on the wiki because they have no control over it. You have based your argument on a faulty premise.

  You run a game company and have an upcoming dlc that you know many people are excited for. You see a false release date based on your previous releases pop up on the wiki for your game and decide to NOT correct that date in any way. All the negative emotions that stem from that are directly on the devs, they allowed people to be misled when a small "release date TBA" would've stopped this entire situation. Just because they didn't put the date there doesn't mean their negligence in correcting the date was an "okay" way to handle the ordeal.

  They allowed nothing. You assumed a fansite's information was an official statement from the developers - despite the fact that the fansite made it very clear the information was speculative - and are now looking for someone to blame other than yourself. You and only you are to blame for your false assumption.

  Careful with the fallacies there, I assumed nothing. I knew the date was speculative, but that doesn't change the fact that it was based on release patterns and left up without any plan to correct the information. To be honest I don't even know why they are letting this happen, it is killing their hype and is going to easily lose them sales.

  So you knew it was speculative and still claim the devs are at fault for your acceptance of speculation? I'm going to ignore you now lest I say something that gets me banned.

  You are apparently slow, since you still are adding in a straw man. I will now use capitalization to make my points clearer. I DID NOT accept any speculation, BUT I understand that a company that DOES NOT address a release date that is based on past releases IS being irresponsible to their community. This DOES NOT affect me, I WAS NOT buying the DLC today. I DO NOT care when it is released. I DO care that they were unprofessional, because I DO LITERALLY support them with money and I DO NOT want to support a company that disrespects their consumers.

  I would refrain from insulting others as this could lead to being banned. Just a helpful warning.

  People have different levels of understanding, he is straw manning for multiple posts. If I am banned for saying that he seems to be incapable of understanding after he fails to understand then I would rather stay in other communities to be honest.

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018

• @Orion said:

  @Chiaki16 said:

  @DocOctober said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:
  The whole situation with this dlc is unprofessional at best and disrespectful to your community at worst. I get "hyping up" a game or dlc, but letting a false release date sit for 2 weeks and then beating around the bush with an actual announcement is just bad PR.

  There was no false release date. There was speculation and nothing more.

  There was a date posted on the dbd wiki for 2 weeks. This date was based upon the schedule for clown. A company letting that sit there for 2 weeks and not giving us at least a release date today is "unprofessional at best and disrespectful to your community at worst".

  The wiki is not run by the devs, and it was made very clear that it was speculative.

  And I was very clear, leaving up a false date on the wiki without a plan to give a date was (say it with me) "unprofessional at best and disrespectful to your community at worst". Bonus points for having their community manager flaunting around the forums saying "soon" to all the hype posts. Maybe she isn't supposed to give us information, but then why is she increasing expectations?

  Imagine if they had just said a week ago (or shoot, even 5-6 hours ago) that they have no release date yet, they would've avoided this mess.

  None of the devs left a false date on the wiki because they have no control over it. You have based your argument on a faulty premise.

  You run a game company and have an upcoming dlc that you know many people are excited for. You see a false release date based on your previous releases pop up on the wiki for your game and decide to NOT correct that date in any way. All the negative emotions that stem from that are directly on the devs, they allowed people to be misled when a small "release date TBA" would've stopped this entire situation. Just because they didn't put the date there doesn't mean their negligence in correcting the date was an "okay" way to handle the ordeal.

  They allowed nothing. You assumed a fansite's information was an official statement from the developers - despite the fact that the fansite made it very clear the information was speculative - and are now looking for someone to blame other than yourself. You and only you are to blame for your false assumption.

  Careful with the fallacies there, I assumed nothing. I knew the date was speculative, but that doesn't change the fact that it was based on release patterns and left up without any plan to correct the information. To be honest I don't even know why they are letting this happen, it is killing their hype and is going to easily lose them sales.

  "Left up" without any plan to correct the information. Correct to what if no further information is available? There was a fat, red "not confirmed" right after the date. If people can't be bothered to read, it's their fault.

  The devs are not at fault in this case, solely the community who can't read.

  The "not confirmed" was added a few days ago, and was solely added as a "cover my butt" move from a FANSITE. If a fansite is doing damage control then you would think the company in question would have some sort of plan to avert people from thinking it was today.

  They did have a plan. Unfortunately, it relied on people understanding the difference between a rumor and an official statement. In short, it relied on people being somewhat intelligent. That's where the plan fell apart.

  A plan that involves "everyone needs to assume that we will have no pattern to our releases and will not address any sort of release date" is a really ######### plan. I wonder if you can actually find another company that has such a lackadaisical approach to such a large money making event like a dlc release.

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018

• @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:
  The whole situation with this dlc is unprofessional at best and disrespectful to your community at worst. I get "hyping up" a game or dlc, but letting a false release date sit for 2 weeks and then beating around the bush with an actual announcement is just bad PR.

  There was no false release date. There was speculation and nothing more.

  There was a date posted on the dbd wiki for 2 weeks. This date was based upon the schedule for clown. A company letting that sit there for 2 weeks and not giving us at least a release date today is "unprofessional at best and disrespectful to your community at worst".

  The wiki is not run by the devs, and it was made very clear that it was speculative.

  And I was very clear, leaving up a false date on the wiki without a plan to give a date was (say it with me) "unprofessional at best and disrespectful to your community at worst". Bonus points for having their community manager flaunting around the forums saying "soon" to all the hype posts. Maybe she isn't supposed to give us information, but then why is she increasing expectations?

  Imagine if they had just said a week ago (or shoot, even 5-6 hours ago) that they have no release date yet, they would've avoided this mess.

  None of the devs left a false date on the wiki because they have no control over it. You have based your argument on a faulty premise.

  You run a game company and have an upcoming dlc that you know many people are excited for. You see a false release date based on your previous releases pop up on the wiki for your game and decide to NOT correct that date in any way. All the negative emotions that stem from that are directly on the devs, they allowed people to be misled when a small "release date TBA" would've stopped this entire situation. Just because they didn't put the date there doesn't mean their negligence in correcting the date was an "okay" way to handle the ordeal.

  They allowed nothing. You assumed a fansite's information was an official statement from the developers - despite the fact that the fansite made it very clear the information was speculative - and are now looking for someone to blame other than yourself. You and only you are to blame for your false assumption.

  Careful with the fallacies there, I assumed nothing. I knew the date was speculative, but that doesn't change the fact that it was based on release patterns and left up without any plan to correct the information. To be honest I don't even know why they are letting this happen, it is killing their hype and is going to easily lose them sales.

  So you knew it was speculative and still claim the devs are at fault for your acceptance of speculation? I'm going to ignore you now lest I say something that gets me banned.

  You are apparently slow, since you still are adding in a straw man. I will now use capitalization to make my points clearer. I DID NOT accept any speculation, BUT I understand that a company that DOES NOT address a release date that is based on past releases IS being irresponsible to their community. This DOES NOT affect me, I WAS NOT buying the DLC today. I DO NOT care when it is released. I DO care that they were unprofessional, because I DO LITERALLY support them with money and I DO NOT want to support a company that disrespects their consumers.

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018

• @DocOctober said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:
  The whole situation with this dlc is unprofessional at best and disrespectful to your community at worst. I get "hyping up" a game or dlc, but letting a false release date sit for 2 weeks and then beating around the bush with an actual announcement is just bad PR.

  There was no false release date. There was speculation and nothing more.

  There was a date posted on the dbd wiki for 2 weeks. This date was based upon the schedule for clown. A company letting that sit there for 2 weeks and not giving us at least a release date today is "unprofessional at best and disrespectful to your community at worst".

  The wiki is not run by the devs, and it was made very clear that it was speculative.

  And I was very clear, leaving up a false date on the wiki without a plan to give a date was (say it with me) "unprofessional at best and disrespectful to your community at worst". Bonus points for having their community manager flaunting around the forums saying "soon" to all the hype posts. Maybe she isn't supposed to give us information, but then why is she increasing expectations?

  Imagine if they had just said a week ago (or shoot, even 5-6 hours ago) that they have no release date yet, they would've avoided this mess.

  None of the devs left a false date on the wiki because they have no control over it. You have based your argument on a faulty premise.

  You run a game company and have an upcoming dlc that you know many people are excited for. You see a false release date based on your previous releases pop up on the wiki for your game and decide to NOT correct that date in any way. All the negative emotions that stem from that are directly on the devs, they allowed people to be misled when a small "release date TBA" would've stopped this entire situation. Just because they didn't put the date there doesn't mean their negligence in correcting the date was an "okay" way to handle the ordeal.

  They allowed nothing. You assumed a fansite's information was an official statement from the developers - despite the fact that the fansite made it very clear the information was speculative - and are now looking for someone to blame other than yourself. You and only you are to blame for your false assumption.

  Careful with the fallacies there, I assumed nothing. I knew the date was speculative, but that doesn't change the fact that it was based on release patterns and left up without any plan to correct the information. To be honest I don't even know why they are letting this happen, it is killing their hype and is going to easily lose them sales.

  "Left up" without any plan to correct the information. Correct to what if no further information is available? There was a fat, red "not confirmed" right after the date. If people can't be bothered to read, it's their fault.

  The devs are not at fault in this case, solely the community who can't read.

  The "not confirmed" was added a few days ago, and was solely added as a "cover my butt" move from a FANSITE. If a fansite is doing damage control then you would think the company in question would have some sort of plan to avert people from thinking it was today.

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018

• @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:
  The whole situation with this dlc is unprofessional at best and disrespectful to your community at worst. I get "hyping up" a game or dlc, but letting a false release date sit for 2 weeks and then beating around the bush with an actual announcement is just bad PR.

  There was no false release date. There was speculation and nothing more.

  There was a date posted on the dbd wiki for 2 weeks. This date was based upon the schedule for clown. A company letting that sit there for 2 weeks and not giving us at least a release date today is "unprofessional at best and disrespectful to your community at worst".

  The wiki is not run by the devs, and it was made very clear that it was speculative.

  And I was very clear, leaving up a false date on the wiki without a plan to give a date was (say it with me) "unprofessional at best and disrespectful to your community at worst". Bonus points for having their community manager flaunting around the forums saying "soon" to all the hype posts. Maybe she isn't supposed to give us information, but then why is she increasing expectations?

  Imagine if they had just said a week ago (or shoot, even 5-6 hours ago) that they have no release date yet, they would've avoided this mess.

  None of the devs left a false date on the wiki because they have no control over it. You have based your argument on a faulty premise.

  You run a game company and have an upcoming dlc that you know many people are excited for. You see a false release date based on your previous releases pop up on the wiki for your game and decide to NOT correct that date in any way. All the negative emotions that stem from that are directly on the devs, they allowed people to be misled when a small "release date TBA" would've stopped this entire situation. Just because they didn't put the date there doesn't mean their negligence in correcting the date was an "okay" way to handle the ordeal.

  They allowed nothing. You assumed a fansite's information was an official statement from the developers - despite the fact that the fansite made it very clear the information was speculative - and are now looking for someone to blame other than yourself. You and only you are to blame for your false assumption.

  Careful with the fallacies there, I assumed nothing. I knew the date was speculative, but that doesn't change the fact that it was based on release patterns and left up without any plan to correct the information. To be honest I don't even know why they are letting this happen, it is killing their hype and is going to easily lose them sales.

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018

• @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:
  The whole situation with this dlc is unprofessional at best and disrespectful to your community at worst. I get "hyping up" a game or dlc, but letting a false release date sit for 2 weeks and then beating around the bush with an actual announcement is just bad PR.

  There was no false release date. There was speculation and nothing more.

  There was a date posted on the dbd wiki for 2 weeks. This date was based upon the schedule for clown. A company letting that sit there for 2 weeks and not giving us at least a release date today is "unprofessional at best and disrespectful to your community at worst".

  The wiki is not run by the devs, and it was made very clear that it was speculative.

  And I was very clear, leaving up a false date on the wiki without a plan to give a date was (say it with me) "unprofessional at best and disrespectful to your community at worst". Bonus points for having their community manager flaunting around the forums saying "soon" to all the hype posts. Maybe she isn't supposed to give us information, but then why is she increasing expectations?

  Imagine if they had just said a week ago (or shoot, even 5-6 hours ago) that they have no release date yet, they would've avoided this mess.

  None of the devs left a false date on the wiki because they have no control over it. You have based your argument on a faulty premise.

  You run a game company and have an upcoming dlc that you know many people are excited for. You see a false release date based on your previous releases pop up on the wiki for your game and decide to NOT correct that date in any way. All the negative emotions that stem from that are directly on the devs, they allowed people to be misled when a small "release date TBA" would've stopped this entire situation. Just because they didn't put the date there doesn't mean their negligence in correcting the date was an "okay" way to handle the ordeal.

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018

• @Orion said:

  @Chiaki16 said:

  @Orion said:

  @Chiaki16 said:
  The whole situation with this dlc is unprofessional at best and disrespectful to your community at worst. I get "hyping up" a game or dlc, but letting a false release date sit for 2 weeks and then beating around the bush with an actual announcement is just bad PR.

  There was no false release date. There was speculation and nothing more.

  There was a date posted on the dbd wiki for 2 weeks. This date was based upon the schedule for clown. A company letting that sit there for 2 weeks and not giving us at least a release date today is "unprofessional at best and disrespectful to your community at worst".

  The wiki is not run by the devs, and it was made very clear that it was speculative.

  And I was very clear, leaving up a false date on the wiki without a plan to give a date was (say it with me) "unprofessional at best and disrespectful to your community at worst". Bonus points for having their community manager flaunting around the forums saying "soon" to all the hype posts. Maybe she isn't supposed to give us information, but then why is she increasing expectations?

  Imagine if they had just said a week ago (or shoot, even 5-6 hours ago) that they have no release date yet, they would've avoided this mess.

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018

• @Orion said:

  @Chiaki16 said:
  The whole situation with this dlc is unprofessional at best and disrespectful to your community at worst. I get "hyping up" a game or dlc, but letting a false release date sit for 2 weeks and then beating around the bush with an actual announcement is just bad PR.

  There was no false release date. There was speculation and nothing more.

  There was a date posted on the dbd wiki for 2 weeks. This date was based upon the schedule for clown. A company letting that sit there for 2 weeks and not giving us at least a release date today is "unprofessional at best and disrespectful to your community at worst".

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018

• The whole situation with this dlc is unprofessional at best and disrespectful to your community at worst. I get "hyping up" a game or dlc, but letting a false release date sit for 2 weeks and then beating around the bush with an actual announcement is just bad PR.

  in Leaving Communities in the Dark is NOT a Smart Strategy Comment by Chiaki16 September 11, 2018
• Pretty sure I saw your comment and it said “I am Muslim” not “if I was Muslim”. That could easily be construed as you baiting people who were effected by 9/11, which you definitely should be banned for.

  in Do the same mods run this forum as the steam forum? Comment by Chiaki16 September 2, 2018
• You want to fix broken add ons like the pig’s? Or can you at least remove them/make a note that they are bugged. This really seems like something that shouldn’t have to be asked after half a year.

  in Question for the Youtube Q&A Comment by Chiaki16 August 24, 2018
• That is why I was hesitant to participate here. The only reason I even made an account was because of hype for the new chapter.

  in Is this forum moderated or not? Comment by Chiaki16 August 24, 2018

• Anzi130 said:

  I feel like most signs point to an Oni-inspirered killer eventhough i’d Much rather have the slit-mouthed woman..
  
  the reason i say so is this.. first off.. the mask that we see. It has 3 eyes. Oni was known to have up to 3 eyes. The woman in the clip seems to be naked, or atleast barefoot. She wouldnt be able to make those Sounds from the teaser trailer.. and finally.. the ‘samurai’ might be a Ninja, i Think. He’s wearing completely Black clothing

  What if the first teaser was the samurai running to confront his cheating wife? A struggle ensues that knocks over a lamp and maybe upsets a child? Seems plausible to me.
  
  Edit: stroke of genius, the lover was already murdered and that is why the samurai is covered in blood.

  in The new Killer & Survivor Comment by Chiaki16 August 23, 2018

• @RuneStarr said:
  Well I guess that rules out the Teacher since that is in the game files.
  I really hope its not the stupid ass creeper (politics aside, the movies aren't even good), but based on stream comments and flavor text on Feng's new outfit... ugh

  One of the outfits also has an Aliens reference so there is still hope it isn't the Creeper.

  in New chapter hints! Comment by Chiaki16 August 16, 2018