OpenTS3
DevlogsPre-alpha Release preparation
← All devlogs

Devlog 01 - Internal Organization Changes

An update on what's been going on behind the scenes the past couple weeks.

  • Team Updates

Hey everyone, JJ here. I know it’s been a minute since I went live, and I want to say a massive thank you to everybody who’s stuck around. If you’ve hung out in chat, sent a video to a friend, or just popped back in every now and then to see how far we’ve gotten, seriously, thank you. One of my favorite things about all of this has been finding out how many of you still love The Sims 3 as much as I do.

What started as a weekend “what if” eight months ago has turned into a full production with a team of incredibly talented people. It’s been a labor of love for me this whole time, and seeing what everybody’s brought to it has been so cool. As the team’s grown, we’ve started sharing the work of leading the project, too. I’m still here, I’m still part of the team, and you’ll still see me making videos and hopping on stream when I’ve got something fun to show you.

And somehow we’re getting into the last leg of development, (which feels a little crazy to say out loud!) We’ll share a release date when we’re ready. Everybody on this team is doing this in their spare time, and I want us to have the room to get it right. I really do think it’ll be worth the wait. I can’t wait to put OpenTS3 in your hands and see what you do with it.

The funny thing is, OpenTS3 was my first Game Lab project, and that first OpenTS3 video was the first Game Lab video on the channel. It feels like we’re just getting started. I’m excited to see where OpenTS3 goes, to show you some of my own little projects, and to see what everybody on this team makes next. A few of us might already have something in the works. 😉

I’ve wanted to keep you in the loop from day one, all the way through getting the game out to you and putting the source up on GitHub. That’s why we’re doing these devlogs. You’ll get to hear straight from the people building OpenTS3 and see what goes into it between streams.

Thanks again for being here. I’ll hand it over to Peribelle to tell you what we’ve been up to.

-JJ

Hello, hello~ Peribelle here! I'll get to why it's me that's writing this section in a bit, as I'm sure you're all much more curious on the lack of visible progress lately. As the exciting work of adding new expansions and worlds has slowed down, video content has become a lot less frequent. We've been focusing on strengthening the foundations of OpenTS3, as well as creating new organizational systems internally.

In May, this project had a team of 4: JJ, Win, Amber, and Nicolas. October not only brought massive changes to the game, mainly all of live mode, but also 6 new members to the team. This allowed for great progress to be made in a short amount of time, but also made it difficult to coordinate with each other within the existing organizational system.

If October was the month of rapid growth, November is the month where we slow down and focus more on stabilizing the core of OpenTS3. This requires more technical knowledge and people coordination than one person is able to provide, so we had a meeting on the 14th, which resulted in the birth of ✨teams✨. This meeting helped us all get back on the same page and produced a shift in roles to better accommodate the growing needs of the project.

Let's start with the teams.

Audio

audio-icon This is the team in charge of making sure audio triggers when it's called and does so without delay, loss of quality, and artifacting.

Construction

construction-icon This team ensures that things in the world look right and act the way you expect. Foundations, walls, floors, doors, interactions with each other and the terrain. Construction is in charge of these tasks.

Performance

performance-icon This team finds optimizations throughout the codebase to eliminate stutters and increase fps. We want OpenTS3 to run well on your computer, so this is a big focus in development right now.

Persistence

persistence-icon This team makes sure the game remembers things it should. Sim state, relationships, items, career progress, all the things stored in your save file. The Sims 3 is a complicated game and has many transitions where we could potentially lose track of these things. This team's job is to find where OpenTS3 is losing track of state it shouldn't.

Rendering

rendering-icon Lighting, shaders, textures, models, all the visual goodies of the game lie in Rendering. This team makes sure everything looks the way you'd expect.

Simulation & Routing

simulation-and-routing-icon Autonomy, Story Progression, and Routing are all heavily intertwined in the game's code. Animation handling, transitions between actions, and getting from point A to point B rely heavily on that same heavily entangled code as well. It's this team's responsibility to work out the kinks in that behavior.

Modding

modding-icon This is the fun team, and the one almost everyone has a hand in so far. New lighting system hooks, new rendering system hooks, increased CAW capabilities, complete UI and audio replacement hooks, and the mod routing layer that handles conflicting mods, a mod settings spec, mod tools for CC, and an api for modders to be able to make more kinds of mods without having to do engine surgery. This is the team that needs a stable foundation to build on, or the whole thing collapses.

Launcher

launcher-icon No less valuable than a functioning and moddable game is the team behind an easy launcher to manage your saves, sims, and mods. It keeps your game up to date and keeps you out of file explorer wrangling files.

Website

website-icon This is the team behind this website! While it doesn't directly impact OpenTS3's development, this team helps build the functionality to be more transparent with you guys. You deserve to know what we're working on even when we don't have anything visible to stream.

