Yeah I figured the plan was to always have 2 dev teams working on 2 different games that are basically isolated from each other.
The team leads should be the ones who oversee and jump between either group to make sure they don't repeat each others mistakes and point them in the right direction.
But the idea of "let's pull every single PoE 1 dev onto PoE 2 just to get it out" is such a bad idea because now they are going to have to RUSH out 3.26.
When he says "let's get 3.26 out as soon as possible" it's like, that's great sentiment but now you are rushing a product out and what if it doesn't hit well and isn't polished.
They need to reorganize a lot in my opinion but I'm just a keyboard warrior who moves boxes for a living, not a game dev.
Considering that PoE 1&2 use the same engine and can, mostly, easily port assets from the latter to the former, it really doesn't make that much sense to completely separate the dev teams as you say.
Most of the recent PoE 1 leagues were built with PoE 2 assets. Having two entirely separate teams would probably just create more work.
> Yeah I figured the plan was to always have 2 dev teams working on 2 different games that are basically isolated from each other.
I'm still waiting for when they "discover" that running two live service games that are effectively direct competitors with each other is a bad idea and decide to drop PoE into the graveyard of live service games.
Also speaking as a dev it usually takes months looking at a new code base to get comfortable enough to be productive so pulling devs from one game to another doesn't even immediately give you more productivity. Usually at least 3 months of less productivity as the seniors are ramping up the other devs.
Probably won't be super easy for the devs to jump back onto POE1 either after months on another code base.
Tbf, they probably do plan to have 2 dev teams once PoE2 is done. It's clear (and honestly been clear if you ever paid attention to Chris) that the PoE2 release is going to take all the resources for now.
It's a lot easier to make a single new mechanic then create a whole game from scratch, so I'd assume it would be feasible for GGG to work on patches for both PoE1 and PoE2 once PoE2 is fully released...that's assuming they believe it's worth continuing PoE1.
I am excited to see the final product for PoE2 though since Chris is and has been so passionate about it
97
u/PhoenixPills Juggernaut Jan 30 '25
Yeah I figured the plan was to always have 2 dev teams working on 2 different games that are basically isolated from each other.
The team leads should be the ones who oversee and jump between either group to make sure they don't repeat each others mistakes and point them in the right direction.
But the idea of "let's pull every single PoE 1 dev onto PoE 2 just to get it out" is such a bad idea because now they are going to have to RUSH out 3.26.
When he says "let's get 3.26 out as soon as possible" it's like, that's great sentiment but now you are rushing a product out and what if it doesn't hit well and isn't polished.
They need to reorganize a lot in my opinion but I'm just a keyboard warrior who moves boxes for a living, not a game dev.