Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

GameMakers

GameMakers artwork

Your Discord Is Lying to You. Watch What Players Build.

Oct 22, 202654 minAudio
ShareXLinkedInFacebookWhatsAppEmail

I like to think about game development as product velocity, and velocity is a vector. It has a magnitude, which is how fast you build, and a direction, which is whether you’re building the right thing. AI is pushing the cost of building toward zero, so magnitude is becoming less of a problem. Direction is now the bottleneck. Knowing what to build is the hard part. The usual answer is "listen to your community." Studios are already great at that. They run Discords, read Reddit, watch Steam reviews and send surveys. The trouble is that most of this is listening to what players say, and I’ve written before about why stated preferences are such a weak signal. Some of the biggest ideas in games never came from a survey. They came from the community. MOBAs came out of a Warcraft III mod. DayZ came out of Arma 2. Auto Chess came out of a Dota 2 custom game. Players didn’t ask for those genres. They built them. So for this episode I wanted to talk to someone who sees what players actually do, at scale, before a studio does. Pedro Esparza is Head of Growth at Bisect Hosting. He has spent roughly 20 years on the business side of game servers: MC Pro Hosting (where, he says, they were the first to support Hypixel), Tebex, Overwolf, and now Bisect. In my words, he’s a landlord for tens of thousands of game communities. He watches them form, monetize and die, and he sees demand in raw numbers before the studio knows it exists. My claim: the best signal for what to build is what players are already paying for in time, money and effort, and a studio’s job is to make that behavior visible before it commits resources. Pedro’s framework is a practical way to do that. It comes in three parts: what counts as a signal, how to rank the signals, and the loop that turns a signal into a build, partner or leave-it-alone decision. One disclosure up front. Pedro’s company hosts dedicated servers, so he has a natural interest in studios supporting them. I don’t think that changes the framework, and you’ll see he argues against building multiplayer in plenty of cases. But you should know it. Part 1: Behavior beats opinion I opened by asking whether studios are doing enough to learn from their communities. Pedro didn’t hedge: "Are game studios doing enough? I think honestly the answer is no." He described two very different kinds of signal. On one side, a Discord channel might ask for multiplayer 500 or 1,000 times, and a community board might have a request with thousands of upvotes. On the other side: "If players take the time and effort to actually reverse engineer a game to take it further, like you mentioned with DayZ coming out of Arma 2, that to me is a much louder signal. They built multiplayer, they maintain it, they run the servers, they pay for all of this." His summary is the line I’d put on the wall of every community team: "Community behavior for me is more valuable than just opinion." Studios, in his words, are great at collecting opinions. What they should care about is revealed demand: where players are investing their time, their money and their technical effort. This lined up with something I found when I studied a set of recent PC and Steam hits last year (Lethal Company, Project Zomboid, No Man’s Sky, Phasmophobia, Schedule I and others). I saw three common traits: small teams (often under 20 people, sometimes one to three), strong community engagement, and long development cycles run with the community. Pedro agreed there’s a correlation, but he pushed back on the cause. Small teams and long development don’t create success by themselves. Plenty of studios of every size sit on a project too long. What matters is the length of the feedback loop between the players and the studio. His example was Schedule I. Tyler built it on his own, which meant no red tape: no path from community to product to leadership, back to product, onto the roadmap and then to engineering. At a larger company, a good request can lose all its momentum somewhere in that chain. My read (this one is mine, not the tape’s) is that as budgets grow, decisions drift from the product people to the money people, and that’s where the loop gets long. Part 2: Adoption, persistence, friction Next I wanted to get specific. When a community builds something the studio didn’t ship, like a mod, what tells you it’s real? I asked Pedro what he actually looks for, and he named three things. Adoption. Are people using it beyond the creator and a handful of friends? Downloads, likes and comments on a UGC platform help, and real usage telemetry helps more. Persistence. Does usage survive the novelty spike? "It’s great, it’s awesome, but then two weeks later people aren’t using it anymore. What happened?" Friction. How much pain will players tolerate to get it? Pedro called this "a very strange criteria, but it’s probably the most important of the three." Think of what it takes: downloading unofficial tools, joining Discords, configuring servers, troubleshooting mods that don’t work out of the box, and sometimes paying money for a feature the game doesn’t officially support. "That tells you a lot." He was careful to add a caveat, and I think it’s the one a lot of studios skip. Hitting all three doesn’t mean the studio should build it. It tells you demand exists. The studio still has to decide whether that demand fits the game, the roadmap and the economics. The friction point hit home for me. I have a friend who is widely seen as the creator of one of the world’s biggest games, Valorant, and he told me something similar: if a game is good enough, you don’t need to worry much about the first-time experience, because players will push through and bring their friends. What players are willing to put up with is the signal. I remember playing the original DotA mod in Warcraft III. It was brutal to get into, and on my first game people were cursing at me. And so many people played it anyway. Part 3: Rank the signals (Discord size comes last) Every community I’ve seen has a vocal minority that wants something, and they may or may not be telling you the right thing to do. I asked Pedro how he separates those signals from the ones worth acting on. He ranked them, and I found the order more useful than any single metric. * Retention first. "A thousand servers appearing for three days is interesting, but 500 servers still running months later is a lot more interesting." At MC Pro Hosting his team went past overall churn: they measured churn by game type and then by title (Rust, Minecraft, ARK), and shared what they found with the studios, because the studios didn’t have that view of their own communities. * Active server count. * Actual mod usage. Downloads matter, but downloads can mislead, because downloading something once costs essentially nothing. * Steam reviews for overall sentiment and repeated requests, and YouTube for what’s breaking and the culture around the game. * Discord size, last. It’s the metric he trusts least, for a reason anyone in a Discord will recognize: the first thing most people do after joining a server is mute it. Then he gave me the line I used to open the video, and I think it’s the best summary of the whole conversation: "If I had to choose between 100,000 people saying they want something and 5,000 people repeatedly doing something, I’d start looking at the 5,000." The community validation loop Next I asked Pedro to walk me through the framework itself. As I understand it, the community validation loop exists because building multiplayer is so expensive. When he ran the P&L at MC Pro, it came down to hardware, people and marketing, each roughly a third, with people the most expensive. Multiplayer means networking, sysadmins, matchmaking, orchestration, moderation, security, compliance and live ops. These aren’t launch costs. "You don’t just flip it on for like 30 days and then that’s it." His point is that if the community is already experimenting, a studio should learn from that before making the investment: "Infrastructure s… Get full access to GameMakers at www.gamemakers.com/subscribe

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

