But even in those two cases you can seperate it from the core game.

So, basically, the main discussion boils down to 'if this fails at a critical time, how dire will the consequences be?' And if the answer is that it can stop the whole production or results in missing an important deadline, it wont get put in the game.Īlso, sometimes it just can't be done in-house, because the system would be too big for the teamsize, like pathfinding or network code.

If it breaks in some way, there is a lot of back-and-forth with the creator of the asset, and it can halt your whole development.

Things like a character controller has to be strongly wired into the whole game, and often has to be modified to suit the design needs. That way, if there is some problem with the tool (incompatability with a needed unity update, a system breaking bug), you can theoretically switch it out for another solution or put that part of the game on hold. In my experience, in production, it works best if external tools are as seperated and stand-alone as possible.

Unity asset store commercial use