Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
24 
Report this post
I'm pretty sure the issue has been fixed, and you seem to just want an excuse to brigade. If you can show reproduction steps, or video of the issue happening, or anything besides being grumpy I'm sure we could help you.
Can you remember the steps you took to make it happen twice in a row?
Are you a dev? Where's your tag?
Anyway, I've been quite elaborate in explaining the issue: During the tutorial, the first time you get the objective to loot ONE item from a locker but you instead loot EVERYTHING, that's when it bugs out. This is because later in the tutorial, the objective tells us to loot that from the locker which we have already looted. As a layman, this seems like a simple fix.
Is it fixed though, as you presume? If so, why are people keeping this thread alive? My last comment was elicited by that very fact.
Oooh, that's good info, let me see if I can make it happen and I'll record it.
Not a dev with Ironwood at all, it's just how communities help their own. If it can be consistently reproduced it's a lot easier to present as a bug.
I just tried to reproduce this - did you remember doing anything else? I tried filling the fuel can from the wreck outside, and the outside pump as soon as I got the prybar and could use it, and it didn't happen, it just went through all the normal tutorial steps. Can you reproduce it and grab a screenshot or video of when it happened?
I'm not sure why people are keeping this thread alive without posting video or reproduction steps - I just replayed the intro twice, and followed SOAP!!!'s directions above, then yours, and each time the intro automatically proceeded past the 'pack supplies' stage with no drama, and each time the toolbox and locker were emptied as soon as I could.
Here's the pic of my backpack and the locker to show it was emptied as soon as it was interactible: https://images.steamusercontent.com/ugc/28816881401278114/B17981EBF19E1021780A8BE505CC62F78853A931/?imw=5000&imh=5000&ima=fit&impolicy=Letterbox&imcolor=%23000000&letterbox=false
I'm not saying you didn't experience this - but have you experienced this recently, and can you reproduce it? It could potentially help the bug get fixed for others that experience it.
This thread is being kept alive because there is a game breaking bug in the tutorial section. I think people stating as much and coming to look for help warrants the continued use of this thread.
If you don't have the issue, then move along I guess. People aren't going to go through a lot of hoops to satisfy your curiosity. I am glad you want to help, but your tone is kinda weird telling people this bug is fixed and it can't be so if they don't offer video proof. Clearly people experienced it recently, that's what all the new posts are about. I imagine traffic is up because the game is included in the current Humble Choice.
The steps I'm asking people provide are just how quality assurance works in software dev. Providing reproduction steps, video, or screenshots are of course not obligatory, but if you'd like to see the bug fixed, it's the kind of information the devs would need to be able to do it.
There's nothing wrong with complaining about a bug you experienced, and noone is under any obligation to provide the information, but a lot of folks seem convinced that the game is fundamentally broken, that it's impossible to proceed past the tutorial for anyone, when that is clearly not the case - these folks are doing something specific, especially if it's happening multiple times in a row.
That could be hardware configuration, other software installed, performance (I saw a lot of folks saying that if they rendered at over 60FPS it would break the game) - but just saying you're experiencing it without providing any information doesn't help the devs fix it, nor does it help other people avoid the issue.
Part of the reason I'm asking is to help troubleshoot - I love this game, I'd love to see other people love it, and it's sad to see folks give up before they've even experienced it.
But you said you weren't a dev.
This bug needs to be corrected by the dev. There appears to be no fix for the bug in-game as of the current build. People aren't going to proactively look for bugs in discussion forums, they are coming here AFTER encountering the bug. Steps to reproduce the bug are moot.
If the bug isn't fixed by the dev, then there is no way to proceed unless one restarts the game. This is really just very bad form from the devs. They know the bug exists (they've commented) and yet, the bug is still there. People playing the game for the first time may encounter the bug and may or may not replay the game. At the very least, it will leave a very bad taste in one's mouth toward the developer.
Unless you are a dev and need precise steps to reproduce the bug, I don't see what good it is for us to go to a lot of work to help you reproduce the incident.
The game is fundamentally broken for everyone who has reported the game breaking bug. I'm still unsure why you feel the need to shill for the devs who haven't bother to correct the problem. It looks like a great game, I loved the 30 minutes I played...until I could not progress forward. I have a ton of stuff to play, why would I spend my time on a game (or dev) that clearly doesn't respect my time?
The game is broken in the tutorial for many people and it IS impossible for many to continue on. This isn't going to be fixed until the dev fixes it and there is no indication they want to fix it. People can't "avoid" the issue until they've experienced it. Then they come here, see that the devs haven't fixed a known issue yet and leave a comment saying this is a crappy situation. Sure, you can glean some tips on how to avoid the issue in the future, but the underlying problem and frustration isn't corrected.
I applaud your attempt to save the game's reputation, but this is clearly in the devs hands to save their rep.