SPEAKER_00Hello, everyone. In game development, it's useful to think about the development of a game as product velocity, which is a vector, meaning it has both a magnitude, meaning how fast you build, and a direction, which means whether you are building the right thing. And with AI making the cost of development approach essentially zero, magnitude is no longer the problem. But knowing what to build seems to be the key limiting factor. And when we look at the history of games,

SPEAKER_00communities have historically driven some of the biggest insights in gaming. As an example, MOBA came from Warcraft III, Defense of the Ancient mod. DayZ, PUBG, and AutoChest are other examples. There's numerous examples of where some of the biggest insights from games have come from communities and mods. And so today we are speaking to Pedro Esparza, head of growth at BISACT Hosting. He has watched server communities form, monetize, and die at four companies.

SPEAKER_00And from his vantage point, Pedro sees what demand looks like in raw numbers before a studio knows it exists. And in our discussion today, Pedro will talk about his framework that speaks specifically to the concept of community-driven development, what he calls the community validation loop. And Pedro will bring specific examples from games like Raft, Schedule I, Oblivion Remastered, amongst others. Welcome, Pedro.

SPEAKER_01I got to say, I especially like the whole thing about communities coming, growing, becoming a business and then, you know, fading away. I've had the privilege of seeing a lot of that happen. A lot of great stories, a lot of success stories in my time in the gaming space. So thank you for having me.

SPEAKER_00Great. Great to have you. And maybe we could just cut right to the chase in terms of one of the things that I mentioned in the intro is this notion of insights coming from communities. League of Legends and MOBA, that came from Warcraft 3 mod. DayZ came out of Arma 2, PUBG. I mentioned those games. And when you think about game studios, and given that all of these insights are coming from gaming communities, Do you think studios are doing enough?

SPEAKER_00Or how can studios more effectively engage with communities to get these kinds of insights? What can they be doing better?

SPEAKER_01Yeah, so, you know, are game studios doing enough? I think, honestly, the answer is no. In my experience, there's two really good ways to read signals into what a community wants. From one side, you have a Discord channel that might ask for multiplayer. Five hundred, a thousand times, you may have community boards with upvotes and you'll see a specific request come in. If players take the time and effort to actually reverse engineer a game, to take it further,

SPEAKER_01like you mentioned with DayZ coming out of Arma 2, that to me is a much louder signal. They built multiplayer. They maintain it. They run the servers. They pay for all of this. And I think, you know, that is a much different signal than purely everyone commenting and just uploading one specific message or one specific direction that they think a game would love to go into. Community behavior for me is more valuable than just opinion.

SPEAKER_01And studios are great at collecting opinions. You know, you have Discord. Excuse me. You have Discord. You have Reddit. Steam, you know, your community threads, you know, all sorts of surveys. But I think what a studio should be interested in is reveal demand. Where those players are investing their time, their money and technical efforts.

SPEAKER_00Great. And I want to go into more about those signals and exactly how you would analyze what's being generated. Last year, I conducted a study where I tried to find what are some of the most successful games and what are some common characteristics of games that Are being successful, given that our games industry today is so difficult to find success.

SPEAKER_00And so looking especially at PC and Steam games, some of the games I looked at included games like Lethal Company, Project Zomboid, No Man's Sky, Phasmobia, Schedule I as examples, many more. But when I looked at the patterns for a lot of these games, I found that there were three common characteristics. The first was that they were relatively small teams, so teams less than 20 in some cases, maybe even one to three people even. There was strong community engagement to this point on community,

SPEAKER_00and they had long development cycles in coordination with the community. And so I wanted to ask your opinion, given that, for example, does that surprise you? And what do you think about the conclusions that I have reached in terms of those three characteristics? Yeah.

SPEAKER_01I definitely agree that there's a really strong correlation. And honestly, I've never had a chance to dissect it into these three specific criterias. I definitely think you're onto something. And the thing to keep in mind is that the common denominator between all of them is a little bit different, you know, small teams. Or long development don't necessarily create a successful game. The number of large studios that sit on a project versus the number of small studios that sit too long on a project is common regardless of team size.

SPEAKER_01So small teams don't necessarily mean that it's going to be a successful game. If more around the short feedback loop they have between the studio, or I guess it's more about that short feedback that they have between the players and the studio. Schedule 1 specifically, it's a very interesting example that you bring up because Tyler, the one developer, can reach... It's different than a larger organization where community feedback has to go

SPEAKER_01through more like red tape, for example. So from community to product to leadership, then back to product, put it in the roadmap, then engineering. All of those steps just make a specific feature or request lose momentum. And I think as we go back to that Schedule I example, Tyler was lucky enough that I believe he got Schedule I all the way to a working game all by himself.

