Jump to content

Recommended Posts

Posted

Whenever your code doesn't do what you expect, you need to do standard debugging. That starts with observing the execution. You have a couple options, you can set a breakpoint on the onImpact() method and run Eclipse in debugger mode then step through and watch what is happening, or alternatively you can add System.out.println() or logger statements in your code to print out to console or log information that helps you understand what is happening.

 

You need to first determine if your onImpact() method is even being called, and if it is being called trace through to understand why it isn't having effect. If you use one of the techniques above it should be quickly obvious what is wrong.

Check out my tutorials here: http://jabelarminecraft.blogspot.com/

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.