The WordPiper of DirtPiper

Don't take anything I say here as gospel - much of it is my own speculation and musings.

TF2 is my favorite game of all time. I started playing it wayyy back in 2012, and while I don't have that many hours racked up total (a meager ~1K), I can at least consider myself to be a few rungs above 'total n00b' in terms of familiarity with the game. I've experienced the best and worst eras of the game - from the Love & War update to the current botting crisis, and I have loved TF2 every step of the way.

But just because I love it, doesn't mean I think it's flawless!

Around 2015-2016 I noticed (alongside damn near everyone else playing TF2) that TF2 was changing, and not in a particularly good way. Love & War was in many ways a perfect update for TF2 - it gave attention and goodies to both the highly casual and the highly competitive ends of the playerbase, with a fancy new taunt system bundled with some pretty fun new weapons. At about this time, Blizzard announced the imminent release of their new game Overwatch, which was directly inspired by TF2 - and now presented itself as being a direct competitor to TF2 in its own niche. This, of course, turned out to be bogus - Overwatch is its own game with its own niche that has a playerbase nearly wholly separate from TF2's.

A common trend amongst the TF2 playerbase at the time was this sense of dread regarding Overwatch - either that it would suck up the entire TF2 playerbase, leaving the game to die, or that Blizzard would try their damnedest to manifest such a reality. Either way, a ton of die-hard TF2 fans began to absolutely loathe Blizzard's new game (before it even came out, I might add) for so much as daring to 'unthrone' TF2.

This entire premise is stupid. It's stupid now, and it was stupid then. But the fear became so pervasive throughout the community that, eventually, it seemed like VALVe was getting scared too. The tone and focus of TF2's updates began to shift far more heavily towards the competitive end of TF2's playerbase - which has never been the majority - as VALVe appeared to try to pivot TF2 into a stance where it could better "compete" with the upcoming Overwatch. Bits and pieces of this started showing with Gun Mettle and Tough Break, before Meet your Match completely revamped the game into a more competitive-focused format.

Why they would do this didn't really make sense - if VALVe wanted to compete against Blizzard's new AAA FPS with a competitive scene, then why would they try to remodel TF2 to position it as a "more valid competitor" to Overwatch when CS:GO was already a proven champion in that space? TF2 doesn't need to compete with Overwatch. It never did. So why would they expend so much effort to change TF2's course when, frankly, it was doing fine as-is?

Looking back now, with nearly a decade of hindsight and a bit more insight into VALVe actually works, I think the picture is a bit clearer, or at least the one I've formed in my head is. I don't think TF2's sudden drastic shift in focus was the result of VALVe scrambling to shore TF2 up against the onslaught of Overwatch - I think it was, rather, the TF2 team scrambling to shore TF2 up against VALVe.

VALVe is not a normal game studio. VALVe is not only lucky enough to be their own publisher (therefore making them a completely independent studio - yes, VALVe games are 'indie'), but also extremely lucky enough to be the de-facto publisher for nearly the entire PC game industry, thanks to Steam. VALVe makes money off of every single game sold through Steam whether they made it or not, essentially guaranteeing them a constant stream of exorbitant income regardless of their own output. They have a complete vertical monopoly of their own industry - they own themselves (VALVe has no shareholders whatsoever), they own their products, they own their publisher, they own their distributor - and now, with the Steam Deck, they own their hardware platforms too. VALVe answers to nobody but themselves, because they own everything that could possibly impact their business.

