Switching From ThreeJS To Unity Engine

Well, it was a difficult decision but, the fruits of the pain are ready to eat!

Already, we have a full battle royale mode #PrisonPlanet up and running within Unity.

Why the switch?

Simply: AI Is trained on Unity, where as AI coding for ThreeJS is more interpretive as a custom engine, which is less desirable because of the sheer amount of mistakes AI makes in ThreeJS environment.

Our ThreeJS project got hung on basically performance, LOD management, and writing a loading system.

Another thing is that the assets produced in the Unity store are just so readily available. Terrain systems, models, networking, etc.

Vehicles were a total nightmare to get working in our FPS engine, it just didn’t work out for us. Where as Unity offers a simple vehicle package that we bought for $3.00 CAD. Drag, drop, vehicles work.

It’s similar to writing plugins for WordPress; AI just knows how to do it with no mistakes. Whereas AI writing a custom react website would blow away code, create bugs, etc.

The lesson? AI isn’t super at creating brand new code features without an engine. Hope this helps someone out there.

But the screenshot up there? Wow. I’m genuinely shocked how fast and how good looking the game is becoming in just 10 days of Unity with no previous experience in the engine.

You can click PLAY NOW and try it out!

PS: I hate the Unity billing model, but hey man, IF we hit 1m in revenue per year and have to pay Unity… so be it. I’m sure at that point we can wrangle some venture capital.