SPEAKER_01So he was a one-man show. That shows a lot of passion and commitment, but that also gives him the benefit of no red tape, no bureaucracy, no stakeholders that he needs to report ideas or thoughts into.

SPEAKER_00Right. And that might be the point. Exactly what you're saying might be the reason why some of the smaller teams are able to find more success potentially in the sense that they are able to move probably a little bit more dynamically with respect to feedback that they're given. And also as the budgets increase, it seems like decision makers seem to shift from like, The product people to the bean counters and the money people. So maybe that has something to do with it. I do want to get into how we analyze and find key insights from the signals from the community.

SPEAKER_00But before that, I also wanted to touch upon your career a little bit, just again, to give our audience some context in terms of the specific vantage point that you bring to And so, you have spent your career essentially on the business side of game servers. So, MC Pro hosting, Nitrato, Tebex, and Overwolf now Bisect hosting. And so, you're kind of like a landlord for tens of thousands of game communities. And so… Could you explain then for our audience in more detail, like what is BISect Hosting?

SPEAKER_00And based upon that business, what is it about that the kind of game server business gives you the insights about these kinds of games and about these communities?

SPEAKER_01Yeah, so I've had the privilege of being in the UGC space when it actually took off, especially during my time at MC Pro Hosting. We were the first to support Hypixel, which, you know, if anybody's played Minecraft, they know that game. It then became an amazing UGC multiplayer server, paving the way and setting a standard for how multiplayer UGC should be. From there, I was lucky enough to go work at Overwolf under Lee McNeil, and he and I went way back because as he was building Tebex,

SPEAKER_01a server monetization tool, I was at MC Pro Hosting and I saw the vision of his platform and the ease of use for my customers, the server owners, and we definitely were one of the first to partner with him to help get that proof of concept out. And so in that same opportunity, I've had the chance to work at Tebex, and I've had the privilege of meeting tons of amazing creators in the UGC space, especially around Minecraft and 5M.

SPEAKER_01I work closely with them, And I shared all that success that I had at MC Pro Hosting and in my background as a whole. And so, you know, helping them build marketing efforts, helping them get a closer look at their revenue and what they did consist of. And for some of them, Yeah.

SPEAKER_01And so in my 20 years, I was able to observe whether people are willing to pay for something, how many communities form throughout all of this time, how quickly they form after a specific mod happens. You'd be surprised how someone can make a mod about something and then another person can say, hey, I like this. I want to build a whole business around it. And so that's a very common thing to see. Trends around novelty spikes. So for example, when a game releases a 26.2 update or a 26.3,

SPEAKER_01I see all of the momentum, the revenue that impacts not just the game owner, but all of the communities around it. As well as things like player versus server behavior. So when a new game or when an existing game has an update, how does that impact communities? How does that impact servers? And as a server hosting company, how does that impact us? How do we prepare for these updates? We also see whether people keep paying month after month after a specific update.

SPEAKER_01We see that decay, we see those trends. And then how community server demand compares to the market. Across different games, not every major update has the same level of impact. And so in the 15, 20 years that I've been here, I know exactly to a degree what sort of impact a specific game in a specific genre with this type of update has on its number of active users, which is every game studio's North Star game.

SPEAKER_00Right. So I was hoping we could actually dive a little bit deeper into what you're talking about. And so when a community does start building something like a mod that the studio itself did not ship You mentioned some of the things that you look at, and you've got data around the behavior of communities based upon mods that ship or things like that. But is there something specifically that you look for to understand whether this is something that the game studio should consider to officially support

SPEAKER_00or not? Or what is the thinking process? What are the specific levers or metrics that you're looking at?

SPEAKER_01Yeah, so there's definitely three things that I look at when a new mod or a new UGC type of vertical stems from a specific game title, and those are adoption, persistence, and friction. First, are people actually using And beyond just the original creator and like a handful of friends, right? Uploading to a UGC platform and measuring downloads, likes and comments, as well as actual adoption, which requires a little bit of telemetry on their side, helps.

SPEAKER_01The second part is persistence. You know, how does that usage persist after the initial novelty spike? It's like, OK, cool. It's great. It's awesome. But then like two weeks later, people aren't using it anymore. What happened? And then the third is how much friction are players willing to tolerate to get access to it? This is a very strange situation. But it's probably the most important of the three because if players are downloading unofficial tools, walk with me here on the number of steps here.

SPEAKER_01So unofficial tools, joining discords, configuring servers, troubleshooting mods because sometimes they don't work right out of the box and sometimes even paying money just to get a feature the game doesn't officially support. That tells you a lot, but I wouldn't jump from that to the studio should build it. Just because it hits these three criteria doesn't mean that. The signal tells you that there is demand. The studio still should decide whether that demand aligns with the game, the roadmap, and the economics.

SPEAKER_00You know, I think that last point on friction is a pretty interesting point to raise. I have a friend who's largely considered the creator of one of the world's largest games, Valorant, actually. And that was one of the points that he was mentioning to me, which was that He felt like if you have a game that's good enough, you don't really need to worry about like the initial fertility or login or tutorial, because if it's good enough, the players themselves will get there, will bring friends in. And so that's part.

SPEAKER_00Of the signal that actually he looks for is just what are they willing to do to play the game? And I even remember, you know, playing the Dota mod from, you know, off of Warcraft 3 was such a pain. And then I, on my first game, like people were like cursing at me and things like that. And it was just like, oh my God, like this is such a fun, fun game. But To get there is so brutal, but there were so many people playing despite that, to your point, friction.

