• Announcements

    • admin

      Rules and Guidelines for the Hinterland Forums   02/24/2016

      The Hinterland Forums strive to be a place that is positive, inclusive, welcoming and comfortable. A community where intelligent, entertaining and meaningful conversations can occur. The rules are presented with these goals in mind. NOTE: Warnings, bans, and lifetime bans are all at the discretion of Hinterland depending on the seriousness of the infraction. Rules and Guidelines for the Hinterland Forums No Backseat Moderating Let the moderators do the moderating. Backseat moderating is when people who are not moderators try to enforce the forum rules. If you see a person breaking the rules, take advantage of the Report () button or simply ignore the offensive post(s), thread, or review. Report Posts to Moderators Should you observe a fellow Community member breaking these rules please report the post or item by clicking flag button located on every item, post, and review. Do not do any of the following: • Flame or insult other members • Bypass any filters • Post personally identifiable information (i.e. name, address, email, phone number, etc.) • Bump threads • Derail a thread's topic • Post links to phishing sites • Post spam or Re-post Closed, Modified, Deleted Content • Repetitively post in the incorrect forum • Openly argue with a moderator Off-Limit Topics/Replies Do not post any topics/replies containing the following: • Porn, inappropriate or offensive content, or leaked content or anything else not safe for work • Any discussion of piracy will result in a permanent ban from the Hinterland Community including, but not limited to: Cheating, hacking, game exploits • Threats of violence or harassment, even as a joke • Posted copyright material such as magazine scans • Soliciting, begging, auctioning, raffling, selling, advertising, referrals • Racism, sexism, homophobia, or discrimination • Abusive language, including swearing • Religious, political, and other “prone to huge arguments” threads No support will be given to those using cheat tools, or hacked/pirated copies, and any forum users who discuss pirated/pirating software will be removed. Please note that these guidelines may be edited or added to by Hinterland Studio as needed. If there is something you do not agree with, please email info@hinterlandgames.com
    • admin

      The Light at the end of The Long Dark -- Launch Date, WINTERMUTE, Next Sandbox Update   05/16/2017

      For the latest information on WINTERMUTE (story mode in The Long Dark), as well as details on the final sandbox update prior to our August 1 launch, check out our recent Dev Diary here: http://www.thelongdark.com/news/posts/light-at-the-end/ And while you're there, be sure to have a look at our new FAQ as well: http://www.thelongdark.com/news/posts/frequently-asked-questions/
    • admin

      The Long Dark Sandbox **May 2017 Test Branch** [OPT-IN, FORUM PASSWORD, SPOILERS]   05/19/2017

      Hello community, 

      As we did with the December 2016 Sandbox Update, we are implementing a TEST BRANCH for The Long Dark's MAY/JUNE 2017 Update, FAITHFUL CARTOGRAPHER. This reflects the fact that we have a huge diversity of players on a variety of hardware configurations, and as a small studio we just can’t test them all! 

      The idea here is to provide an early version of the next update, about a week or so before we’d like to launch it officially in the Release branch (i.e. where you are currently getting it), so that we get some extra time to find bugs, crashes, and any other issues before it goes lives for the rest of our community. 
        >>> IF YOU DO NOT OPT-IN TO THE TEST BRANCH, YOU WILL NOT GET IT. I.e. You will not get the Test Branch build "by accident". This should help keep spoilers to a minimum. Here on Official Forums the Test Branch Discussion subforum requires a password to access. The password is: test_branch
      Some details. READ THESE CAREFULLY: 

      * The Test Branch is for STEAM ONLY. It is available for Windows, Mac, and Linux. 
      * The Test Branch is full of SPOILERS. If you don’t want to see what’s in the next update, stay out of the Test Branch and all its discussions. 
      * The Test Branch is a tool for us to find issues with Work In Progress features. We’re primarily looking for feedback on bugs, crashes, and any major balancing issues. 
      * When reporting on bugs or issues, please use the appropriate TEST BRANCH sub-forums on Steam and in our Official Community. DO NOT DISCUSS TEST BRANCH FEATURES outside the Test Branch sub-forums. Those posts will be moved or deleted. 
      * When reporting on bugs or issues, please use the posted bug submission procedures. This will help the development team filter the feedback, eliminate duplicates, and in general ensure we can act on the feedback in a more timely fashion. 

      Our hope is that this new Test Branch process will allow us to ensure we can continue to put out stable Sandbox updates well into the future. 

      We’re very hopeful that the people who choose to opt-in to this Test Branch will approach this as a way to help ensure the updates are as smooth and stable as possible, and not use the Test Branch discussion as a forum to lobby for or against certain features or content. 

      As always, The Long Dark is a community-informed, not community-driven, project. We look forward to enlisting your help in identifying whatever issues we’ve missed in our own internal testing! 

      For more details, please check out the TEST BRANCH discussion forums [SPOILERS!] http://hinterlandforums.com/index.php?/forum/81-test-branch-spoilers/ (See password info above for access)

      Thank you! 

      The Hinterland Team 

EternityTide

Members
  • Content count

    1,060
  • Joined

  • Last visited

Community Reputation

321 Excellent

2 Followers

About EternityTide

  • Rank
    Advanced Member

Recent Profile Visitors

