LÖVE

kikito wrote:

tsturzl wrote:It really seems like what he's doing is actually easier, IMO. Really the concept isn't that hard to grasp...

I was under the impression that he was not yet *doing* anything, but thinking about ways of doing things, and asking questions.

Stateful provides a couple tools to deal with this complexity: first, states are stackable (so megaman can be "jumping" and "wood-powered" at the same time), but the code has no "ifs": instead, methods are overriden in certain order.

Second, one state can "inherit" from another, so if two states are "mostly the same except from one bit" the code isn't duplicated; when you change the parent, you don't have to remember changing the child.

Finally, there are callbacks that are automatically called every time a state is entered/exited (or pushed/popped from the state stack). If you need some initialization code to be called every time that megaman changes from one other power to "IcePower", Stateful makes sure that that method is called; you don't have to remember it.

I'm not saying it is the ideal solution, but I'm certain it's worth considering.

tsturzl wrote:Using stateful.lua just seems like another library to learn.

I don't know what to make of that phrase. You seem to be implying that using libraries, or learning to use them, is a bad thing.

teh8bits wrote:I know I'm new here and to Lua in general, but wouldn't it just be easiest to have a few booleans and avoid nested ifs? I know from Java experience it wouldn't be hard to make some cut off boolean so if he gets hit the next tick he would stop firing and start getting hurt.
Better yet just have in the firing animation method if ~= hurting

teh8bits wrote:What do you mean by standardizing? Like just having all entities that need a variable depicting if they're on the ground have a variable named onGround? (same names throughout?)

sanjiv wrote:Thanks guys, for all your help

Given the tactic of interchanging tables, will I be able to use sprite-sheets to store images? I know how to draw from them, but I can't seem to figure out a way to store those images as variables. I guess I'd have to simply store their quads in tables? It seems like I'd be clogging up my memory doing this.

@ stateful: I have absolutely no interest in building my own class/object orientation system, but I confess I haven't learned how to use other people's libraries yet. Doing things the simple stupid way for now gives me smaller victories more often, and I think is an important learning process for a beginner like me.

But yeah, things have already gotten hairy.

@ booleans: Are you talking about setting up

Code: Select all

jumping = false
shooting=false

if jumping and shooting then
     jumpAndShoot()
end

sanjiv wrote:so with something like this

where the different sprites may be of different sizes, is anim8 my best choice out of the ones you listed?

On the wiki entry for new quad (https://love2d.org/wiki/love.graphics.newQuad), it suggests that create a specific resource once and store it somewhere it can be reused. How would one do that? I didn't easily come across an answer to this, but it seems like it would be standard knowledge.

tsturzl wrote:
I agree somewhat with this. However I think its better to just do it objectively with tables, this way you could make an array full on different characters that you could swap between in real time, not to mention its good practice. This way you can keep your players health, x/y coords, image object, and other relative variables inside your player object.

player={}
player.x=10 --x
player.y=10 --y
player.s=10 --speed
player.form='A' -- can switch between 'A' and 'B'


formA={}
function formA.move(dt)
     player.x=player.x+player.s*dt
end

formB={}
function formB.move(dt)
     player.y=player.y+player.s*dt
end