SPEAKER_00And so I guess my next question would be, you've got experience watching these communities build. You also have experience interacting with these communities. And so could you talk to us about If you were to put yourselves in the shoes of a typical studio, how should they engage with these communities? What kinds of activities should they plan or how should they communicate with

SPEAKER_00the community and how often? Maybe you could just walk us through what would be best practice here.

SPEAKER_01Yeah, so I think with game studios, the biggest mistake I see sometimes is treating the community as a broadcast channel. The best studios I've seen in my experience, they create a continuous feedback loop. They talk about what they're thinking, but they also spend a lot of time watching what players actually do. Discord is very useful. Reddit is also useful, and so is Steam. But I'd probably be looking more at what mods are growing, what community servers are being created,

SPEAKER_01what's all happening inside them, which tools players are building, where players are encountering back to that friction point, and which behaviors persist. In terms of frequency, I'd rather have Consistent engagement every week than a massive community survey once every six months. That creates, you know, a big disconnect between you and the community and you're setting yourself up for failure. And obviously a huge drop in active players if you don't long to engage with them.

SPEAKER_01And I think studios should close the loop. If the community raises something important, eventually tell them what you learned and what you're doing about it. Even if the answer is, we're not building it, don't be afraid to say so because players today will respect you all the more for it. You lose more respect if you leave them in silence and they lose respect for you. So it's really important to make sure that you communicate something even if it's not what they probably want to hear.

SPEAKER_00So maybe we could get a little bit more specific here in terms of the specific kinds of community activities. And so you have some of these platforms or channels like Discord and Reddit. And so you should have the game studio have members of the team go and engage Should they also have regular calls, create devlogs? I'm just wondering about some of the other things that you may think would be effective for a studio to do to better engage with the community.

SPEAKER_00I know some people will fly out when they're key members to meet with the studio directly. Is that worth it? I'm just trying to understand what you've seen that's effective. Or is it not about the activities, it's just about how you engage with them?

SPEAKER_01I agree. I think it's the last one. It's more about how you engage with them, whether it's virtually or whether it's you flying them out to your headquarters and spending a weekend with them in some sort of summit. I do think that community teams within each game studio are incredibly valuable. But the most important thing is whether there's a path from what they're hearing into product decisions. For example, at a smaller studio, that might literally be the founder or lead developer spending time in Discord every week.

SPEAKER_01As the studio goes, you probably need community people because your game is going to grow, your popularity is going to grow, and more people are going to Think that they can demand more of your attention, which when you do that as a lead developer, one man show, then all of a sudden your product becomes a secondary and we don't want that. So as the studio goes, you need those community people, as I mentioned, but they need strong relationships with the product team, the design team and the engineering team.

SPEAKER_01And so understanding the game that they play. And I know this sounds very basic, but it's really important for community people not to Wholly focus on the community, but also take time to really understand the game that they're, you know, promoting, talking about in discussions. I was talking to a friend last week who said he was looking for a marketing slash community person and he found somebody and then their resume, you know, marketing and community skills were like 10 out of 10.

SPEAKER_01But they don't have any experience playing video games or promoting video games as a whole. And just because you have those marketing skills, you need to equally have that game knowledge or the aptitude to learn new things about a new game. Maybe it's not a game that you play, but if it's your job, you need to become familiar with it. And it's important to identify those skills. So I'd rather have two community people whose insights regularly reach the Game Studios product team than 10 people whose job is just community moderation,

SPEAKER_01banning, muting, all that kind of stuff. I think the organization question I would ask any studio is, who is responsible for turning community behavior into something the studio can take, discuss, and do something with?

SPEAKER_00Great. And so when you just try to help people or game studios understand the kind of team and the kind of people that would be required to try to execute some of the things that you've discussed, how would you think about that? That in terms of the number of people and the kinds of people, to your point, should it be a founder? Should it be someone else? Does it just depend on their skill set? And how many people typically would be required?

SPEAKER_00How do you think about that?

SPEAKER_01Yeah, so there's a scalability problem with it because you want to build that tightly needed relationship with those founders slash supporters of your game. But then after that, you definitely want to put a little bit more time into... Focusing on your game and maybe, you know, you start small and you scale big so you can bring on like a part time community person, but their job isn't just to moderate the community and keep them from, you know, from mutiny or anything like that,

SPEAKER_01but rather take all that noise and turn it into signals that then the one studio owner developer can do something with it. And so when you're talking about noise versus signal, which is something that I've always been very keen on in my past experiences and anywhere I've worked, it's really important.

SPEAKER_00Right. And to that point, sometimes in a community, you could have like a very loud vocal minority that may or may not be telling you the right thing to do, but it's just something that they want. And so how do you distinguish between different kinds of signals that you're getting that might be, you know, actually really good insights and signals that you should implement? Or you should consider versus others that you shouldn't. Is it about ranking specific metrics or how do you think about that?

SPEAKER_01So if we were to rank them, I would say that if we were to look at things like server count, retention, mod downloads, Discord sizes... YouTube comments, mentions, uploads, you know, that kind of stuff, as well as obviously Steam Reviews. If you're doing your game through Steam, I would probably put retention first. A thousand servers appearing for three days is interesting,

SPEAKER_01but 500 servers still running months, months later is a lot more interesting. And this was something that we kept in mind when I was at MC Pro Hosting. We looked at churn. You know, from a high-level business perspective, most people can say, oh, well, we want to look at churn. We want to make sure our customers are using things as long as possible. We went one step further and we created churn by game type, and then we went into specific types. So we looked at churn around Rust. We looked at how long those servers were up and running.

