About the casual stuff, yeah. Makes sense. No point in reinventing the wheel. However, API's don't really seem to be my forte. As I still woudn't know what to create an API for.Try to find a unique but interesting game. Casual shit like BedWars, ... you should not develop. There is to much of it. A good idea is to code some backend stuff for developers. Publish some useful API's.
Discord/Teamspeak would be possible. But what should they be able to control? As there are already a ton of plugins that do this like DiscordSRVExamples: A simple Discord/Teamspeak API (+ control it from your mc sever or whatever) , Data Management, Networking/Communication, ...
I've been thinking about using some of my server projects and puting them on <insert service here>. Maybe I could do that.Make a plugin that YOU would want to use. If you've never built a plugin before, you may quickly lose interest in the project unless you have a personal use for it.
Pick something small and with a clearly defined goal so you don't end up working on it for a year and feeling like you've not made any progress.
As long as you didn't have an agreement with those servers to not share their plugins, that could be a good way to kickstart your workI've been thinking about using some of my server projects and puting them on <insert service here>. Maybe I could do that.
