[pistle]

I see a disconnect between balance of dependencies vs. the minimum required to yield the target result. A lack of focus on the thing you are trying to show... coding skill/efficiency around the game problem. The tight piece should be a great set of game code. I see, which I see a lot when I see IoC for small jobs, inversion of focus. Lots of ceremony yielding a loss of clarity.

You know laravel. You know about libraries and can use them. It's less clear that the code you wrote was good. It's sort of buried in a fair bit of noise.

You won no favors by requiring an install of the nature you have and fumbling that a bit as well (chmod 777).

The other thing is... you can't trust a potential employer's reason for saying, "No." They said it, but you don't know if the message is garbled by the HR rep or even a flat out lie because the short answer is, "No." and they don't want to spend time explaining themselves.

They decided and moved on. They are not invested in your future. Coming here for feedback is a good practice. We care about you and have few reasons to just let you know, "No."

Soooo many dev job fish in the sea. Get your line back in. Your bait is fine.