SPEAKER_01We looked at churn in Minecraft. We looked at churn in Arc. And we took some of that information and we shared it with the game studios because they don't have access to that kind of detail when it comes to communities as well as initiatives. If you have a community that's been running around for a long time, The question as a game studio should be like, why? What are they doing that is helping our Northstar KPI, a number of active players, you know, continue to play our game, continue to enjoy it, even if it's outside of the vanilla box and going more in this like modded route.

SPEAKER_01So retention is super important. After that, I'd look at active server count, right? So then actual mod usage. Downloads matter, but downloads can be misleading because downloading something once costs essentially nothing. When you're talking about reviews on Steam, as I mentioned, they're very useful for understanding overall sentiment as well as repeated requests. But YouTube can tell you something is breaking, right? And the broader culture around the game, rather than a dedicated Steam review.

SPEAKER_01Discord size is probably the metric I trust least. Since joining a Discord, you join, the first thing most people do is mute the channel until I turn it back on. That's very second nature at this point. So my thing is I always go with signals more than noise. As the player has to invest more into them, time, effort, money, and repeated use. We talked about those friction points earlier. So honestly, if I had to choose between 100,000 people saying they want something and 5,000 people repeatedly doing something, I'd start looking at the 5,000.

SPEAKER_00Right. So it kind of sounds like what you're saying is that data talks, right? Like you want to orient the insights around what the actual player behavior is and the data tells you what the players are actually doing versus what they may be saying. Because quite often, like, you know, sometimes specific feelings of a loud minority or it could be that the players may not even be able to express some specific insights, but the data will actually tell you. Is that essentially what you're saying?

SPEAKER_01That's right.

SPEAKER_00Okay. So now I'd like to talk about this framework. So I know you've come up with something called the Community Validation Loop. And it sounds like it's a framework to help studios orient themselves around how you can... Create a better structure around trying to get better signals and then implementing something based upon that is my rough understanding. But I think you can explain it a lot better. So if you could explain it for the audience and to me, I'd love to better understand this community validation loop framework

SPEAKER_00that you have.

SPEAKER_01Yeah. So the community validation loop is the way that I think, in my experience, is How studios should look at decisions, especially around multiplayers. So once a game studio decides that multiplayer is a core feature, you're potentially committing engineering resources and people, which is always the most expensive part in game development. I remember at MC Pro, my P&L was always hardware.

SPEAKER_01People, marketing, it was always those three. And it was almost 33%, you know, across the board. Hardware was expensive. People were the most expensive. And marketing, depending on what you're working on, was equally kind of balanced between the two. So you have to spend into resources and people, but also, you know, Networking itself, you have to hire sysadmins, you have to get into matchmaking, you have to get into orchestration, moderation, security, compliance issues, live ops.

SPEAKER_01If you were to mention the word live ops too, To a small indie developer, like say Schedule 1, they were working on their amazing passion project and you said, oh, this needs to be a, we need to talk about LiveOps. They would absolutely just fall over thinking of the fact that they would have to have something to support that. As well as ongoing support. So those aren't just launch costs either. Those are ongoing things. You don't just flip it on for 30 days and then that's it.

SPEAKER_01It's a continuous expense that you have to keep in mind. And so what interests me the most is whether we can move You know, some of that validation earlier so that if the community is already experimenting with multiplayer or dedicated servers or whatever other behavior, why not learn from that before making such a huge investment? And I think at the end of the day, infrastructure should follow validated player demand rather than being the thing you use to discover that player demand exists.

SPEAKER_00Just to make things a little bit more concrete for the audience then, could you maybe give us a specific example or use case of this community validation loop and maybe walk us through each of the phases of how this would work and what the game studio would do, what they would see, and then how they react at each of these phases?

SPEAKER_01Right. The validation loop is really a way of reducing the risk of building something purely based on what people say they want. We talked about saying versus doing and et cetera. So instead of making a huge product decision up front as you're building the game and you're even putting your story together, you progressively validate demand. So the first thing you want to do is find the signal. What are players repeatedly asking for or are they creating themselves?

SPEAKER_01The second thing is enable an experiment. Give the community enough access to test the idea, whether that's mod support through mod.io or whatever, dedicated server binaries, APIs, or just not stonewall things and make things really difficult for your community to explore new things. So the third thing is also measure behavior. Are people actually using it? Are communities forming because of this? Are servers kind of popping up left and right?

SPEAKER_01Are players returning? How is your North Star metric? Fourth, you want to validate persistence. So does that behavior survive beyond the initial hype? Are people investing meaningful time or money into it? And then finally decide whether To build it in game. And, you know, at that point, the studio has substantial more evidence to decide whether it should become an official thing or keep it community led. And I think, you know, those are important.

SPEAKER_01Or the third one is to just leave it alone if they're doing something that's helping you drive more sales as a studio, maintain visibility and continue to grow. And you don't have to touch it, but you've provided them with the tools and resources. Just let them. I think one great example of that is, you know, Minecraft is a fantastic title, especially on the Java side. They don't really touch that side of the business. They let the community drive more players. They let the community drive more things to explore,

SPEAKER_01which means more players are going to see it. And that drives the revenue for game sales as a whole.

SPEAKER_00Okay. And so in those five steps, first was find the signal, second was enable the kind of experiment through some of these things. And so as a game developer coming from the mobile side, where a lot of the games in mobile don't have as much community enablement as maybe some PC and Steam games, could you walk us through that in a little bit more detail? So you mentioned a few things like... Whether it's APIs or mod.io. So could you walk us through all the different ways that you could enable community experimentation?

SPEAKER_01For mobile?

SPEAKER_00No, just generally. I'm just saying, for me coming from mobile, I just don't understand it very well. So if you could go into a little bit more. Just explaining what some of the... Like, I don't even know what mod.io is, for example.

