{"id":12841,"date":"2025-01-29T10:24:31","date_gmt":"2025-01-29T17:24:31","guid":{"rendered":"https:\/\/mattfife.com\/?p=12841"},"modified":"2024-12-15T10:34:07","modified_gmt":"2024-12-15T17:34:07","slug":"when-to-make-your-own-tools","status":"publish","type":"post","link":"https:\/\/mattfife.com\/?p=12841","title":{"rendered":"When to make your own tools"},"content":{"rendered":"\n

Mr-Figs asked a great question on the reddit gamedev forum: how do you handle making your own tools needed to make a game?<\/a><\/p>\n\n\n\n

It used to be that building a game also meant building all the authoring tools to go along with it. With the advent and spread of game engines like Unity, Unreal, Godot (and literally hundreds of others) along with amazing tools like Photoshop and Blender, the need to make your own tooling has dramatically decreased. Almost to the point that in a majority of cases, you probably don’t need to write tools. <\/p>\n\n\n\n

Even if you do find you can’t use an existing tool, others suggest using chatGPT to either extend an existing tool or a tool in the engine you’re using via their SDK. Let AI do the work for you since tools are not shipping code nor need to be overly performant.<\/p>\n\n\n\n

Strict_Bench_6264 wrote up a whole blog article to describe what he learned:<\/p>\n\n\n\n

\n
Custom Tools and Work Debt<\/a><\/blockquote>