Timer for mod - PLZ HELP

[KhanBhai]

so um I need some help with my mod...

wut I'm trying to do is that after every 10 min (20x10=200 ticks) it makes the player say something in chat.

this will run forever. this is wut I have so far but it not working. I recently got into java so IDK wut I'm doing so plz help.

I think that the code is accurate and should work but it don't.

 

public class Timer {

    private int timer = 0;

    @SubscribeEvent
    public void onPlayerTick(PlayerTickEvent evt)
    {
      tickCounter++;      
      if (timer == 200)
      {
          <MOD NAME>.getInstance().getMinecraft().thePlayer.sendChatMessage("10min passed bud");
          timer =0;
      }
      else {
          tickCounter =0;
      }
    }
    
}

 

[KhanBhai]

BTW im using 1.8.9

[Draco18s]

10 minutes is not 200 ticks, its 12000.

[diesieben07]

PlayerTickEvent fires twice per tick, for every player, on server and client. What you want is ClientTickEvent (also fires twice per tick, check TickEvent#phase). Stop using 1.8.9.

[jabelar]

The general idea is correct. However there are a couple Java things plus a couple Minecraft things that probably need to be fixed.

 

Java Stuff:

 

First of all, you have a private field called timer but you're incrementing something called tickCounter. Actually I'm not sure why Eclipse isn't warning about the fact that tickCounter isn't even declared, and also I'm not sure why it even would run for you at all. I think everywhere you have tickCounter you should replace with timer.

 

Minecraft Stuff:

 

How did you register the class as an event handler? Just annotating the method isn't enough. You need to register the whole class to the event bus. 

 

Also, as mentioned you only want the event to fire on the client. So you should use the client tick event. Since you reference the Minecraft class, you should also technically make sure that bit of code is client side only. There are a couple approaches to this:

1. Put the code with Minecraft into a method that runs through your proxy system. The concept of the proxy is very important in Minecraft modding. Basically it means you create a method with same name/parameters that has different code on client versus server. In this case, your client-side version would have the code you used, and the server side would just do nothing.
2. Alternatively you could make your whole event handling class client-side only (by annotating it as sided) and only register it on the client side. For the registration you could that again using the proxy, or you could switch to the annotation style of event handler registration and indicate that it is sided in the annotation.

If you haven't modded before, all the points about client versus server might be confusing, but it is worthwhile taking time to fully understand it as it is critical to bug-free modding.