Discussions

The Greenfoot class method 'mousePressed' only returns true when a mouse button goes from an unpressed state to a pressed state. It does not return true if there is no change in the state of a button. Therefore, your 'else' block needs to be removed and you need to use another set of conditions for detecting when the state is changed back: <Code Omitted>would work by itself, if you are okay with the possibility that it could be the other mouse button that is released. <Code Omitted>will pr

To detect, not the state of, but a change in the state of a key, whether it be the pressing or the releasing, you will need an instance boolean field to track the state of the key: <Code Omitted>

With the code Super_Hippo supplied, you can just remove line 23 (from your last posting of the Roomba class). If you use '/**', with two asterisks, for your multi-line comment blocks (whether they are actually multi-line or not), your code will display better here.

Still collision detection -- none the less. You were saying to allow a move to the right if not touching Door object or DoorPost object. That is the same as "don't allow a move to the right if touching both". Actually, I think you should probably use the AND conjuction, '&&', not the OR conjunction, '||', there at line 65 of the Pengu class (if not touching one AND not touching the other). At any rate, my point is that it does not matter that you used NOT, '!'; it is still collision checking.

By convention, class names begin with uppercase letters (I will use the name Word since it will display the word (with underscores -- or not). This is a brief summary of what is needed only to sow you an example:

The field type on line 6 should be 'boolean' -- with a lowercase 'b'. Using an uppercase 'B' will have the field treated as an Object field reference of type Boolean instead of as a primitive type boolean field. As an object reference, its default value is 'null'; as a primitive field, it is assigned a value of 'false' by default. Also, all your multi-line comments should begin with '/**', using two asterisks. That way, at least in the postings here, some of your code lines will not look like comment lines because of their text color.

Ok, I see where I went wrong. I cut Line 23, created an act method in my World class and added the spawnPuffer method to it, and adjusted the If statement condition in order to slow down the spawning rate since at 20% it seemed ridiculously fast. I also commented out line 83 and it works as intended still, that line may have been redundant. Thanks for the help, once again lol.

Ok, makes sense. Thanks again!

Ok, thank you!

I kind of figured that the Volume class was for displaying the current volume -- just wanted to be sure of that and that there was nothing there that might influence the current volume. From your last post, it appears that there may be a bug in the implementation greenfoot has for sound volume with your version.

Never Mind I used a different thing and figured it out

Thanks guy :)

Try <Code Omitted>Your line 12 needs to be moved outside the method, though.

Use instance 'private int' fields in your world class and add a 'public int getInteger_()' for each one so the actors can access the value of them with (using MyWorld as world class name): <Code Omitted>You can change the underscores simulateously to whatever, for example 'A', 'B', 'C', ..., for each field. Actually, you can name they whatever you want, I just wanted to point out that all underscored names are referring to the same field.