⌘K
Ahmad Sajid This is a really fun twist on the usual snake concept. Making the player the one being chased gives it a nice sense of pressure right away. The 5-second spawn interval feels like a good starting point, but I could see the difficulty becoming much more interesting if the interval gradually decreases as the score increases. I also like the Top X% idea, especially with the global leaderboard. It gives the short runs a bit more purpose and makes you want to immediately try one more time. The React/Canvas \+ Supabase setup is a nice combination for a small browser game too. I’d definitely be interested in seeing things like different virus behaviours or temporary power-ups added later.
Physikz2 Thank you for the feedback Ahmad I really appreciate it and yes i agree with some of your points as Ive considered them myself. If the global counter does get higher maybe I will introduce new things here and there
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Amy Egan Did you try the debugging tips linked above? I'd recommend checking the build settings and output to figure out why the page is missing
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Ryu Hi Solomon, The `Functions` tab only showing `/api/auth/[...nextauth]` is not necessarily a problem by itself. Static App Router pages will not always show up there as functions. The more important signal is the exact 404 type and which URL is returning it. I’d separate three cases: ``` 1. Unique deployment URL returns 404 2. Project/production alias returns 404 3. Only specific app paths like /todo return 404 ``` Can you test the unique deployment URL from the deployment details page, not just the project alias? ``` curl -I https://<deployment-id-or-unique-url>.vercel.app/ curl -I https://<deployment-id-or-unique-url>.vercel.app/todo curl -I https://study-hub-phi-sand.vercel.app/ curl -I https://study-hub-phi-sand.vercel.app/todo vercel inspect <deployment-url> ``` If the unique deployment URL works but `study-hub-phi-sand.vercel.app` returns `DEPLOYMENT_NOT_FOUND`, that points to an alias/routing association issue. If the unique deployment URL also returns Vercel’s platform `DEPLOYMENT_NOT_FOUND`, then that is much stronger evidence that the deployment is not being served at the edge even though the dashboard says Ready. The most useful escalation details would be: ``` deployment URL tested: production alias tested: deployment ID: exact UTC timestamp: x-vercel-id from the 404 page: vercel inspect status/target/aliases: ``` I’d avoid redeploying repeatedly for now unless you need to restore service, because the current broken deployment state may be what Vercel needs to inspect.