VALVe is, in a lot of ways, in a somewhat similar situation to AT&T (aka 'Ma Bell') back before the breakup of the phone company back in 1982. AT&T owned the entire phone network - from the switching equipment to the phone lines to the handsets plugged into them - and they charged every person in the country who leased phone service from them (you couldn't own a phone back then!) a subscription fee. AT&T, then, had basically infinite money to do whatever the hell they wanted with (though the government strictly regulated their commercial activities so they could not compete in any industry but telephony). As a result of this, Bell labs, the core Research & Development branch of AT&T, was in a very unique scenario - projects undertaken by Bell labs researchers weren't given budgets - they were given quotas.

AT&T didn't care how much money or time was spent on a project by a Bell labs researcher, so long as it ultimately resulted in something that benefited the company. And this model worked very, very well - Bell labs' researchers gave the world the transistor, the laser, the CCD, the Unix operating system, the C programming language, and received 10 Nobel peace prizes.

VALVe, through Steam, has a free, infinite revenue stream. VALVe's staff, then, effectively have infinite money and time at their disposal to make whatever they desire - so long as it ultimately results in something that benefits VALVe. Or, at least, so long as the people who hold the most seniority at VALVe think it would benefit VALVe.

It's no particular secret that the old guard at VALVe are, largely, unenthusiastic about TF2. Remember - Team Fortress is VALVe's oldest franchise. The original Team Fortress mod was released in August of 1996 - a mere one month after the Nintendo 64's initial release - a full 2 years before Half-life. Sure, VALVe didn't initially create Team Fortress, but they bought Team Fortress Software for a reason - Team Fortress was insanely popular. And it's not just TF2 that has absurd longevity, it's the entire Team Fortress franchise; here's a match from a Quake Team Fortress competitive tournament that is currently ongoing as I write this post:

VALVe acquired Team Fortress software with the premise that the sequel to Team Fortress would become an expansion to Half-life, thereby increasing Half-life's desirability by attaching it to the sequel of one of the most popular FPS games available at the time. TF2, of course, took a bit longer than expected - so Team Fortress Classic, a more-or-less direct port of Team Fortress to goldsrc, was released in 1999 to satiate people until the real TF2 came out.

That took another 8 years.

When TF2 finally released, it pioneered the concept of games as a service - that you could buy a game once and it would receive new content, features, fixes, etc. indefinitely - for free. These were not paid expansions or DLC, these were actual updates made directly to the game that anyone could get access to so long as they happened to own the game. And, once TF2 went free to play, the deal became even better. This model was utterly groundbreaking in 2007 - it's the standard for how most games operate today, sure, but only because TF2 proved how well it could work.

The issue, of course, is that VALVe was eternally working on TF2. By 2015, Team Fortress 2 had been in development in some form or another for 17 years. With this perspective, it seems understandable why some of the more senior members of VALVe would have grown sick of Team Fortress - they'd been doing or dealing with the same game for nearly 2 decades.

But, of course, newer hires at VALVe would have nowhere near the same level of fatigue - many of them were likely still very passionate about the game, and eager to continue its lifespan - but when the people who sign their paychecks and review their employee performances are sick and tired of hearing about Team Fortress, it becomes less and less attractive to pour effort into the game, no matter how much they may personally wish to.

Under these circumstances, the tonal shift TF2 experienced around the release of Overwatch appears more as an internal struggle - the remaining TF2 team trying desperately to prove to their seniors that TF2 was not yet ready to be phased out, that the game could modernize and remain relevant in the modern competitive gaming scene, that just because they were sick of TF2 didn't mean that everyone was.

So, they gambled. They bet TF2's future on a new revamp to adapt it to the then-modern world of competitive e-sports... and fumbled it pretty hard with Meet your Match.

The problem with the TF2 team's attempt to make TF2 more suited to the modern world of competitive gaming was that they seemed to overlook that, to the average non-competitive TF2 player, the game as it was was perfectly fine. Through Quickplay, any player could be automatically placed into a server matching their desired criteria and just... play. A server would stay on a given map for roughly 45 minutes (though players could vote to extend the map timer) regardless of how many rounds there were, meaning that everyone got the same amount of time to play the map regardless of how good or bad either team, as a whole, performed. This game players plenty of time to just... have fun playing TF2. There was no rush or hurry or incentive to play the game in any way other than how you wanted to.

This made TF2 very unique in the FPS world - the truest example of a "casual shooter". There were no ranks or rewards or incentives to play every day beyond random item drops and the enjoyment derived from simply playing the game itself.

The TF2 team's attempt to 'modernize' TF2 in Meet your Match effectively ruined this.

In addition to the introduction of a new, dedicated 6v6 competitive mode, Quickplay was replaced with 'Casual' - a matchmaking lite that tried to find a middle ground between the chaotic ad-hoc freedom of Quickplay and the more rigid, competitive structure of Competitive. It didn't work. Most TF2 players just wanted to play TF2 - casual forced them to stop and wait for the matchmaking system to find a server for them matching its desired criteria, stop and wait every other round for the server to change maps, stop and wait for matchmaking cooldowns to run out if they left a game in progress - so much time was spent stopping and waiting to play the game that hardly any was left to play the game itself. Yes, some of these problems have since been smoothed over, but Casual still forces the play to spend less time playing the game than Quickplay did. In my opinion, Casual, as it was released, could have been perfectly fine if Quickplay was kept alongside it. Instead, in one fell swoop, the way the vast majority of people played TF2 was effectively removed from the game.

In fairness to the TF2 team regarding this gamble, they were under enormous pressure - not just from a TF2 community growing increasingly paranoid about TF2's future due to the imagined threat of Overwatch - but also from the higher-ups at VALVe they were trying to convince.

However, the TF2 team snuck a back-up plan into Meet your Match - the Heavy vs. Pyro war. By outright promising a future major update (or perhaps two, even!), the TF2 team could at least insure that, no matter what their 'bosses' thought, they could justify their continued work on the game as fulfillment of a promise made to the community. And, if the new update was enough of a hit, it could perhaps inspire their 'bosses' to let TF2 continue to live on, at least for a little while.

So, the TF2 team pulled out all the stops for the next update. Jungle Inferno had an animated short, new maps, new weapons, entirely new features (ie. the contracker), it had a massive hype-spiraling 4-day-long update announcement, major weapon rebalances and overhauls - they clearly tried their damnedest to make the best TF2 update possible.

Whether or not the team managed to convince their superiors is unknowable. Jungle Inferno was followed by the fanfare-less Blue Moon update in early 2018, followed by radio silence. The TF2 team may very well have still been hard at work on the elusive Heavy update, but the double-whammy of the all-hands-on-deck push to get Half-life: Alyx finished and released immediately followed by the COVID pandemic likely reset whatever momentum or motivation the TF2 team had left.

This scenario, as described, is painful enough. From the outside, it appears as though VALVe had rebounded from Meet your Match, and was doing its best to improve the game in the wake of their own missteps, only to suddenly drop TF2 with zero explanation given. TF2 was left in a state of indefinite limbo with no clear outlook whatsoever on the future.

What made this infinitely worse is that VALVe had left the game in a state that wasn't just unfinished, it was broken.

TF2 has literally always had a botting problem. For the first span of the game's life, this generally manifested as idling/trading bots, but later on more and more bots began to appear that sought only to disrupt gameplay. Micspam, false votekicks, aimbotting, speedhacks, etc. - purely for the sake of irritating real players. Until Meet your Match, these cheating bots were relatively uncommon - real players could very easily either kick them from the game or simply join another server via Quickplay. Their impact on gameplay was no more than a minor, brief annoyance, and thus they were considered a non-issue.

Meet your Match's new Casual system, however, dramatically restricted the player's ability to hop to other servers when bots arose. Not only this, but the ability to switch teams at will was disabled on Casual servers, meaning it was now impossible to deal with bots on any team but your own (previously, if the other team was too slow to kick their own bots, it was possible to just wait for an opening on the other team, hop over, and call a votekick against the offending bot that would usually end up succeeding). Now, the disruption caused by a single bot was far more impactful than it had been before - because it was a far greater chore to either kick the bot or find a different server. Moreover, Casual outright incentivizes players to stick to the same server until the end - awarding them extra points the more they play, and nullifying any progress they've made towards a given contract that match if they leave before it ends. Players are thus, in effect, forced to play even when bots have made the game unenjoyable.

This resulted in a feedback loop - bots were now more irritating, so people complained about them more, so bot hosters hosted more bots, making them even more irritating - and that feedback loop has continued nearly unabated until modern day.

The TF2 community has been begging for an end to the botting problem for ages - and there have been genuine efforts from the TF2 team to try and fix the problem, but they have been too small and too infrequent to make much impact. And, to be frank, there is no way to effectively, permanently remove the bots. Attempting to keep any and all bots from the game would require enormous, constant effort from the TF2 team - something which is a very tall ask given VALVe's attitude towards the game for the past decade.

What can be done, however, is to simply make the bots less impactful. To let players more easily avoid them, to let players enjoy the game for longer so the bots are no longer such a nuisance, to let players have enough freedom in how they play that they are no longer forced to suffer through games with bots. It won't outright remove bots forever, but it will make them so much less of a nuisance that bot hosters will likely lose the incentive to bother with them. As soon as that happens, the feedback loop will be broken, and the botting issue will decline in severity as their potential impact on players' enjoyment of the game is neutered.

The simplest way to do this is to make Casual just as free as Quickplay was.

45 minute map timers, extensible by vote.

An Indefinite number of rounds per map.

Ad-hoc joining, leaving, and team switching.

Progress on contracts not erased by leaving mid-round.

These are not overwhelming changes. If anything, it's something of a return to form - not outright bringing back Quickplay, but making Casual into a suitable replacement for it - at long last.

And - most importantly - it's a one-time fix. It does not require an eternal arms race against bot hosters, nor a full return to frequent, massive content updates (though those would be nice).

One update to make TF2 more fun, to make the bots less impactful, and to give the game a better standing for the future.

One update to fix TF2.

I've been waiting to say this for a very, very long time:

1.1.12 is almost here.

...Kinda. It's nearly ready for playtesting. I've got one last feature to smooth over and then it'll go out to the testers for feedback. Once the testers are happy with it (and I'm happy with what the testers are happy with), then we'll test multiplayer for a bit - and then it's time for full release.