SPEAKER_01Okay, yeah. So when you talk about, you know, allowing... Players to try these things, you know, enable those experiments. Mod.io is a fantastic platform because it allows game studios to build a UGC library for players to then use, download, and try things. For example, if we were to look at... Any game title that uses UGCs, I'm blanking out on all the games for some reason right now, but that maybe use mod.io or don't.

SPEAKER_01But the idea is the game studio can use mod.io to create these assets, which then players can use. This basically allows a do and don't list for UGC creators to create the kinds of things that they want. Let's say, for example, there's a war game, you know, first person shooter. And they want to enable, you know, customization of tanks. Well, then what that game studio will do is they'll upload that tank asset to mod.io and

SPEAKER_01then allow players to extract that asset directly from the game. So it's staying always They can download that asset, modify it, whether it's rapid in pink, or whether it's rapid in camo, or maybe put a different gun, bigger wheels, etc., But they're using this intermediary platform between them and the game, and it allows them to really explore all the limits. And the game studio is safe knowing that what they've allowed through Bond.io

SPEAKER_01or whatever other platform they want to use allows them to let the players in the community have fun with these assets or specific levels of access that they want with the game itself.

SPEAKER_00Okay. And I was looking at some of these specific use cases in terms of like different games and how they try to kind of reduce product uncertainty. And so when we look at games like Raft, which kind of tested the core concept with a free prototype, Stardew used demonstrated kind of player demand to prioritize co-op and, you know, Schedule 1's modders, I guess there was a shift to dedicated servers,

SPEAKER_00and maybe you can go into more detail on that. I'm wondering if you could talk a little bit more about how should a studio decide what it needs in terms of a prototype or structured player research, just looking more at the data, or some kind of community-built experiment. How should a studio think about this? And what do each of these different kinds of things do? How would a studio use these methods to actually prove something to them?

SPEAKER_01Yeah. So when you're talking about Raft or Starter or Schedule 1, those are all various different use cases. And the way they developed... Additional products within that game. That's why I don't necessarily think there's like one validation method because sometimes the man is overwhelming enough that direct community feedback is useful. Sometimes players can prototype the feature through mods, and sometimes the developer itself can cheaply prototype the idea.

SPEAKER_01I think my preference is always around economics and effort. But what is the cheapest credible experiment that gets us closer to observing that behavior instead of just opinions? If you can test something for weeks or months before committing years of development and LiveOps resources, we talked about some of that earlier, then that's going to be incredibly valuable.

SPEAKER_00Okay. And so maybe like one of these, like Schedule 1, obviously a huge success story. One developer, Tyler, 8 million copies, you know, four-player peer-to-peer, no official server. And then could you walk us through like, how did this kind of shift to dedicated servers happen? Maybe walk us through exactly what the community signal was and what happened.

SPEAKER_01Schedule 1, one amazing developer, fantastic game. I'm a big player in this title. The big thing that communities wanted to do is support that initiative and make it a persistent idea, something that they could enjoy 24-7, literally, without having to rely on that one person who's hosting it for the rest of them. The high-tech mod definitely did make that happen. With these These servers, you know, we want to look at occupancy. We want to look at the data behind all of that.

SPEAKER_01So unique players, how long were the sessions in terms of like when someone was around, retention of those servers, was it seven days, 30 days, 90 days, or is it still ongoing for some? So, you know, in terms of what I would tell the studio, instead of like, as a community, I wouldn't say, hey, you need to build more dedicated servers. I would say, Is there enough evidence so that you should investigate this further? If you see this mod and you see that what it's doing to your players

SPEAKER_01and it's impacting your metrics in a positive way, that's an opportunity to take that signal and look into it further.

SPEAKER_00And from the perspective of the impact to the game, like what did you see and what does that mean in terms of like players and what does that mean in terms of cost, like shifting from, you know, Peer-to-peer to dedicated.

SPEAKER_01The big lift going from peer-to-peer to dedicated is the amount of responsibility that we remove as a game host provider that we remove for the game studio. The game studio doesn't have to rely on keeping the framework needed to support peer-to-peer by letting us have But by letting us manage dedicated servers, we remove all the pains and headaches that come with that. And you can then focus on storytelling, feature updates, new things.

SPEAKER_01And so I think that's the best thing that I could say you should get from the biggest benefit that I see from letting dedicated servers remove that peer-to-peer headache.

SPEAKER_00And when you think about features that should be built by the studio versus having a third-party productize something, how should a studio think about that? And, you know, as specific examples, I think Rim World Together, Community Mod, I think you guys are the official host. Ludeon never built multiplayer. Like, what should the thinking be from a studio in terms of, like, You know, the studio internal development versus, you know, third parties.

SPEAKER_01So deciding one over the other is a big question. And so the big thing about my framework is it's important to consider whether the community creates something players love. And if that's the case, then it may be perfectly rational for the studio to leave it community run. If it's humming and everything, everyone's happy, as they say. Then you should leave it as is. The studio could officially support it. They could say like, oh yeah, we support it.

SPEAKER_01It could expose maybe some additional APIs. It could work directly with the modder. It could hire them. It could partner with them, et cetera. Or it could just simply leave the door open. Hey, you're doing great things. We appreciate it. If there's anything you need from us, we're just to click away. And build that kind of passive partnership. I think one great example is the whole 5M or CFX.RA acquisition by Rockstar. The goal here isn't for the studio to own everything players create.

SPEAKER_01This is how you stonewall yourself up and you create these gaps between you and the community. The goal here is to understand what players are telling you through their behavior.

