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
12 
Report this post
Main ring
map map_aquaponics_a
Zero-G section
map map_aquaponics_b
Command ring
map map_aquaponics_c
Ship boarded
map map_aquaponics_d
Escape
map map_aquaponics_e
Fortune's Run has a tutorial which doesn't allow you to save manually, but it autosaves frequently.
In the actual campaign, you get frequent autosaves, a quicksave/quickload function (with a neat 'rewind' visual effect) and you can save and load manually pretty much anywhere, at any time.
Please tell us if something isn't working so we can fix it!
Aaah. Well, there's not really meant to be an autosave system. You are meant to save manually throughout the entire game, as you used to be in most old shooters. The autosave on map start is mostly a technical thing. In the demo we actually had a message telling people not to forget pressing F5 - this time... we have forgotten to put the message... eh
But a lot of classic shooters had this feature, it's really not a new thing.
You're saying the map start autosave softlocked the game? Can you describe this a bit more? on which map? Would you be able to share the save file?
Edit: I'm real tired, and I do all the VA right now, so I won't be doing it promptly, but I plan to add a call from the Assistant where she reminds you to save if you haven't saved in a while. Hopefully this makes the design clearer.
Maybe we might add a thing where it autosaves at map terminals. Frankly it's just a little hard to figure out where the saves might go because the map is non-linear! We have some after bosses and things like that, but there's like 2 hours of content between them so it's not exactly meant to be relied on.
Oh come on! This person has purchased your game and is giving feedback, it may be due to user error it may be a bug in the auto-saves. Either way, you need to act appropriately.
A little bit of customer services advice. You can approach this by responding "thanks we will look into it" followed by "here is a helpful work-around (sugar coated - here is what you should be doing)." Like it or not people who pay for your product are your customer and they have a right to raise issues, complain, and dislike features.
Dev's Response looked appropriate to me, OP was calling it broken and bugged, so it's not entirely clear since it could just be name calling the intended features as bugs due to frustration. What's the point of saying "We'll take a look into it" if you're not sure your looking at the complaint correctly? Sounds more dismissive and disconnected if it was left at that.
I'm not sure how "It sounds like you just don't like games where you have to save manually" is appropriate, but cool, thanks for the input.
Bugs and features don't have feelings, describing this as "name calling" is bizarre, I take it you mean mislabelling? In either case responding to a paying customer's complaint with a belittling statement is not professional nor it is appropriate. We aren't in school here debating what our favourite Power Ranger is, this is a paying customer providing feedback.
Simple, the developer has not had time to investigate if this is a bug or not, they are assuming that OP doesn't know how to save a game. There is no way they could have done even the most basic check to verify either way. Secondly, if this isn't a bug and this is just the CUSTOMER ranting, then the developer could have phrased the response in such a way that accomplished two goals:
1. Provided a work-around to a problem which the paying customer is experiencing (maybe the designed way of doing things).
2. Defused the situation and reassured the paying customer that concerns are being met with professionalism and will be taken into consideration.
Maybe, just maybe, there is a bug or the feature does have room for improvement. I have not once in all my 20+ years in software development found a piece of software that was written perfectly on day one. Any claim to the contrary is deceitful or arrogant at best. This is based on an experienced developer's view, more times than I count have I been made to look the fool by claiming something works only to find an edge-case where it doesn't.
Either way, this response like many others from this developer is arrogant, emotionally charged, and quite frankly demeaning. I'm not sure of the details for the person in charge of posting on here, maybe they are young, maybe they are going through some stuff, who knows. What I do know is that you cannot act in this manner when you are charging people money for a product.
It's such a shame because OP kinda has a valid point; from a modern casual gamer perspective who has not played some old ass game from 1998, it makes no sense that it doesn't save automatically, and we probably should say that somewhere. In fact, we were supposed to, and I just literally forgot, and the VA is a big pain in the ass to do (I voice 4 people!) so we haven't had the chance to double back on it yet. I'm thinking of adding a message to Sigmar's conversation since he uses auto-generated audio.
Also, likewise, OP had something to learn here; quicksaving is required in games like immersive sims and retro shooters, sometimes. We both learned something. It should be a net positive, not some kind of traumatic emotional experience.