Mod for multiplayer on client-side only?

[Kozz]

I'm attempting to implement a very simple mod for use (by myself) on a multiplayer server.

 

It's purpose: Keep a count of specific blocks I've acquired, render that information on the screen.

• Event: Player has picked up a block
  • Check if the block is a nether quartz (I'm using silk touch).
    • Add it to a totalNetherQuartz variable, which is later rendered to the screen.

 

Simple, right?

 

The problem: Runs fine on single-player; doesn't run on multiplayer. 

• I understand server-side vs. client-side; however, I am unable to find a way to avoid using the server-side.
  • Yes, I have looked at the docs and tutorials. The docs are sparse; tutorials are outdated (MC modding seems to have changed quite significantly in 1.13).

 

The code:

 

ExampleMod.java

@Mod("Profit Counter")
public class ExampleMod
{
  public ExampleMod() {
    MinecraftForge.EVENT_BUS.register(this);

    // Register my custom event handler.
    EventHandler handler = new EventHandler();
    MinecraftForge.EVENT_BUS.register(handler);
  }
}

 

EventHandler.java

public class EventHandler {
  private int totalNetherQuartz = 0;

  @SubscribeEvent
  public void onPlayerPickup(EntityItemPickupEvent event) {
    EntityItem item = event.getItem();
    if (item.getName().toString().contains("nether_quartz_ore")) { // I'm sure there's a better way to check for this, but this functions.
      totalNetherQuartz += 1;
    }
  }

  @SubscribeEvent
  public void onRender(TickEvent.RenderTickEvent event) {
    if (Minecraft.getInstance().isGameFocused()) {
      Minecraft.getInstance().fontRenderer.drawStringWithShadow("Testing", 5, 5, 0xffFFFFFF); // This runs client-side, before even connecting.
      Minecraft.getInstance().fontRenderer.drawStringWithShadow(Integer.toString(totalNetherQuartz), 15, 5, 0xffFFFFFF); // Changes in single-player; does not work in multiplayer.
    }
  }
}

 

 

What steps must I take in order to get this working on a multiplayer server?

• Before you scream "client-side proxy" at me - please explain (or show me where I can find) how to set this up, since the tutorials for doing this in 1.12 no longer work, and the docs explain absolutely nothing other than the fact that you need one.

Edited March 26, 2019 by Kozz

[Draco18s]

What you're probably missing is the declaration that tells Forge "this is client only."

Its part of the @mod annotation, but I don't remember the necessary syntax.

[Cadiboo]

@Mod(clientSideOnly=true)

[Cadiboo]

  On 3/26/2019 at 10:16 PM, Kozz said:

Before you scream "client-side proxy" at me - please explain (or show me where I can find) how to set this up, since the tutorials for doing this in 1.12 no longer work, and the docs explain absolutely nothing other than the fact that you need one.

Expand  

public static final IProxy PROXY = DistExecutor.executeForDist(()->()->new ClientProxy(), ()->()->new ServerProxy());

[Kozz]

  On 3/27/2019 at 2:10 AM, Draco18s said:

What you're probably missing is the declaration that tells Forge "this is client only."

Its part of the @mod annotation, but I don't remember the necessary syntax.

Expand  

 

  On 3/27/2019 at 2:47 AM, Cadiboo said:

public static final IProxy PROXY = DistExecutor.executeForDist(()->()->new ClientProxy(), ()->()->new ServerProxy());

Expand  

 

When I call "@Mod", the only parameter it will accept is a String.

 

This works fine:

@Mod("test")

 

If I try:

@Mod(modid="test")

Or 

@Mod(clientSideOnly = true)

I get a "Cannot resolve method 'modid'" or "Cannot resolve method 'clientSideOnly'"

Why is this?

Edited March 27, 2019 by Kozz

[DaemonUmbra]

@Mod only takes the Mod ID in 1.13.2

All the rest goes in the mods.toml, however to my knowledge clientSideOnly and serverSideOnly have not been carried over, I believe because they were already legacy and essentially deprecated without being marked so.

[Kozz]

  On 3/27/2019 at 3:55 AM, DaemonUmbra said:

@Mod only takes the Mod ID in 1.13.2

essentially deprecated without being marked so.

Expand  

 

This is the kind of stuff that stresses me out!

It seems any new modder like me has come into a rough time... heck, it seems like a lot of experienced modders are even having trouble ATM.

 

Do you have any recommendation for how I can figure this out?

[DaemonUmbra]

Without seeing all your code I can make suggestions but honestly I'd rather test them myself before I suggest them, is your code on GitHub?

[Kozz]

  On 3/27/2019 at 4:08 AM, DaemonUmbra said:

Without seeing all your code I can make suggestions but honestly I'd rather test them myself before I suggest them, is your code on GitHub?

Expand  

You're looking at all the source code

 

It's just the default example mod (hence class ExampleMod) with one new class added, which is listed.

I started simple... which is still too complicated for me I guess.

No point in me adding any more until I can get this figured out.

[Kozz]

I'm currently reading this thread, this user is facing the same issue as me.

 

Apparently my issue is simply trying to use a server side event on client-side only.

Even with a client side proxy, or a "@Mod(clientSideOnly = true)", it appears this wouldn't work (although I may be wrong.)

 

I need a client-side event I can use in order to determine how much of a specific item I have gathered.

[DaemonUmbra]

I think I know how this can be done, but I need to check before I put my foot in my mouth

[Kozz]

  On 3/27/2019 at 4:17 AM, DaemonUmbra said:

I think I know how this can be done, but I need to check before I put my foot in my mouth

Expand  

 

Let me know if you figure anything out please!

[DaemonUmbra]

There is no way to do this purely client-side.

There is an !isRemote guard before this event would ever be on the (logical)client.

 

Because this cannot be done purely client-side you would also need to get into packets to get it working with the way things stand.

[Krevik]

  On 3/27/2019 at 2:10 AM, Draco18s said:

What you're probably missing is the declaration that tells Forge "this is client only."

Its part of the @mod annotation, but I don't remember the necessary syntax.

Expand  

it's @OnlyIn(Dist.CLIENT) I think.

Edited March 27, 2019 by Krevik

[DaemonUmbra]

  On 3/27/2019 at 5:52 AM, Krevik said:

it's @OnlyIn(Dist.CLIENT) I think.

Expand  

No.

That is not a magic annotation that makes your code sided, it is an annotation that will cause a crash if a class annotated with it is loaded on the side other than what is specified in the annotation.

[Krevik]

  On 3/27/2019 at 6:04 AM, DaemonUmbra said:

No.

That is not a magic annotation that makes your code sided, it is an annotation that will cause a crash if a class annotated with it is loaded on the side other than what is specified in the annotation.

Expand  

Ohh thank you, I didn't know actually

[Draco18s]

  On 3/27/2019 at 3:57 AM, Kozz said:

It seems any new modder like me has come into a rough time... heck, it seems like a lot of experienced modders are even having trouble ATM.

Expand  

I mean...its still in beta...

What'd you expect?

[Kozz]

  On 3/27/2019 at 1:20 PM, Draco18s said:

I mean...its still in beta...

What'd you expect?

Expand  

 

Solid documentation is what I'd expect.

Detailed descriptions of every class and method... It's pretty standard.

Beta is no excuse not to have this. They don't provide it for old methods either.

 

Honestly, their documentation is more like a wiki page.

An outdated one at that.

I followed the docs step-by-step for setting up the workspace, only to find the steps they provide on the FIRST PAGE are outdated, so I had to turn to the forums for that too.

Edited March 27, 2019 by Kozz

[DaemonUmbra]

Free and open source project with relatively few people working on it IN THEIR SPARE TIME.

If you are unhappy with the documentation, learn the code and document it yourself, the main crew are a bit preoccupied with getting everything back up and running.