It's been a looooooong time since NSSS last got a major update - September of 2021, to be exact. Sure, there have been tweaks and patches since then, but even then it's been over a year since 1.1.11_111-1. NSSS has been at version 1.1.11 for three years now - about half as long as NSSS has existed, period.

I'd like to think of 1.1.12 as the beginning of a return to form - wayyy back when NSSS first started, Vulpovile and I were releasing updates once every two weeks. I doubt I can maintain that pace, but at the very least I can avoid any more multi-year update droughts.

I've already got ideas lined up for 1.1.13, 1.1.14, 1.1.15, etc... - many of which I've been daydreaming about for years! I really want to finally sit down and work on these ideas, and make them reality once and for all.

There's a couple other things I'm hoping to polish up. First off - the website. I put it up a few months ago but it's been sitting semi-finished for a while now. The other day I finally dug up my FTP login credentials to actually upload the NSSS multimc instance and server jar there so I could fix the broken download links in the original forum post. Sorry for letting them sit broken for so long - I was very busy with IRL work. I'm going to be fleshing the website out a bit more soon - maybe I'll even get the in-browser applet working!

The launcher is also getting renewed attention. I figured out Oauth a while ago (so you can actually log in to microsoft accounts with it - yippee!) but was struggling to deal with https connections in older versions of Java. I think I've figured out a solution that's workable, so the launcher should finally be ready soon - here's hoping!

Lastly, the forums. Yes, there are official NSSS forums - but the URL has been somewhat hidden for a while now. I've been having trouble getting the phpBB theming to look the way I like it - if anyone has any experience with phpBB themes, please reach out! The increasing futility of trying to present information on discord has made it clear to me that it's for the best if most NSSS-related discussion were to happen on an actual public-facing website rather than a glorified IRC chatroom. The discord will still exist - but it will no longer be forced to do the triple-duty of "information repository", "public forum", and "community chat".

Let's see how much of this I can get done before 2030...

With my Writer's block for NSSS cleared, I've taken some time to think about the path moving forward.

I really want to release more updates to NSSS, but, for now, that means putting a major, promised aspect of 1.1.12 on ice.

Seasons, and all the other goodies I've been cooking up for the next update, will still be coming. But the weather system will be put on hold, at least for a while.

Weather has been the last major part of 1.1.12 that I've been hung up on for a while now, and every time I try to finish the implementation I encounter some major bug that's a pain to quash and all the wind gets taken out of my sails. It's holding me back from finishing the rest of the update, and it's holding me back from starting work on other work that I want to do on NSSS.

So, what can you expect?

Hopefully, more frequent teasers of what's still confirmed of 1.1.12 - Seasons, mostly, but there's a few more seecrets in there ;)

