View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0028437 | Heart Of The Machine | Suggestion | May 26, 2024 7:10 pm | May 27, 2024 9:40 pm | |
| Reporter | B | Assigned To | Chris_McElligottPark | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 0.523 The Sunday Testers | ||||
| Fixed in Version | 0.525 So Much Clarity | ||||
| Summary | 0028437: Railroaded to murder - alternative options to the first rebel. | ||||
| Description | I didn't want to kill the first rebel, I wanted to provide them with the information they sought as a peaceful way to get them on my side (maybe) and resolve that part of the game. But I was 'forced' to kill. This especially stung because the game just told me that I get to make al the choices. Maybe the promise of freedom of choice should be delivered AFTER the rebel is killed. | ||||
| Tags | No tags attached. | ||||
|
|
You're not forced to kill him, though. The game says the upcoming fight will be easier if you do, but you can kill the investigators yourself, without attacking the rebel at all, and that way they survive |
|
|
Can you explain which part implied that you had to kill him? This may be a good point to clarify in future. |
|
|
Agreed, if there's something that would help clarify that you don't have to kill the rebel, that would be great. You cannot speak to the rebel after the first time you speak to them. The first time you speak to them, they make it really clear they have no interest in talking to you. So after that, it's like "well, if I wanted to kill them, that would get a response. Or I can ignore them." |
|
|
You are correct that you're not forced to kill the rebel, but it felt that way on first playthrough. I think it was a combination of struggling with the UI, struggling with finding information on what to do next, and struggling with finding things on the overworld. And then the second prompt when interacting with the rebel talks about killing them. Example: the game clearly states that notifications are on the bottom right, but doesn't tell you that objectives are on the top right. So after interacting with the rebel, and being told to consider killing them, the player is left without a sense of what to do next. Until they happen to spot objectives on the top right - which (in sunday's build) were ordered out of order. The frustration makes it feel like I need to kill this rebel to get back to the freedom of choice promise. Then the very next thing to do is equip slayer ability - and in sunday's version of the game the objectives would now state: kill investigators, kill rebel, find more bots So a lot of it wasn't clear. In today's version of the game the objectives are more sensible, though I still don't get why I must equip slayer then find more bots. If the intention is to kill some humans keep me on that path, if the intention is to find more bots put me on that path. Mixed messaging here made for not a fun time. Ultimately I think removing the text about considering killing the rebel, just have them not want to talk to you. Then tell the player to go find more bots, now talk about slayer and killing people for reasons, would make for a smoother process. |
|
|
Well -- it's trying to give you options. And this is also how you learn about the inventory at all. So removing that won't work. But basically, making the messaging more clear of "hey, you could go one of two ways here" is perhaps something that needs to be made more explicit. I do see the point that equipping slayer ability, with no additional context, implies you need to use it. So making it really explicit that you really don't, but you want to consider the option, is I think a good thing to do. |
|
|
Thanks! * Did further updates to the "equip slayer ability" part of the prologue, both in the tooltip in the upper right, and the at-mouse tooltip. ** It makes it really clear that you do have to learn how to equip it, but you don't have to actually use it. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| May 26, 2024 7:10 pm | B | New Issue | |
| May 26, 2024 8:34 pm | Alias50 | Note Added: 0068722 | |
| May 26, 2024 8:35 pm | Alias50 | Note Added: 0068723 | |
| May 26, 2024 9:16 pm | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| May 26, 2024 9:16 pm | Chris_McElligottPark | Status | new => feedback |
| May 26, 2024 9:16 pm | Chris_McElligottPark | Note Added: 0068728 | |
| May 27, 2024 9:21 am | B | Note Added: 0068736 | |
| May 27, 2024 10:55 am | Chris_McElligottPark | Status | feedback => confirmed |
| May 27, 2024 10:55 am | Chris_McElligottPark | Note Added: 0068742 | |
| May 27, 2024 9:40 pm | Chris_McElligottPark | Status | confirmed => resolved |
| May 27, 2024 9:40 pm | Chris_McElligottPark | Resolution | open => fixed |
| May 27, 2024 9:40 pm | Chris_McElligottPark | Fixed in Version | => 0.525 So Much Clarity |
| May 27, 2024 9:40 pm | Chris_McElligottPark | Note Added: 0068775 |
