• Projects 3
  • Rating 3.5
  • Rating 572

Budget: 1500 USD Deadline: 10 days

I can start immediately and complete the Pixi.js polish in 10 days for $1,500. Within 24 hours, I'll deliver a concise mechanics and physics audit with a prioritized tuning plan, then refine the update loop, deterministic physics, responsiveness, game math, and balance curves. I won't rewrite the architecture unless the documentation reveals a genuine blocker.

  • Projects -
  • Rating -
  • Rating 406

Budget: 1500 USD Deadline: 8 days

Hello,

I’m an experienced JavaScript game developer with strong expertise in Pixi.js and 2D game development. I have hands-on experience refining gameplay mechanics, optimizing game physics, balancing game math, and improving overall responsiveness to create a smooth and engaging player experience.

What I can contribute:

* Improve physics, collision, and movement systems
* Fine-tune gameplay balance and mathematical calculations
* Optimize performance while maintaining clean, maintainable code
* Work efficiently with an existing codebase and technical documentation

  • Projects 39
  • Rating 4.9
  • Rating 7 867

Budget: 1500 USD Deadline: 7 days

Good day, I am ready to complete your order but we need to clarify the details, please contact me.
https://pprintim.com

  • Projects 32
  • Rating 5.0
  • Rating 7 968

Budget: 1500 USD Deadline: 14 days

You need someone to take a working Pixi.js game and make it *feel* right — tightening physics constants, rebalancing progression curves, and eliminating the friction points that stop players from staying engaged.

My approach: first I audit the existing physics layer to identify where forces, velocities, or collision responses produce unnatural behavior and fix them with tuned parameters rather than rewrites. Second, I profile the game loop for frame-rate consistency — Pixi.js ticker drift and interpolation issues are the most common source of "sluggish" feel, and I'd lock that down. Third, I review the math behind scoring, difficulty scaling, or any RNG systems and adjust them so the difficulty curve feels intentional rather than arbitrary.

I work directly in your existing codebase, no architecture rewrites unless the docs point to a structural blocker.

Could you share the technical documentation and describe which specific mechanic currently feels the most off — physics response, balancing, or something else?

The list does not show proposals concealed by the client or freelancer with a Plus profile, as well as proposals violating rules