LoveLive is a library I've made to make the process of editing game variables live a little nicer. Solutions for this exist, but I wanted to go for something that's simple to use and implement, and something that can show immediate output of a change in value to streamline the process a bit. If you have any questions as to how it's used, feel free to ask. Any suggestions or bug reports are appreciated too.
I imagine this isn't too relevant to anyone's current usage, but I updated the library to v0.2.0 with two main changes:
The mouse being bounded to the window, and therefore making you unable to change values is fixed.
The parameters for the UI font are changed to use love font objects instead of paths and sizes.
I have yet to actually test-run it in my other application, but one thing I've found is a little bothersome is having to loop through collections of objects to edit them as a result of a change in LoveLive. It makes me think whether or not there's an easier way to do that. I'll see if I can figure something.
That's an interesting thing to think about. An interesting thing I'll be thinking about.
So, perhaps, maybe another program entirely, where you'll somehow define the variables from there? Maybe using Lua environment trickery? Sounds like fun.
There is/was a lib that is basically an external console for a löve game, that ran in the browser. Don't think one can be much more transparent than requiring that and calling its update function, and when the time comes, deleting two lines from the code.
Still, i might find use for this lib soon.
Nevertheless, good luck on thinking up something!
Me and my stuff True Neutral Aspirant. Why, yes, i do indeed enjoy sarcastically correcting others when they make the most blatant of spelling mistakes. No bullying or trolling the innocent tho.
You're most likely referring to lovecat, which is similar to lovebird, but closer to LoveLive in purpose.
As far as I can tell... lovecat isn't all too hot when it comes to transparency. That's pretty much the one thing I wanted to achieve here: make it easy to use and easy to implement. Not sure if removal (aside from aforementioned solutions, which I'm already prototyping to some extent) can be done all that cleanly.
The simple fact that its console stacks duplicate messages allows me to quickly/lazily debug things.
The love console isn't so useful with all that spam.
Also it'll find all the global variables you leak by forgetting to use local.
Real-time variable inspection is great for debugging
And it's easy and convenient to use.