SPEAKER_00Right. And then what about Skyrim together? You know, years of demand, hundreds of thousands of downloads and Bethesda, I guess, didn't go through with it because of cost. How do you interpret that? What would you have done?

SPEAKER_01You know, I don't think the existence of like demand automatically means that Bethesda was wrong. I think a community can prove that players want something. It can't prove that the economics work for the studio. I think there's a lot of things that Bethesda has to consider, as I mentioned, engineering, QA, platform. And this is on a much bigger scale because you're talking about a reputable studio. You have support, security moderation, brand risk, and the opportunity cost of what those developers aren't working on instead.

SPEAKER_01The distraction to go into this, what's going to be impacted by this? What's going to be put aside while we focus on this? Bethesda, with Skyrim together, can simultaneously prove that multiplayer demand exists and Bethesda can rationally decide not to build multiplayer. It's not the best example, but it is one that we have to keep in mind. Even if the signal's right and everything is saying yes, Sometimes the economics or the red tape just isn't allowing that to happen.

SPEAKER_01Those aren't necessarily contradictory conclusions either.

SPEAKER_00Right. And we not only have community-based mods and additional capabilities for games, but if you look at games like Oblivion Remastered, Black Myth Wukon, Black Myth, Wukong, they're both getting multiplayer from ReadyM, which is a venture-backed platform. And so how do you think about kind of like, you know, professionalized enablement of, you know, capabilities for games?

SPEAKER_01Yeah, so when it comes to ReadyM and Michael, fantastic guy. What a passionate individual, by the way. I've enjoyed my conversations with him and seeing what he's doing with these game titles has been a lot of fun. I do think professionalization definitely strengthens the thesis of Of, you know, these mods and historically community experimentation, dependent on someone talented, being willing to spend hundreds of hours building something for fun. Now you're starting to see developers and companies and hedge funds

SPEAKER_01who are very interested in this space and are looking to, you know, support these initiatives. And so to me, that's interesting because the community layer starts becoming an infrastructure for experimentation. So a studio may no longer have to choose between we build it ourselves or we don't have multiplayer. There's a third option that's growing in the space that is someone else proves it. Someone else proves the experience first.

SPEAKER_00Right. And just to speak to a game studio, just getting really tactical here. So let's say you run a small studio, 10, 20 people, something like that. A small studio, you've got a hit. And your community starts building something that you didn't ship, but you've got some community enablement features, whether it's mod.io or whatever. And so what is the sequence? What does that studio do? Let's say on Monday next week, what should they do?

SPEAKER_01So the first thing I wouldn't do is put it on the roadmap. Monday morning, I would find the people building it and go talk to them. Understand what they've built, why they've built it, who's all using it, getting permission to look at those metrics, what limitations they're running into, and how I can help them, and then start instrumenting this behavior. I want to know how many people are using it, how frequently they're using it, whether the usage is growing. We talked about when something comes out.

SPEAKER_01And we have that honeymoon phase where everyone's on it, but now what's happening after that? Whether they're bringing other players into the game, you know, is this impacting, is this kind of having like a halo effect against my sales? My number of players. And most importantly, whether they're still doing it 30, 60, or 90 days later. I think from there, I'd make the smallest investment necessary to remove friction from the experiment, you know, that specific mod. And maybe that's documentation. Maybe it's an API. Mm-hmm.

SPEAKER_00One of the things I mentioned is that as a mobile game developer, we've seen much less modding support or community enablement types of capabilities. A lot of this works in terms of the community validation loop and getting signal about stuff for the game if There is some capability there for the community. And so no mod support, no dedicated server option, no API means no signal.

SPEAKER_00And so is leave the door open at launch, maybe you could talk about that approach. What is the cheapest thing a studio can do to leave things open for the community?

SPEAKER_01I think... Leaving the door open, like you said, is probably the simplest way I would ask this feedback over to the game studio, no matter the size. But I don't mean that every game should, on day one, have Steam Workshop, complete SDK, dedicated servers, APIs, the works, basically. The cheapest door is simply designing the game so that experimentation isn't impossible. If dedicated servers make sense architecturally, you can consider exposing the server binary.

SPEAKER_01That's usually the way that most of multiplayer servers usually allow servers to happen. Game server owners want that control. And so if you're okay with them just having fun and strengthening your community by creating stronger pillars on top of your game as a whole, that is definitely something that I would do. If there's any configurations that can safely be exposed, document those. Don't unnecessarily encrypt or lock things down.

SPEAKER_01The community wants to experiment and you don't need to do all of that. And then when someone builds something interesting, don't make your first reaction to send over a cease and desist. Reach out and speak with them. And as I mentioned, just find out what they're doing and how is it working out for them. Because at the end of the day, you don't have to build the experiment. Sometimes you just got to make sure you haven't designed the game to prevent one.

SPEAKER_00Right. My understanding of the community validation loop and one of the major use cases I think you alluded to earlier is basically multiplayer. The way that a lot of people have thought about your framework is like taking a single-player game and then turning it into a multiplayer experience of some kind. When you think about some of these single-player games that are then extended to multiplayer, I guess my question is, when is the answer sometimes no?

SPEAKER_00Just stay single-player, don't consider multiplayer? Or if you want to even generalize, when should a GameCity not consider engaging or doing stuff with some of the things that they're seeing in the community?

SPEAKER_01I think there's plenty of games that I would sell them to stay single player forever. Multiplayer isn't automatically a feature upgrade. It can fundamentally change the product. And there are some, just like there are amazing mods like the ReadyM Crew. There are others who are making multiplayer mods for games just for the sake of having it without realizing how the game mechanics change as soon as you add You know, 20 people instead of four, for example.