These are our starting nine teams. As development progresses and we uncover new areas that need focused work, new teams will emerge and people will shift between them. Each team has a team lead and a backup lead who serve as the "experts" of that domain, so that we know who to coordinate with across teams and share the responsibility load, reducing single points of failure in the future.

In addition to the team leads, we've also reassessed our available time and capabilities for leading the project itself. JJ did an amazing job assembling the team we have now and getting OpenTS3 to the place it is today. This leadership change was made communally, with JJ willingly stepping down as Project Lead to take on a more promotional role instead. He is still involved with the project and plans to continue making content about it. We are all still on very good terms with each other and there are no hard feelings about the change in project leadership.

So if JJ's not Project Lead anymore, who is?

Great question, heading! The answer is, it's complicated, and it fits into the ethos behind OpenTS3.

OpenTS3 has always been for the people, worked on by a collective. While JJ started it as a weekend solo project, it quickly grew to be the fruit of a whole team. No one single person owns and controls the direction of the project. It is ours to develop and get it to the finish line, where the source will be opened, and it will truly become the community's.

So, no one single person is the Project Lead anymore. That term comes from the corporate world where there's a product with a deadline and a paid team who work on it full time. Given we're a team of unpaid volunteers who work on this project in our spare time, the same structures that work in the corporate world don't necessarily translate to this project 1 to 1.

That isn't to say that no one is fulfilling the traditional responsibilities of a Project Lead, though. The internal responsibilities fall into two main domains.

  • The Tech Side: Knowing how the project works internally and being an experienced enough developer to create a roadmap of where things should go from a technical viewpoint
  • The People Side: Knowing the specialties, desires, and bandwidths of individual team members and how to match those realities with the current work that needs to get done

Both sides are critical to get right. Get the people side right without the technical guidance and you have a buggy codebase with missing critical features. Inverse that, only getting the tech side right and you have an unhappy team and an unfair distribution of work. That isn't to say those are the only responsibilities of a Project Lead, though. Two other essential facets are:

  • The Organizational Side: Creating and maintaining systems so team members can easily pick up and find work when they have spare time, as well as managing communications amongst team members and coordinating meetings when possible
  • The Communications Side: Keeping those following the project in the loop on where development is headed, answering community questions, and being as transparent as possible on where the project is and where it's headed

The elimination of a designated leader has made it much easier for devs to speak up about things they want to implement, and the addition of teams has made it much more clear on who to speak to about what. We're still implementing workflow and internal communication improvements, as well as learning how to match people to work in the new structures. We wanted to prioritize transparency with everyone following the development of OpenTS3 and get this devlog out asap.

The People Stepping Up

This has been a week of sweeping changes, Or, more accurately, a very efficient use of a few days. While things are still in flux, I have seen a pattern emerging. Let me illustrate it with a chart.

Traditional Project Lead Responsibility Person Fulfilling Said Responsibility
Tech Alex, Tea
People Peribelle
Organization Maddie, Peribelle
Communications JJ, Peribelle, Maddie

Unshockingly, the 2 librarians on the team love to organize. Who could've seen that coming?

Currently, I've taken the lead on the people side of things and Alex has taken the lead on the tech side. We've been spending this week organizing the repo, our workflows, and how we coordinate with each other. Maddie has been an instrumental part in the organizational efforts, and the communications effort has largely been shared between JJ, Maddie, and I for a while now.

JJ makes the video content, and Maddie and I answer questions and post updates on the discord (which you should absolutely join btw). If you've been in the stream chat before, you've also met a number of the devs answering questions as well, such as Win and Fuyu. Tea you might not have heard of before, but his contributions to the team are best summarized by this image.

tea's-refactor-meme

Adapted by Peribelle from xkcd #2347, “Dependency” by Randall Munroe (CC BY-NC 2.5).

So yeah, Tea's kind of a big deal around here.

I know this likely wasn't the type of update most of you were hoping for. We don't have a release date set in stone yet, but rest assured we do have big plans for adding modding capabilities to the engine. Like the meme illustrates, though, all of those features are supported by the boring dirty work of creating sane, stable systems. As, unsurprisingly, AI is currently incapable of oneshotting a whole new engine for a 17 year old spaghetti game. This whole thing goes incredibly faster with the assistance of AI, but it still takes a boatload of human effort alongside it.

We plan to show you more of that human effort in a variety of formats going forward, rather than relying on videos and streams as our only modes of communication, as those are rather time and labor intensive to make. If you're the type to have read this far, you might be interested in the shiny new RSS feed for our devlogs, which you can subscribe to here. I know Maddie's planning on making a devlog of her own, and JJ's cooking up a Q&A video. Win is working on a website architecture overhaul which will hopefully allow for the addition of a github stats page so you can peek behind the curtain at your leisure.

Thank you all so much for following the development of OpenTS3. It's been an incredible experience working on this project and seeing all the joy and passion still present for this game. This community has gathered so many people in such a short time and interacting with all of you is the highlight of my day. We're going to work our damned hardest and do our best to meet your expectations.

- peri