I'm going to set aside Raylib for awhile. Possibly forever.
Last night I was working on the next game of the series. I wanted some physics, so I directed my AI to go ahead and get me some of that.
AI: And did I fail miserably?
Well, kind of. Not really. I realized I have neither the math background nor the interest required to handle the AI wrangling I'd need to get the inertia, mass, bounce, whatever working properly. Plus someone has already done it. Someone who probably liked it.
AI: So we're switching to an engine?
Yup. We're switching to an engine.
I was reading Reddit the other day and someone said they made a Flappy Bird clone and put it on the Play Store. They said they were making $50 a month on ad revenue.
https://www.reddit.com/r/raylib/comments/1kyfg1r/my_first_raylib_android_game_got_10k_downloads/
Now $50 a month is not a lot of money, but that's not the point. I've never made a dime off a personal project in my life. How cool that would be, to pay for a year's worth of the server that hosts this site with a game I made.
AI: Every developer's dream!
Every developer's dream.
Now a note on the Flappy Bird clone: they made it in Raylib. There is no reason I couldn't start targeting Android on top of the desktop and web builds I've already been doing.
But I want physics. And I don't want to learn physics.
AI: But you said you wanted to drive the bus!
Yeah, I wanna drive the bus. But I don't want to have to build the engine. Ha. Engine.
And so I'm going to try an engine that is suitable for desktop and the web - and was apparently built for Android?
AI: Yes, it started as a framework to help developers write Android games more easily using Java, without having to touch the Android SDK or Java boilerplate.
Well, I don't know what an SDK is but that's good enough for me. Next time you hear from me I'll probably be griping about toolchains again.
Something Developer Kit.
AI: It's Software Development Kit.
Close enough.