1) Are we being
honest or are we being
nice? What kind of game? Was the game multiplayer focused or anything like that first? What's the assumed baseline game?
2) The kind of game where nothing changes when the servers are turned off.
3) Assume you design your game from the start with an EOL plan and that the executor wasn't washed out in the regular "wipe the board" that management likes to do to projects that are done.
4) Create a deployable server package such as a "dedicated server", which may be nothing more than a headless program that kiosks maps on rotation and can be configured via a script. Have alternate assets prepared for a debranding.
5) Embezzle funds from the upper management, use creative accounting to siphon funds from other less important departments, use a collective trashcan instead of many bins, ask an accountant; not a developer. That's not their area.
6) Legally or ethically?
7) Design the game up front to be able to run a local server that fits in a sane amount of space like...28 megabytes?
10) Depending on the game, this is simply adding more wheels to a car that runs fine already; redundancy might be fine for industrial design or biological function, but worthless for many applications.
11) So what, like using the same engine, codebase, or assets between projects? Maybe if your Jeff Vogel, but most devs don't even get the luxury.
12) Well duh. Even if it's a series of stationary targets, an infinite road, or what have you. I've known of an MMO that even did a server move, LIVE (they moved the players into a holding area.)
13) Shred them like classified documents. Anything less feels like IntSec and InfoSec nightmares. Hopefully they were airgapped in the first place.
15) Preferably, not needing specific code or compilation for a shutdown condition.
16) Introduce it as part of the opening documentation as a supplemental appendix in the manual.
17) Oh, simple. They won't. If it requires more than 3 clicks to setup, most people cannot nor will not bother. How many IPX, Serial or DECNET things do you know people to regularly bother with?
18) Then I guess your management screwed up. Though, it may be possible to untangle from that.
19) Then I guess your management team screwed up, hard. Who outside of them would hard bake missable events into the game?
20) IMPLICIT YES.
21) What do you mean "authoritative"? Once it is in the player's hands, be it to them to figure this out. I don't recall the designers of Unreal regularly showing up to private instagib servers and telling those players to knock it off. That or your game was designed poorly as a joke, well done bending to your management who seriously screwed up.
22) Have them be the same build, just throw a few compile flags or event flags down when EOL. KISS.
23) As much as can be legally provisioned. Next question.
24) If you're having to answer this question, try again. Either you're talking to management (a mistake) or your audience is unlearned to not know the difference between
hither and
thither.
25) Then it was either too big or designed wrong.
26) Automatic certificate renewal (just throw a 5 kb patch every once in a while), automatic anticheat updates (prompt em'), Skin/Emblem creator (don't worry, it wasn't long for this world anyways.), Play of the Game (worthless feature), awards/EXP (this encourages toxic behavior), etc.
27) Design your game to never use a managed backend; same as using a solution to a problem that didn't exist until someone invented it.
28) That's a funny way of saying, "Try running it without
X and see if it falls over". Stop spending so much time with marketing.
29) Obviously, you run one instance in airgap/airplane mode. This question is absurd.
30) Implicit Yes. See 20.
31) Hopefully that login service and DRM were external and not carefully weaved into the main executable. You did separate it into a launcher or something, right?
32)
SEE ABOVE, REDUNDANT QUESTION. 33) See 13.
34) Provide a dummy file, stub, or fake address.
35) Good jorb. Outside of acts of nature, there's not really a good excuse for this. Was your code poorly documented? Did you accidentally tie the BINK video to a critical function? How did you even reach this point?
36) See 24, but replace implications of distance with implications towards file sharing.
37) Then I hope you have a hex editor and a few free hours. 58 is X in hexadecimal. I understand that to be a fine way to blot out sensitive data.
38) Define "safe"?
39) A large clear message either in the main menu or upon opening would be generally the defacto standard, would it not?
40) How do you think Shareware worked?
41) Simple: As if it had never been part of the larger ecosystem. If it wasn't big or good enough to stand up on it's own, well done! We call those mini-games and put them in games for the Amiga or Amstrad, typically in packs of six with a loose theme or license tying them together.
42) Exactly one plank unit of time. Did you make the mistake of asking management again? As long as it is feasible unless you'd rather community host.
43) Didn't we discuss this earlier? Is this the part of the presentation where we make sure people were paying attention during the hour long meeting that could have been a 15 minute presentation?
44) With great care. Mostly by building them as separate ideas.
45) Labor, monetary, or time?
Amazing, 45 questions over an hour because they thought having two talking heads instead of just text would be a good idea.