The weather system, particularly dynamic weather, is still a major part of my vision for the future of NSSS - it will still, absolutely, come, but it will be in its own, smaller update, not bundled in with a smorgasbord of other goodies.

Once 1.1.12 is out - which may be a while yet - then 1.1.13 will be arriving much, much sooner. And 1.1.14, and 1.1.15 - and so on. I'd like to return NSSS to a more frequent update cycle - nowhere near has fast as 1.1.3 - 1.1.7, but fast enough that I can push an update, listen for feedback, and then fix or improve things with the next release. A little, often - like firing a steam locomotive.

Novelty is only fun for so long - I won't know for certain if the changes that I make are good ones until I can examine them in the long run. It seems that 1.1.11 ended off on good footing - people are still enjoying it 2 years later - but there's bugs and problems that have materialized over that time which really ought to be smoothed out. It's time to fix 1.1.11_111-1... and I'm all out of ones.

There are also going to be some changes to the patreon. Stuff like playtesting access will probably get removed as a tier perk - I'd like to generalize the patreon from "support my work on NSSS!" to just "support my work!", which will be NSSS in addition to other things. Whatever happens, anyone who has ever gotten a custom name color or cape or particle effect will keep it in perpetuity - they're meant to signify a 'thank you' for throwing money at me, after all! Every dollar, euro, pound, zloty, real, and lira is appreciated.

I need to tidy up the website a bit as well, and the forums are still an unusable mess - if someone knows phpbb theming inside and out and is willing to pitch in, let me know!

From NSSS, to be specific.

Previously, most of the delays and pauses in NSSS's development were caused by other responsibilities - college, work, health, etc.

However, while these things are still contributing somewhat to NSSS's slow development pace, there is a new (and pernicious) factor that has been preventing me from so much as opening eclipse to work on the game.

Writer's block.

For the longest time I didn't even know why I had it, or even that I had it. I would keep opening eclipse, loading up some class file that I knew needed tweaking, and just... stare. I knew, essentially, what I needed to do. I knew how I would do it. But, for some reason, I just didn't do it. After a while I couldn't even get to the point of opening eclipse anymore. I attributed this to general busy-ness - I volunteer a lot of man-hours to a computer history museum, and this eats up quite a bit of my free time.

But then, when I took breaks from the volunteer work, and had all the time I needed to dig in to NSSS, I still just... couldn't.

What made this most frustrating was that NSSS still constantly occupied my thoughts - what I'd change, what I'd add, how this should look, how that should sound, how the launcher should work, what will be in the update after the update after next - all the time. My head was constantly bursting with ideas, but I just couldn't find the motivation to actually make them materialize.

Maybe it was because 1.1.12 was in feature freeze, and I was still banging my head against the cloud logic... but that didn't explain nearly enough.

Anyways, a user who had been playing NSSS since it was barely even 6 months old had reached out to me several months ago about possibly making some original music for the game. We chatted a bit about the general feel/tone/instrumentation said music should have, and then parted ways. This was about 10 months ago.

Well, last week they shot me a DM with one of the tracks they had been working on. NSSS was at the very bottom of my mind that day, but I decided to listen to it anyways.