501 profile views
  1. Such is the risk you take when you communicate with any large group of people - the general rule of thumb is that you cannot EVER please everyone. It's impossible. The trick is to manage your community in such a way that your communication is as clear as possible to avoid confusion, and to make decisions that benefit the community majority. You will always have a minority who will complain and scream blue murder. The only thing you can control, really, is what information you give out, so if you keep that information to a high standard then you are doing fine. In the meantime, batten down the hatches and ride out the whingers (but don't entirely ignore them, because you may miss some important concerns).
  2. [Ambles in nonchalantly] [looks around forum] [Notices firestorm] Christ on a bike...... [performs tactical retreat]
  3. I seriously doubt that a makeshift arrow from a fairly low draw weight bow would be able to penetrate a Wolf skull. For a bow of this poundage, the killing factor is blood loss. Very rarely would you get a shot that would destroy vital organs.
  4. I honestly think that the "one-shot-kill" mechanic needs to be done away with. Unless you hit something absolutely vital, there's no reason a wolf should go down in one shot. Therefore, I think the hitboxes need to be revamped, with lethal shots being the eyes, the heart and the base of the neck. If you hit anywhere else, a timer starts, with an RNG that calculates every ten seconds whether the blood clots or not. If the timer runs out before the blood clots, the wolf dies. Of course, the wolf will run away and be afraid of you if shot, but this gets rid of the "fmolwba" aspect. There should also be a cool down timer that reduces a wolf's aggression to 0, making it flee at any chance it gets. A tiny aggro radius around it should trigger a unique attack scene where the wolf will immediately pounce on you and then run away after knocking you flat on your back.
  5. I like the way this idea has fleshed out, so I would like to add to it. First of all, I would like to address this issue of "free meat on legs with a bad attitude" that wolves are now perceived. Lately I've been playing a lot of Don't Starve, and the behaviour of a certain creature springs to mind. The Varg, as it is called, is an aggressive, high HP wolf-like creature who can summon hounds (which are smaller and weaker, but still dangerous adversaries) by howling - without this ability, the Varg would be much easier to defeat. Therefore I suggest a tweak to the wolf behaviour. Lone wolves would behave similarly to @Kyopaxa's idea, however they would be more timid and reluctant to attack. Entering a certain radius would aggro the wolf, who would bark and run away - this bark would alert other wolves within 200-250 metres to your presence and they would converge on you. Wind direction would asymmetrically increase the detection radius, meaning that upwind you are more likely to be detected, but downwind you can get closer without being detected. The wolves would also be equipped with a "vision cone" that is sensitive to movement at long range, but can detect you regardless of position or movement at short range. They would also have a dynamic hearing radius - in cold, clear, windless conditions, their hearing radius is at its furthest extent. Blizzard conditions reduce it to within a 10 metre radius (visibility impairments also effect their vision cone). Wolves should also posses a internal volume count. Fully fed wolves are less likely to pursue you, less likely to attack, but are also disinterested in decoys. Starving wolves are very likely to pursue you, more likely to attack but CAN be distracted by decoys. Killing a starving wolf only provides 2 kilos of meat, and a 75% condition hide. Fully fed wolves provide a full 6 kilos of meat and an 100% condition hide. Overhunting an area increases the chance of the local wolf population becoming starving wolves. Cooking food on the campfire increases your detection range downwind for both bears and wolves, and at night, using torches or lanterns in clear conditions attracts wolves.
  6. I'd rather get a whole new PC. My CPU is coming up for 4 years old now, and it was the lower end of the market. The motherboard is second hand, my HDD is reasonably well managed, so I have still got a few hundred gigabytes left. A tower PC is rather bulky to transport, so I think I will invest in a gaming laptop.
  7. It's the GPU. I reckon some of the RAMDACs have shuffled off this mortal coil. It's only been about 5 months since I was fitting new RAM sticks (16GB), I gave her a good brush down and clean up. My room was very warm when it crashed, so perhaps the GPU overheated. I've been keeping my room at around 15° since as a precaution. No problems since (I think the GPU has damage control software built in that has helped mitigate damaged sections, unless the damage was not that serious). Anyhoo, I'm keeping a weather eye on my GPU in case it acts up again.
  8. I believe that this is a sign that I need to move on to a new PC: (Zoomed in to make the picture small enough to upload) Sadly, this might be the last days for my computer. It's picked itself back up since this incident, but the prognosis is not good.
  9. I'm inclined to agree with @rla1974, it is a good idea. For extended periods, improving Forging skill could both be acquired from books and crafting. @alone sniper don't assume that your playstyle is the same as everyone else. I'm also expecting more crafting in forging, so a forging skill would come in handy.
  10. Don't get me wrong, I much prefer fresh milk, but for cereal, baking and for adding to Tea, UHT cartoned milk is a decent stand in.
  11. I do believe this is the time to introduce people to the concept of UHT milk. At home, because I live 20 miles (32 km) from the nearest decent supermarket, I bulk buy crates of UHT milk in sealed cartons, to be used for the next 3 months. UHT milk can keep for six to nine months unrefrigerated, so it is well within the timeframe for TLD.
  12. Thanks, I just hope it is. The pumpkin was very mild tasting, and I used a regular pumpkin rather than a sweet pumpkin. Making it, it felt all the world like making a sweet quiche
  13. I've never tried it before, so we'll see how it goes!