Local meaning that it's on your personal machine, separate from systems accessed by connecting to a separate network like the internet.
I'm a programmer for a living and I'll tell you that the approach they took was the best one to accommodate all platforms. They didn't want to isolate people who might be picking up the game for the Xbone or PS4.
If I remember correctly, all ME:G did was create an artificial save file, which ME2 was already programmed to look. That save file only needed to be generated for PS3 players. Months later released that program to accommodate 360 and PC players
With DA:I and the Keep, they made it with all platforms in mind from the beginning. DA: I wasn't programmed with an "import local save file" function since 2 new consoles were released and those local saves would have no means to exist. Of course it's dangerous to assume that everyone has a means to connect to the internet, but logistically speaking, it's easier to program one function that uploads data from a single uniform source(Keep), than to program a multiple versions of a similar function for each individual platform the game is released on.. Doing it this way is also better for people who may jump between systems, so a single webservice can hold their data and keep it synchronized between platforms without having to manage them on each individual platform. It's very feasible to do it the way you're suggesting, but it's just inefficient.
I'm not talking about a save import. At all. Adding a single extra step in your character creation process, like setting Shepard's background and war history, wouldn't take much effort at all to add to the different versions. This wouldn't even need to use fake save files, it could just use the same process it uses to make a world state in the first place.
edited a sentence out, realized I'm getting dickish





Retour en haut







