No, Nes Maker is just like Unity, which is for lazy f**ks
Recent community posts
Me again, :|
The idea for stuff sort of like leaderboards, if the user's name changes, I'd like it to update on the leaderboard.
Maybe by creating a new API endpoint?
If practical, maybe it can also be extended to other user information?
This would be an amazing feature for multiplayer games that depend on Itch.io's APIs.
This is currently not an issue for the game I am making, however it will be one for sure in the future, seeing as it's multiplayer.
Should the callback URI point to my global game server which manages basically everything?
But how would the server know which client to trust judging by that API key it's given?
Or should the callback URI point back to the client?
Although this might be insecure as well.
I'm making a game at the moment, and it's big.
The problem is getting is started, which is unlikely without a lot of marketing.
How less likely am I going to get users with the client than directly from the browser?
I'm asking this question because I am using Itch.io authentication with the app manifest.
I am making a game in which the server has full control of the entire game.
This allows people to make their own multiplayer games very easily.
This game will also support Android.
Question, should this game be 2D or 3D?
Or should I make just 3D because people can fake 2D games using GUIs and other stuff?