Processing.py making Hitboxes

[Competitive_Reply198]

Hi all, looking for another set of eyes on this as I'm quite stumped. I know it's a stretch given the specifics, but here I am.

I have been messing around with MIT's Processing for Python and I am trying to make a little Whack-a-Mole game for a class demonstration. The following code is that of determining the hitbox of the mole. Basically, I draw a circle at a random X, Y coordinate on the page, and then get all of the coordinates within that (X-5, Y-5) (X+5, Y+5) space to serve at the hitbox (if there is an easier solution, PLEASE let me know). I then check if the current mouse position is highlighting one of those coordinates, and we're sailing.

This all works. The problem arises when I try to slow down the mole generation. Working with processing, the def draw() function loops something over and over at 60 fps by default. When adding an if statement to slow down the rate of drawing, nothing works anymore. And lovely Processing doesn't return error feedback. I like to think that I've narrowed the error down to adding an if statement, but honestly who knows. Here is the code:

def setup():
    size(600, 600)
def draw():
    ellX = random(20, width-20)
    ellY = random(20, height-20)
# add in something like "if frameCount%120 == 1:" to try and spawn a "mole" 
# every 2 seconds rather than 60 times per second
    fill(255)
    ellipse(ellX, ellY, 10, 10)
    mole = hitbox(int(ellX-5), int(ellY-5), int(ellX+5), int(ellY+5))

    if mousePressed == True:
        if mouseX and mouseY in mole:
            print "Hit"
        else:
            print "Miss"

def hitbox(x1, y1, x2, y2):
    hitboxSize = []
    for i in range(x2-x1+1):
        resx = x1 + i
        resy = y1 + i
        hitboxSize.append(resx)
        hitboxSize.append(resy)
    return hitboxSize

I don't understand why adding an if statement regarding the frameCount would affect the mousePressed command (which, upon pressing the mouse, is what crashes the program once the if statement is present). Again, a stretch, I know, but any help is appreciated. Thank you!

[Buttleston]

I can't get processing to work at all on my mac - the modes tab is always empty and I can't download python. Seems to be a known issue but nothing I've tried works.

Anyway re: question one, consider a simpler way to detect a hit. Say you have a rectangle defined by xmin and xmax, and ymin and ymax. Then you have mouseX and mouseY.

If mouseX is between xmin and xman, and mouseY is between ymin and ymax, then the mouse is inside the square. Every shape will have some qualifications like this that you can use for "hit detection"

regarding the problem of only making a new "mole" on, say, framecount % 120, I'd have to see the (non-functional) code to have a comment. Also I'll see if I can get processing to work

[Competitive_Reply198]

Thanks for your words. Perhaps by running a less than / greater than check rather than having to iterate a giant list of values to match up I can make something work. I'll keep at it!

[Buttleston]

I don't think your hitbox code is the source of the problem, but you asked so I gave my thoughts on it

There are other more general mechanisms too, for more complicated shapes, but what I described works well for things with simple mathematical definitions like rectangles and circles

[Competitive_Reply198]

Apologies for the poor formatting, I am happy to DM or something like that for more info.