LOSS404
New member
Thank you for the warning, i do appreciate that. However my aim was to begin development within 4.0 and had been awaiting the Linux version for some time now. I was attempting to be proactive in facilitating (if possible for me, I'm no expert) with helping to keep the Linux version closer to the latest windows build. ^_^
So I do understand your concern and it is definitely worth anyone to be aware of these facts, so as they do not encounter potential compatibility issues.
I should mention that appimages being updated is something a user manual does (or can do, if the option is available or the appimage includes the update information.)
and for updating the appimage, its something that seems rather deliberate and another layer obfuscation compared to a normal Linux software manager or package manager.
basically I'm trying to say as far as i know it would be fairly deliberate to update (yet still not too difficult for an average user to self perform.) but before i forget, it also defaults with version control by saving a copy of the "old"/former appimage.
but anyway, thank you again, for cautioning me about the potential compatibility problems, as well as for letting me know about the current backwards compatibility.
based upon what all you've told me, i would make the guess that the current 3.0 6391 appimage is able to load 4.0 for this backward compatibility reason. however that is still just a guess.
hello
thanks, & heck yes, i love openbor. i think about it almost every day haha. I used mugen a rather long while back. which i thought it was great. however i look at openbor and my mind sees it making basicly perfect sense. as in i think its well written, intuitive, easy to read, and i often ffind myself day dreaming about many cool possibilities that can be done in/with OpenBOR. Sometimes i admittedly forget a bit as the reality & fantasy blur, but the hype is real for me. Thanks for saying hey, it's a great engine and i hope more people find and enjoy it too!