SPEAKER_01It introduces network complexity, infrastructure, moderation, cheating, security, and as I mentioned, the whole LiveOps dilemma. Instead, I'd ask whether multiplayer actually strengthens the core experience, because if the community signal is weak and retention is poor, the experience doesn't become meaningfully better with more players. Or supporting it takes away from that and it makes the game special, I would say, I don't think you should do it. That doesn't mean you have to stop the community from experimenting by any means.

SPEAKER_01There's a huge difference between we shouldn't build this and players shouldn't be allowed to build this.

SPEAKER_00One of the things that you mentioned is like, instead of a studio automatically going for a cease and desist, they should maybe talk to the people that are in charge of a specific mod. But when you think about, because a lot of studios still do takedowns, for example, but where is that line? And when should you go for the cease and desist or the takedowns?

SPEAKER_01I mean, a cease and desist should only be enforced, at least in my opinion, should only be enforced if they are breaking core fundamental mechanics of the game. And I think that is definitely where I would pump the brakes and I would still reach out to understand what they're doing. And if they're like non-communicative, not willing to understand my concerns as a game studio, then I would then need to proceed to, you know, More of like a hand-on-hand kind of conversation about it.

SPEAKER_01Unfortunately, sometimes that happens only through legal cease and desist and things like that.

SPEAKER_00Okay. And I want to mention something that you spoke about at Gamescom, which is this kind of new product, Bisect 1, I believe is the name of the product, which would be a product for multiplayer studio leaders. And I don't know, could you talk about that? It sounded like some kind of productized version of listening to your community, of listening Something along those lines. Maybe you could explain what that exactly is and how

SPEAKER_00that could help game studios better engage or listen to the community.

SPEAKER_01Yeah, so there's two separate things here. What we've been talking about today is how studios determine whether multiplayer demand exists. Bisek Fleets is more about what happens once that demand is real. So once you've validated multiplayer, you suddenly have a different set of problems. Where do servers run? How do you allocate capacity? You know, RAM allocations, CPU allocations. How do you respond to concurrent users changing by region?

SPEAKER_01How do you monitor performance? How do you scale without over-provisioning and seeing some crazy, scary bill at the end of the month? This all matters greatly when you host the servers yourself and you need a solid platform to help you manage 100 or 10,000 servers. And with Bicep Fleets, that's the infrastructure problem that we're solving.

SPEAKER_00Got it. So those are all the questions that I have, Pedro, but is there anything that I left out that maybe I should have asked you? What would that question be or what would be the specific additional insight, if any?

SPEAKER_01No, I actually enjoy these questions, and it's fun to be able to talk to people in the space that I think, you know, that share this similar community goal. Yeah, it's a shared community goal. We want all games that are telling great stories to be successful, whether that... Whether it's Mario Kart, whether it's Schedule 1, whether it's GTA 6, we have a certain level of passion and commitment to helping everyone be successful. And I think that's really what we want to do with all of this knowledge,

SPEAKER_01sharing, and advice that we've learned throughout the years. So I appreciate the opportunity to be able to speak to others about it.

SPEAKER_00Well, I appreciate your thoughts and insights. And so maybe what we can end with is like, if there is somebody out there in the audience that would like to know more about maybe you or about BISect hosting, how could they find out more information or getting contact?

SPEAKER_01Yeah, so if they want to learn more about BISeC hosting, whether it's private, dedicated servers, you can go to BISeChosting.com. If you'd like to speak with me and learn more about BISeC Fleets, managing 100 to 100,000 servers, all with a nice, easy configuration, nice, easy tooling, we can have a conversation with me. You can find me on LinkedIn, or you can just shoot us a message on the contact page at the bottom of BISeC Hosting.

SPEAKER_00Awesome. All right. And I'll include links to all that in the show notes. But with that, Pedro, thank you so much for your time. And for our audience, we will catch you next time. Thanks, Pedro.

SPEAKER_01Thank you. Thank you, Joseph. [music]

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. PR for Gaming Studios

    Sep 1, 202651 minAudio

    Kalie Moore ran the prompts across ChatGPT, Gemini, and Perplexity. What came back turns game discoverability into a PR problem, and she gave me the playbook she uses to fix it. When I ask people in games what PR is...

    Credit the people on this episode

  2. The Paradox of AI ROI

    Aug 28, 202659 minAudio

    The story is that AI isn’t paying off, that the ROI just isn’t there, that the org charts and the earnings calls are still waiting for the productivity spike. Harsh Savergaonkar and I are pretty extreme vibe coders....

    Credit the people on this episode

  3. The Most Important Number in Unity’s D2C Launch Is Zero

    Jul 14, 202643 minAudio

    In 2002, Electronic Arts banned ICQ - the office chat app - and put a single internet terminal in the center of the building. A programmer named Steve Ganem responded with what he calls “civil disobedience”: he built...

    Credit the people on this episode

  4. So This Is How The Metaverse Dies

    Jun 23, 202650 minAudio

    Here’s the top of the Fortnite metaverse, as of June 20, 2026, during a Saturday night at around 8 pm EDT: (Source: fortnite.gg) #1. Battle Royale: 549.3k concurrent players. #2. A battle royale variant: 97.7k #3....

    Credit the people on this episode

  5. 🎙️ The Most Valuable Asset in Games Isn't Your Game

    Jun 16, 20261 hr 58 minAudio

    Here’s a contradiction worth sitting with. Earlier this year, Epic Games - the studio that spent five years and north of $100 million breaking the platforms’ 30% tax - quietly cut the value of V-Bucks by 20% to, in its...

    Credit the people on this episode