u/GreaterThan2

https://preview.redd.it/ntsxqra5aljh1.png?width=694&format=png&auto=webp&s=1b6edf54b74806d4a9cf7fac01efa2f6a6df1fa0

Hey everyone,

I’m a student developer, and over the past few months, I’ve poured all my time into building PlayerMC (playermc.site). It’s a dedicated platform for Minecraft player lookups, server status tracking, and a skins gallery utilizing WebGL for 3D skin rendering.

The Product Angle: Most Minecraft players use NameMC, but the biggest community frustration with it is that users can hide their username history. I built PlayerMC to solve that specific pain point, it does not allow name history hiding. If an account changed names, it remains fully transparent on our platform.

The Highs and the Roadblocks: When I first shared the project, the initial "launch spike" felt incredible. Seeing actual server lookup traffic hit my dashboards and watching users browse the skin gallery validated all those late nights coding.

But right now, I've hit a double wall:

1. The Traffic Slump: The initial launch hype has died down, and my organic traffic is tapering off. I'm trying to figure out how to transition into sustainable, long-term distribution within the gaming niche without a marketing budget.
2. The Infrastructure Crunch: My API relies heavily on a native Node.js environment that requires a dedicated VPS to run properly without breaking. The hosting invoice is $25 this month, and being a student with zero income, I flat out don't have it. I’m facing a complete database/API shutdown if I can't keep the lights on.

What I'm hoping to get from the community: I really don't want to let this project die over pocket change.

• For those who have built niche utility tools, how did you survive the massive drop-off after your initial launch spike?
• How do you market a tool directly to a gaming community without getting banned for self-promotion?

I've backed up all my data, but I'm trying everything I can to prevent an actual service interruption. Would love your honest advice on the project, the distribution problem, or how to handle hosting crunches at this stage.

Thanks guys.