The song was perfect. It was melancholy, soothing, and exciting, it sounded just like "minecraft alpha", it felt familiar and yet brand new, and it was exactly what I felt NSSS should have. And, as I wrote out my full thoughts to them as feedback (I'll spare you the full 10 paragraphs I wrote), it finally clicked for me why I wanted to make NSSS in the first place.

Previously, I always thought I had wanted to make NSSS because I wanted to fulfill my childhood fantasies, or to make a better minecraft than minecraft, or to polish the game as it was in 2010 and move it in a different direction.

But these are all closer to whats than whys.

Imagine returning to your family home and walking into your room and seeing it, not the way you left it, but exactly as it was when you were in elementary school, and there are toys strewn about the floor that you didn't even remember you had until that instant when you saw them again, and everything that was going through your mind, every tiny short-term memory that was in your head that day - what you ate for lunch, what you had to do at school the next day, what time Spongebob was gonna be on - are all just dumped right into the front of your conscious mind as if they'd never left.

But you're an adult. You're a different person. You can look at these things with a different perspective, see things that kid you never possibly could have. And that's never happened before. Like you've been handed a key to your own memories and told "go wild."

The past has been made brand new again. These aren't just dusty old memories that bounce around in your head, slowly getting distorted and thinned out over time. It's the very context that made those memories in the first place, and you're free to keep going from there, knowing what you know now, being the person that you are now.

This, above everything else, is what I have always wanted from NSSS. It's the mentality that has driven me to be so interested in history, period - it's why I volunteer at the museum, it's why I spent nearly a decade of my life archiving media from a certain other block game, and it's why I insist on using antiquated, obsolete tech for what it was intended for, rather than just letting it sit on a shelf looking pretty. I want to make the past brand new again.

After all, 'the past' is just a funny name we use to refer to the parts of the present that have already happened. There's no reason why it can't happen all over again.

To some extent, this is not an uncommon view - the term 'Nostalgia' exists for a reason. But 'Nostalgia', in my opinion, has the connotation of a biased, selective view of the past. It cherry-picks bits and pieces, either because they were remembered more positively, or because they are cheaper or easier to reproduce. A P.T. Cruiser may have 'vintage-y' styling, but it does not make the past brand new - it's too distorted and half-assed.

A few weeks ago I was hanging out with some friends when someone pointed out that Good Burger had gotten a sequel. I had never seen the original before, so we all watched it. Despite having never seen the film, everything about it - the set design, the acting, the fashion, the soundtrack - were extremely familiar to me, as though I had seen it a hundred thousand times before, but it was still brand new to me. And I enjoyed it! It was a goofy, somewhat contrived 90's movie with an only-somewhat-leaky plot and memorable characters.

Then, immediately after, we watched Good Burger 2 and I felt almost nothing. Part of that was because I frankly thought the film kinda sucked - the lessons Dexter learnt in the first film having been ultimately forgotten served to detract from his original character arc, for one - but the original movie was no paragon of writing either, so why did it get such a free pass from me?

Good Burger, despite my never having seen it before, managed to still seem familiar to me because, as a movie made in 1997, it had all the key qualities to slot right in as a movie I plausibly could have watched hundreds of times as a child. Good Burger 2, though clearly intended to capitalize on the 'nostalgia' that other people my age would have had for the original, completely missed the ball in that regard. It was no longer familiar, and thus, every other flaw in the writing, plot, etc. no longer got a free pass from me. It was no longer a 1997 movie with a 1997 movie's plot, it was a 2022 movie with half of a 1997 movie's plot and half of a 2022 movie's plot - it was half-assed. It, like a P.T. Cruiser, couldn't decide whether to be from the past or from the present and ended up in a weird, uncanny worst-of-both-worlds.

I've always been keen to be true to the historical context of whatever historic artifact I'm using - whether it be a typewriter, SGI workstation, palm pilot, or, in NSSS's case, an indie game from 2010 written in Java. It's why I develop NSSS using period tools and constraints - I use an old version of eclipse, maintain strict compliance with Java 5 (which came out in 2004), optimize the game for hardware that is now 20+ years old, built the entire website in .jsp, modeled the wiki after minepedia as it was in September of 2010, etc.

Because I'm not just doing this all to nostalgia-trip, I'm doing this to drag the past back into the present for us all to experience again. It's not going to be exactly as it was in 2010 - I do still want NSSS to be its own thing beyond just minecraft alpha 1.1.2_01 with bugfixes and QoL improvements - but it will be both familiar and new. It will have been made exactly as it would (and could) have been made back in 2010. And you can sit down and play it, and feel just as you did 14 years ago, not just in that you're playing the game as it was back then, but that you're playing a new game just as it was new back then.

As I put it in the discord server last year:

"I want to see someone who first played minecraft 13 years ago, back when they were young and wide-eyed and had never seen a game like it before, someone who got addicted and spent a solid week doing nothing but eat sleep & play, someone who almost pissed themself with fear the first time they got eviscerated by a creeper, someone who woke up their parents in the middle of the night shouting with glee when they found their first diamond, someone who fell in love with the game as it was then and stuck with it as it grew with them, changing and evolving and morphing just as they did, through beta and release and their highschool graduation and their first car and the combat update and the nether update and their first apartment when they finally let minecraft sit dormant on their PC for over a year, when they just lost the last remnants of the spark they had, and they don't even care enough to know why they fell out of love -

I want that person to play NSSS, shake off the cobwebs in their brain as they try to pull out the memories that have become faded and warped with time, just enough that they've forgotten just what this game did to them when they were younger, just enough that they expect the same old experience that they've grown more and more unenthused about over the years -

And I want them to get eviscerated by a creeper for the first time in 8 years and fucking shit their pants."

The last patch to NSSS came out 3 months ago, and the last major update - 1.1.11 - nearly 2 years ago. Where the hell is 1.1.12? Or the new launcher? Or the website, the wiki, the forums, and trailers???

Let’s tackle these one-by-one:

1.1.12

This is the single most ambitious update NSSS has ever had, which is saying a lot since 1.1.11 was also a ‘most ambitious update NSSS has ever had’. But it’s true! The two main features of this update - weather and seasons - have both required a ton a work in both design and implementation to make a reality. Seasons are now pretty much done, but weather is proving to still be an irritant. A large portion of that is due to how I’ve decided to implement it - based directly off of an ancient post to r/Minecraft by AbouBenAdhem suggesting a dynamic cloud system as opposed to Minecraft’s static bitmap. Notch thought the idea was wicked cool - and I do as well - but ended up passing it by.

When he did finally implement weather in Beta 1.5, it was a somewhat rudimentary system where the entire world would experience the same weather at the same time - if it was precipitating in one place, it was precipitating everywhere. The weather itself is also fairly boring - rain doesn’t sound particularly interesting (the sound effect is essentially just white noise), and the most gameplay-effecting phenomenon is thunderstorms, which (just barely) make the surface dark enough for hostile mobs to spawn during the day and can spawn lightning bolts, which can start fires. The challenge of thunderstorms is, of course, made totally moot by the fact that the player can skip them using a bed.

I don’t like the weather system we ended up with, and to my knowledge that’s a fairly common perspective. “Better weather” mods have existed for Minecraft since weather itself, but the design angle I have always thought had the most potential gameplay value was to couple it to a dynamic cloud system much like the one AbouBenAdheim had suggested back in 2010 - where the weather could be just as interesting as the infinite, procedural world itself.

A good portion of the delay in finishing this new weather system is the amount of times I have gone back to the drawing board. An attempt might end up being too slow, or too janky, or not interesting enough, or just flat-out doesn’t work. It’s been a major effort trying to get a system like this to fit neatly into Minecraft’s existing codebase and structure - a fair amount of shimming and shaving has been needed, though thankfully with each failed attempt some more useful shims have been added to make the next attempt a bit smoother. I believe I’m currently on implementation number 5.

But the biggest portion of the delay has been life. I can’t really afford to work on NSSS full-time (though I wish I could!) - the money I’m making off of patreon, while deeply appreciated, isn’t quite enough for me to be able to justify pouring all my time into this. And even if I could, I’ve been consistently interrupted by various health emergencies - in the past year alone I’ve had  to deal with bone bruises on both my feet, COVID, Appendicitis, and C. Diff. Aside from the health emergencies, I have other obligations - I work as a museum docent/restorer, a martial arts instructor, and I have tons of other projects that command various quantities of my time. Life is also responsible to a large degree for all of the other following delays:

New Launcher

The last update to the official NSSS launcher came out so long ago that I don’t even care enough to check - 3 years ago? Maybe even 4 by now? It was so long now that the Microsoft account migration was announced, began, and ended during the timespan since the last update. With the end of Mojang accounts, it is no longer even possible to log in with the old launcher. As such, I’ve been hacking away at adding support for Microsoft accounts to the new launcher using Oauth, which has been nothing short of a nightmare.

The actual documentation on interfacing with this API is fairly comprehensive, but the problem lays in the encryption side of things. Pretty much half the point of the NSSS launcher is to be able to run the game on legacy operating systems - operating systems that are so old that no other launcher available today will run on them, despite Minecraft itself having been available on them back in the day. A large part of this is down to Java’s security support - the oldest version of Java that any version of Minecraft (every version up to release 1.8 or so, really) will run on is Java 5, which will run on Windows 9x, OS X 10.4, Solaris, etc. - but Java 5 lacks support for TLSv1.3 encryption, which is what Microsoft’s API absolutely totally 100% requires you to use if you want to interact with it. The oldest version of Java that natively supports TLSv1.3 is Java 8, which, while it still has fairly wide OS support, does not have the same legacy outreach as does Java 5.

So why not cram TLSv1.3 into Java 5?

Well, you can! Tons of companies are still maintaining massive, mission-critical codebases that they can’t easily update to modern versions of Java, so the need emerged for a third-party, pure Java library to handle more modern encryption methods - and thus one was made, called Bouncy Castle. Bouncy Castle does everything I need - the problem is I have no clue how to use it.

This is apparently a common problem - most of my google searches for “how do I do [X] with Bouncy Castle” turn up with results saying “you can, but there’s no documentation on how”. What I’m trying to do is so simple it baffles me how hard it is to get working - from what I have found this fix ought to be literally two lines of code to add the Bouncy Castle security provider to the list Java uses when making https connections, but so far nothing has been anywhere near that easy. I had briefly broken down and started using a proxy endpoint that Vulpovile wrote in PHP to strip all the encryption out of the GET and POST requests I was making, and I did manage to get logging in to work flawlessly with that system, but I scrapped it because it just felt too sketchy. The launcher will be released the instant I can figure this out - and if you do comprehend Bouncy Castle, then dear god please tell me what the hell to do.

The Website

This is mostly done, to be honest. I just need to get around to upgrading my hosting plan so I can set up Apache Tomcat. Once it’s up, you’ll see it here. Be wary that playing the game in-browser will take a while to be ready -  applets are not my forte.

The Wiki

This is getting there! I recruited some folks to help get the wiki set up based on archives of Minepedia as it was in September and October of 2010, with NSSS-specific features and fact-checking sprinkled throughout. Most of the block articles are done, and you can check out our progress here.

The Forums

These are a bit of a mess, at the moment. I’ve been wanting to set up a proper dedicated forum for NSSS for a while now - the discord server is not adequate as a centralized place for discussion, and discord honestly kinda sucks at things like distributing mods and world downloads and discussing basically anything more than one topic at a time. The forum will be phpBB, just like the original Minecraft one, though I am having difficulty in getting a theme set up that looks (and works) right. Once the forums are done then the discord server will still remain, albeit with far fewer channels - everything that is currently a ‘discord forum’ will get archived.

Now you’re all caught up! Stay tuned for some more ramblings here about game design and junk.

When I first found Minecraft I was roughly 10 years old.

I can’t precisely identify how I found it - through some kid at school, or a friend of my sister, or randomly on the internet - but I remember falling in love with it.

I loved the aesthetic, I loved the dopey Minecraft music parodies, I loved the let’s plays, I loved the classic multiplayer servers, I loved the dumb jokes the community made, but most of all - I loved the game itself. It was weird, beautiful, simple, terrifying, serene, and hilarious, all at the same time.

I spent hours not only playing the game itself, but also watching videos about it, reading forum and blog posts, and poring over the Minecraft wiki - my favorite articles of which were the ones regarding the removed, unused, and planned features - aspects of the game that I could know about but never experience for myself.

Over time the game I fell in love with started to fade away - the aesthetic changed as biomes were added (though not that much, and it still looked nice), the gameplay began to suffer (a fast travel hell dimension with nothing to do in it, beds that let you sidestep the entire challenge of the game), but it was still largely the game I loved.

After Beta 1.8, the game I loved ceased to exist.

Okay, that’s a bit too dramatic. I still played the hell out of the game during the early release era - but I notably stopped playing survival singleplayer altogether after Beta 1.8. Multiplayer in any game is fun, and the newly added creative mode gave me hours of mindless entertainment blowing things up with TNT and making useless redstone contraptions. But to a large extent I stopped playing the game itself - survival singleplayer - and every time I did I found myself having a very hard time enjoying it.

Now, kid me didn’t really know why I suddenly lost all interest in this game I loved - I could kinda grok that stuff like the new hunger system and terrain system were less than stellar (likely helped by the fact that everyone seemed to hate these two things at the time - the massive open letter to Mojang begging them to add beaches back to the terrain generator springs to mind), but the nitty gritty specifics of what exactly made the game less fun for me were not yet apparent.

Luckily for kid me, I managed to find something to help me alleviate the problem - Exalm’s OldDays mod. This mod allowed you to tweak Minecraft’s features to your own preferences, literally undoing changes from various updates on-the-fly to permit you to hand-tune your personal “perfect” version of Minecraft. I used it to tear out all the changes I didn’t like - gone were the biomes, hunger system, nether, sprinting, new terrain generator, stackable food, potions, enchanting system, etc. Now, suddenly, I could play (and enjoy) singleplayer survival again - and this was the ‘default’ way I played Minecraft up until the mod stopped getting updated in 2013, around release 1.6.4.

By this time a brand new Minecraft launcher had released which allowed you to (officially) go back and play previous versions of Minecraft - with OldDays gone, I picked the version of the game closest to my hand-crafted ideal and dove right in. Thus, the primary version of Minecraft that I played became Alpha 1.1.2_01.

Flash-forward 5 years to July 18th 2018, and I’m not a kid anymore. I’ve just graduated high school, and I’m on vacation with my family in Long Beach Island, New Jersey. It’s a rainy day, so I’m playing Minecraft on my laptop. By this point I had a singleplayer world with damn near everything a player could want in 2010 - an automatic cactus farm, a mob grinder, a minecart system, vast underground mines, an automatic boat dispenser, a hulking storage room - you name it. But deep within I felt a twinge, a feeling that something was missing. I don’t remember what originally set me off, whether it was being by the ocean, or the nascient release of the update aquatic, or a memory of Minecraft classic, but somehow I started getting a bit upset that sponges were unobtainable in the version of the game I was playing.

Very conveniently, I had taken a class on Java my junior year of high school.

I dug up an ancient version of the Mod Coder Pack for a1.1.2_01, decompiled Minecraft and started poking around the codebase. After a bit of digging, a realization slowly began to dawn on me - why stop at sponges? Why not fix more things? Like fix axes not breaking workbenches? Or redstone ore taking an eternity to mine? Or boats exploding when you sneeze on them? Or, better yet, fulfill my childhood fantasies by implementing all the removed/unused/unimplemented features I used to spend hours reading about on the minecraft wiki. Realizing I could use some guidance, I asked my friend Vulpovile (creator of Minecraft Classic Creative Revived) if he might like to help me out with my new project.

side note: I planned on adding the ambient loops a full two years before getting around to implementing them... and my method was essentially the same as what I schemed up on the first day. Most NSSS features bounce around my head for a year or two before I finally implement them.

We managed to get sponges done within a day, and banged out the rest of the little QoL fixes I wanted not too long after. Soon we began going haywire - adding singleplayer commands, trying to fix the outrageously janky alpha multiplayer, optimizing the game, making food stack, making trees drop apples, underwater dungeons, whatever we wanted to do, we did it. We had already numbered our new ‘fork’ of Minecraft as ‘Alpha v1.1.3’, but didn’t actually have a name for it - the original working title was “Minecraft Redone” - a very literal description of our goals, but not that catchy. After 4 days I finally coined the name.

By the 28th, our first release was out: Not So Seecret Saturday’s Minecraft Alpha v1.1.3. We ended up released one update every other week straight on into october - in 1.1.4 we tried to beat the server code further into submission, in 1.1.5 I reimplemented the score system from survival test and added floating worlds, in 1.1.6 I tried (and failed) to improve mob AI and made sponges redstone-sensitive, and in 1.1.7 we polished our work a bit and added two more world types. Then September hit and Vulpovile and I were sucked right back into college. During winter break we managed to release some more patches to 1.1.7, as well as 1.1.8 to add McRegion and running... before the first gap.

‘The gap’, as I’m dubbing it now, is a fairly common occurrence in NSSS development - it’s happened roughly 3.5 times now, and each time it’s the same thing:

Development on NSSS is interrupted by something IRL (at first this was always college, but now it’s health conditions and other boring responsibilities of being an adult. And a bit of depression.)

I don’t get right back to working on NSSS.

I spend a lot of time thinking about the then-current state of NSSS. A LOT of time.

The more I think, the more I determine needs to be done to NSSS before I’d be satisfied enough to do a new release.

Every time I open eclipse I either get so overwhelmed by the massive backlog of work that has to be done that I either only manage one tiny portion or I give up and do something else.

Steps 2-5 are repeated ad nauseum, until...

A sudden, miraculous wave of motivation occurs. I get everything I’ve been planning over the past [weeks/months/year(s)] done in the span of 2 weeks, release the update, and finally return to making semi-regular NSSS updates.

This routine is so predictable to me now that I can nearly time my watch to it. But that first gap after 1.1.8 was special - as I sat and thought about NSSS, and what I really wanted to do with it, my goal slowly shifted. At first I had just wanted to ‘fix’ Minecraft alpha by cramming a bunch of shiny toys and knick-knacks into it to satisfy my inner child, but now I wanted something... more. I didn’t just want to make a better alpha than alpha, I wanted to make a better Minecraft than Minecraft.

Let me preface this by divulging that I’m a massive fan of Team Fortress 2.

The development history of TF2 is utterly fascinating, and if you’re at all interested in game development I urge you greatly to play through the entire TF2 developer’s commentary, but the relevant parallel is this:

The original Team Fortress was a mod of quake made by a trio of Australian teenagers who went hog-wild with QuakeC, the super powerful Quake scripting language, to invent the class-based shooter in 1996. At first they were just adding things to have fun, but over time started paying more and more attention to the actual design and balance of the game they had created. Eventually, the entire team was hired by VALVe in ‘98, and after porting Team Fortress to GoldSrc as ‘Team Fortress Classic’, they got right to work on Team Fortress 2.

Team Fortress 2 didn’t release for another 9 years.

During that time, TF2 went through a multitude of totally different designs and ideas, at some points being nearly unrecognizable gameplay-wise to the original Team Fortress, until ultimately VALVe decided to stop trying to invent something wholly new and unknown and instead to improve on what they knew - and so they essentially rebuilt Team Fortress for the third time, now in the Source engine, and with a cartoon-ier art style. And then they started playtesting.

VALVe had learnt from making half-life that playtesting often and early is utterly invaluable as a tool to aide game design. After all - how do you know how something is gonna play until you’ve played it? And how will it play for people who are totally unexposed to it? A developer already knows all the game’s mechanics and how they work - how would a lay-person discover them all for themselves? Which mechanics would a normal player use in ways the developers never intended? There’s no way to find this stuff out until you hand your game off to a stranger and wait to see how they break it.

And so VALVe, through constant playtesting, tweaking, and fiddling, honed TF2′s design and gameplay to a point where, while not totally perfect, was absolutely better than the original Team Fortress. And aside from the new artstyle, the omission of grenades and bhopping, and the medic becoming... well, an actual medic, very little had changed of the core gameplay beyond little tweaks and nudges.

That’s what I wanted NSSS to become.

I wanted to make Minecraft into a better game than it already was through little tweaks and nudges - an adjustment here, a rebalance there, and a few new features where a gap exists to justify them.

During the first gap I did manage to release some moderate patches to 1.1.8, fixes for things like the busted FastRender port and proper textures for all the dye colors, as well as the first release of the NSSS launcher. But all of these were just tide-overs for what I really wanted.

In summer of 2020 the first gap-and-a-half concluded with the release of 1.1.9, which added Creative mode, Sponge Armor, and Ambient loops. All of these features were things I had spent years brainstorming, tweaking, and revising before I was finally happy with them - and when they finally released to the public... they were good. By now NSSS had started to accumulate some following, and the positive feedback to 1.1.9 was notable - it turns out that people like things that are carefully thought-out and designed! Two weeks later I released 1.1.10 to patch over some more things and finalize gold touch, and then I set my aim on the largest hulking problem NSSS has faced since day 1:

Multiplayer.

The original ‘legacy’ NSSS server was accidentally based off of a version of hMod for Alpha 1.1.2_01, but our problems with it would have occurred regardless; the Alpha server SUCKED. Within a day of poking around the code Vulpovile and I came to the conclusion that Notch had taken the Classic server and stapled infinite worlds onto it to create a horrible abomination.

Mobs would randomly turn invisible, Redstone would only work at certain Y levels, Doors would open halfway, you would randomly die of fall damage for no reason, you couldn’t eat food unless you were looking directly at the floor, if you checked a furnace while it was smelting something it’d break the timer and waste fuel, you could dupe items in chests by clicking on them fast enough, tools could be repaired by dropping them on the ground and picking them back up - it was a nightmare.

Vulpovile and I both, quite rightly, came to the conclusion around 1.1.8 that the legacy server was unworkable. We started trying to write our own , new server from scratch, but that went nowhere - too much of an uphill battle. Once 1.1.9 came along, I decided to do it ‘the easy way’ and just take a later version’s server and downgrade it to alpha - the winner was beta 1.7.3. I had hoped to finish by 1.1.10, but found myself in a deeper hole than I expected, so 1.1.10 was shipped with no multiplayer and I made 1.1.11 into the “fix multiplayer” release.

1.1.11 took over a year to finish.

God what a nightmare. It did not take me very much time to get simple interoperability between the NSSS client and the Beta server, but certain bugs quickly emerged as gordion knots: if someone sneaked they would crash all connected clients, opening a chest crashed the game, crafting recipes were one slot to the left, your armor would shift one slot down at random times, and vehicles were possessed by demons. The sheer amount of bugs I had to work through to get this update out was mind-boggling, to a point where I actually opened 1.1.11 up to a limited group of playtesters for several months before full release just for the sake of trying to eliminate every bug possible. Ultimately, the pre-planned release date of September 18th, 2021 (exactly eleven years after Alpha 1.1.1, the first seecret saturday) snuck up on me, and I panickedly released what I hoped was a relatively bug-free 1.1.11: it wasn’t! While multiplayer was far, far better than it had been in 1.1.9 and prior, singleplayer had become riddled with bugs, namely pertaining to inventories and creepers. I quashed most of them in later patches, but the armor shifting bug still isn’t totally fixed in multiplayer - if you die and relog without completely closing and reopening the game, your armor still shifts one slot down. I have no clue why the hell this happens.

Something that started happening during 1.1.11 that would foreshadow the next 2 years of NSSS’s development was a trend wherein I would gradually feel more and more trapped by the feature set of the update I was working on, and would increasingly wish I was working on the next update instead - this sucked for motivation and made 1.1.11 take even longer. That next update was going to be one that would add Seasons and Dynamic Weather to NSSS - an update which has been in progress for almost two years.

1.1.12 is still coming along, don’t worry, but I can guarantee you that once it’s out, I am never doing another massive, year-long-wait update for NSSS every again. Updates will return to being smaller and more frequent - the way it should be! Expect further ranting in a later post.