quick note: I used to document quite a bit of my game dev process here on this blog. I started doing videos instead in the pandemic (patreon, youtube) because I was finding that drained less energy from me than writing a post. I haven't done either very much recently because I felt so much of what I wanted to talk about would just make more sense once the game was out so you'd know what I was referring to. Now it's out! I'll hopefully be doing some of those posts. I'm not sure yet what the balance of videos to writing will be, but this one's writing!
868-HACK is structured as a series of servers you hack one after another, with increasing difficulty as you go. Quite a few people never even saw the difficulty increase because you had to win a couple of rounds in a row to get there. When I did an expansion for it a few years later (PLAN.B) I wanted to put the difficulty modifiers up front - both so that everyone would see them, and because those of us who'd been playing a bit started to find the game a bit too easy without them. But sometimes a stack of them could just be unfair though so I wanted a way to skip the really bad combinations, and came up with the .QUIT prog. This is just a basic ability you can pick up and use like any other, and what it does is instantly win the round. Actually amazing. This would be blatantly S-tier if not for the opportunity cost: you don't want to take the free win if you could use that siphon to get more points instead.
.QUIT is one of my favourite progs because it's something that computers do but games don't. Coming to the sequel I really wanted to push as far as I could in that direction; try everything I could think of that felt like a "computer" ability and would fit naturally here and not in a typical fantasy game. So .QUIT and .UNDO were at the top of my list for returning progs. (Puzzle games should generally allow undo, strategy games don't because it creates a very boring play pattern around any random or hidden element; putting a cost on it that isn't undone solved that well enough for 868-HACK, but unfortunately wasn't enough to make it work in BACK.) .QUIT fit quite nicely into BACK overall, but the new scrip system made it fairly easy to minimise the opportunity cost.
One of my early ideas for a bonus powerup in 868-BACK was called Local area network!, which I) protected a server from being hacked unless you'd hacked one of its neighbours the day before, and II) forced you to hack one of its neighbors the next day. I really liked having a "map-only" powerup, making a server more difficult to hack not because the levels and enemies were any harder but simply because it was inconvenient to get and out of. I really liked the spatial element this gave to the server map: these little sequences where you had to move step-by-step across it rather than just picking from it like a menu. There were many problems with this. Does nothing on the last day. You could get stuck and lose the game with no options if you weren't careful - and that tended to feel unfair rather than like you'd excitingly hacked yourself into a corner. Didn't interact well with the "reveal powerups by gathering data in adjacent servers" mechanic. So eventually it went away.
Thinking about limitations that could be applied to QUIT to make it slightly less dominant - what about an effect on the server map? I thought of folding in Isolated workstation!: if you quit a server you don't get to explore the ones next to it. Jake suggested folding in Local area network! instead: if you quit a server you have to go to one next to it tomorrow. This was really good! We kept Isolated as the map-only powerup (its device restriction was added much later at Leon's suggestion to prevent it doing less the more of the map is explored). When Linkcubes were added I let it go along those links as well. It seemed like the problem was solved.
Since the game's been released and a lot more people have been playing it, a few rare bugs showed up involving QUIT. This is going to happen - different people have different skills and approaches, so they'll try something in a different situation - or else just the dice get rolled a lot more times so an arrangement comes up that you never saw before. I'd added certain types of server that couldn't be accessed unless specific conditions were met - the megacorp x6s and the shops. In particular this restriction on the shops came very late in development (to stop new players from having a disappointing experience of going to a shop where they can't afford to buy anything). So a few people had been able to quit with only a shop in range but then weren't able to get into the shop! When I dug in to fix this I realised that QUIT was getting quite complicated. We'd already had a few players being confused about when they could or couldn't quit, and this was making it more confusing by adding situations where your ability to quit depended on the status of servers you haven't even explored yet. So rather than add all those complications I gutted it and made the whole thing much simpler: you can always quit, and tomorrow you can go wherever is nearest that you can get into. If you're surrounded by locked shops and corporate headquarters, instead of being sad and stuck you just get to go slightly further. It should play pretty similarly in most cases, but be clearer to understand, less prone to bugs, and maybe even occasionally exploitable in clever ways.
patch is up now!
No comments:
Post a Comment