Hi guys, I hope that are well…
I would like to share the previous game and would be great if you can test and play a bit and share comments, more ideas, feedbacks, etc
Sploshball
A first-person paintball game that runs in the browser — built to play with
friends and family. Colourful paint splats, visible flying paintballs, an arena
full of bunkers, and either AI opponents or real ones over the network.
sploshball.com
Two ways to play
| Mode |
What it is |
| Solo |
A 5-minute match against AI bots that patrol, take cover, flank and shoot back. |
| Online |
Everyone types the same room code and fights in a shared arena. |
4 Likes
Hey Juan!
Hey, I tried your demo. Look, there are some critical issues:
-
When I first loaded it, I got stuck at the “Loading the field… — 58% · 59 / 101 MB” stage. I waited about five minutes and then refreshed the page. I think you might want to use a resource loader with reconnection capabilities. There were no errors in the console.
-
The first time I launched, I saw a game manual that I really wanted to skip, but there was no button 
-
When I tried to launch the singleplayer, I saw an error like “Could not load https://rawcdn.githack.com/pmndrs/drei-assets/9225a9f1fbd449d9411125c2f419b843d0308c9f/cloud.png: undefined” – and if I press the reload button, the page completely reloads, and I’m back in game mode, which I can’t exit.
So, I physically can’t play.
Try storing all the resources on your server.
Judging by the screenshots, I’d work on the weapon models; you have a pretty cool game style.
And, from my experience, the most difficult thing in such games is balancing the competitive mechanics and the player behavior mechanics (physics) so that the controls feel native to the user. For example, one of the best references is Valve games — they have very good immersion in character control. This is VERY difficult to achieve.
It also makes sense to check the user’s device at the start of the game and, if they’re logging in on a mobile phone, display a message that stating the game is only available on desktops.
Optionally, you can try creating an Electron build of the game or a launcher for it.
1 Like
Update:
The asset wasn’t loading because I had VPN on. Unfortunately I sometimes have to use it.
The game launched.
What’s noticeable:
-
pretty cool design
-
weapon models would be better done with a modeler/designer
-
freezes happen quite often — looks like when a new material or shader appears in the scene. In my own demo I use scene “warmup” before start: everything that might potentially show up gets rendered before the game starts, and then there are no freezes
the rest of the development depends on what you ultimately want to build. It’s fairly obvious you’re using AI to generate code, but (in my opinion) you need to be very careful about what gets generated and how — the engine structure and how entities relate in the architecture. If you let the process drift, you’ll very quickly end up with a “mess” in the code and bugs that are really hard to track down.
By the way, you can use my debug utility — it’s pretty useful for this kind of work: DHGui — debug GUI panel
1 Like
Thanks for your comments, I’ll take a look 
It’s extremely stuttery; I don’t know exactly what my frame rate is, but it feels like 30 FPS, with occasional severe spikes and lag—even though I have a powerful gaming PC.
The controls and aiming don’t feel right; it feels jerky and pixelated. I can’t aim smoothly.
When I jump, I often get stuck in mid-air, losing control until I automatically reach a higher level, at which point the controls start working again.
Sometimes the game freezes for three seconds; everything just hangs for several seconds.
It looks good, but players won’t stick with it because it doesn’t feel good to play. It has that typical “browser game” feel. Yet, Three.js is capable of so much more—enough to make it so you wouldn’t immediately notice it’s running in a browser.
I hope this constructive criticism helps you.
1 Like
hey bro, take a look again when you have a chance
