Just found a better way to do what I had in mind, requiring only two comman blocks. The first spawns a horse at the location of all snowballs with the name “Horse.” The next chained command block deletes all snowballs named “Horse.” When the player throws the snowball, the horse immediately spawns. No need to wait for the snowball to hit the ground or to detect age because it’s instantaneous.
How would you do that? Would it be through the scoreboard? Perhaps one could set a special tag to the entity that increments by one on the scoreboard every time the player spawns a new one by throwing the snowball?
I am trying to create a machine that spawns a tamed saddled horse when a player throws a snowball. I've seen some outdated similar videos like the one below, but they're for 1.8 and use "c=-1" to get the youngest entity. I've seen that "limit" replaces "c" now, but limit does not allow for negative values. How can I recreate the machine in the video, but for 1.13? How can I target the youngest entity?
I got started by watching YouTube tutorials for modding (a good up to date series for 1.12.2 can be found here by Loremaster). I also read the Minecraft code and copied it to make similar items/mobs. Reading code and learning how it works is a great way to learn too.
I am trying to search for key words and text in the Minecraft code, but searches only show matches in my own packages. However, when switching to any other workspace, the text finder works just fine. Any ideas of what setting I may have accidentally changed? I am modding in 1.12.2
I got everything to work! It's not a great way to do it, but it works. I used the "FMLNetworkEvent.ClientDisconnectionFromServerEvent," which works for clients on both dedicated and integrated servers.
To answer your question, I needed the client to delete some entity dynamic textures that are created when the player looks at my entity (see my ore sheep mod). I needed to delete these textures when logging out of a world, preventing a memory leak/refreshing the texures for a new world. This new event works, except that trying to delete textures in this event using "Minecraft.getMinecraft().getTextureManager().deleteTexture(/*texture here*/)" gives an error "no openGL in this thread" or something like that. I had to set a boolean to true in "FMLNetworkEvent.ClientDisconnectionFromServerEvent" and then to a boolean check in my entity's render class to delete the textures the next time it is triggered.
Like I said, it works now, but it is super messy! Ideally, I need to be able to delete the textures directly in the event "FMLNetworkEvent.ClientDisconnectionFromServerEvent" or a similar one.
I though it wouldn't be too difficult, but the packet doesn't seem to be received on the client side using "PlayerEvent.PlayerLoggedOut." It doesn't receive on the client of an integrated server or dedicated server. Any ideas? Here is my code:
@SubscribeEvent()
public void onLogOutServer(PlayerEvent.PlayerLoggedOutEvent event)
{
//TODO packet works server side, but client seems to "get away" before it receives the message...
ModOreSheep.INSTANCE.sendTo(new ClientResetPacket(true), (EntityPlayerMP) event.player);
}
Custom Packet and Handler: I assume that the "reset" boolean isn't necessary, but I wasn't sure if a message could be empty.
public class ClientResetPacket implements IMessage
{
boolean reset;
public ClientResetPacket()
{
System.out.println("ClientResetPacket ran!");
}
public ClientResetPacket(boolean canExecute)
{
this.reset = canExecute;
}
@Override
public void toBytes(ByteBuf buf)
{
buf.writeBoolean(reset);
}
@Override
public void fromBytes(ByteBuf buf)
{
buf.readBoolean();
}
//The params of the IMessageHandler are <REQ, REPLY>, meaning that the first is the packet you are receiving, and the second is the packet you are returning. The returned packet can be used as a "response" from a sent packet.
public static class ClientResetHandler implements IMessageHandler<ClientResetPacket, IMessage>
{
@Override
public IMessage onMessage(ClientResetPacket message, MessageContext ctx)
{
if (message.reset)
{
System.out.println("packet reset client");
/*method to reset client*/;
}
return null;
}
}
}
Error:
[08:53:56] [Netty Server IO #3/ERROR] [FML]: NetworkDispatcher exception
java.io.IOException: An established connection was aborted by the software in your host machine
at sun.nio.ch.SocketDispatcher.write0(Native Method) ~[?:1.8.0_101]
at sun.nio.ch.SocketDispatcher.write(Unknown Source) ~[?:1.8.0_101]
at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source) ~[?:1.8.0_101]
at sun.nio.ch.IOUtil.write(Unknown Source) ~[?:1.8.0_101]
at sun.nio.ch.SocketChannelImpl.write(Unknown Source) ~[?:1.8.0_101]
at io.netty.channel.socket.nio.NioSocketChannel.doWrite(NioSocketChannel.java:417) ~[NioSocketChannel.class:4.1.9.Final]
at io.netty.channel.AbstractChannel$AbstractUnsafe.flush0(AbstractChannel.java:856) ~[AbstractChannel$AbstractUnsafe.class:4.1.9.Final]
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.flush0(AbstractNioChannel.java:362) ~[AbstractNioChannel$AbstractNioUnsafe.class:4.1.9.Final]
at io.netty.channel.AbstractChannel$AbstractUnsafe.flush(AbstractChannel.java:823) ~[AbstractChannel$AbstractUnsafe.class:4.1.9.Final]
at io.netty.channel.DefaultChannelPipeline$HeadContext.flush(DefaultChannelPipeline.java:1296) ~[DefaultChannelPipeline$HeadContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush0(AbstractChannelHandlerContext.java:776) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush(AbstractChannelHandlerContext.java:768) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.flush(AbstractChannelHandlerContext.java:749) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.ChannelDuplexHandler.flush(ChannelDuplexHandler.java:117) ~[ChannelDuplexHandler.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush0(AbstractChannelHandlerContext.java:776) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush(AbstractChannelHandlerContext.java:768) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.flush(AbstractChannelHandlerContext.java:749) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.ChannelOutboundHandlerAdapter.flush(ChannelOutboundHandlerAdapter.java:115) ~[ChannelOutboundHandlerAdapter.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush0(AbstractChannelHandlerContext.java:776) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush(AbstractChannelHandlerContext.java:768) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.flush(AbstractChannelHandlerContext.java:749) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.ChannelOutboundHandlerAdapter.flush(ChannelOutboundHandlerAdapter.java:115) ~[ChannelOutboundHandlerAdapter.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush0(AbstractChannelHandlerContext.java:776) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush(AbstractChannelHandlerContext.java:768) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.flush(AbstractChannelHandlerContext.java:749) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.ChannelOutboundHandlerAdapter.flush(ChannelOutboundHandlerAdapter.java:115) ~[ChannelOutboundHandlerAdapter.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush0(AbstractChannelHandlerContext.java:776) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush(AbstractChannelHandlerContext.java:768) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.flush(AbstractChannelHandlerContext.java:749) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at net.minecraftforge.fml.common.network.handshake.NetworkDispatcher.flush(NetworkDispatcher.java:559) ~[NetworkDispatcher.class:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush0(AbstractChannelHandlerContext.java:776) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:802) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:814) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:794) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:831) ~[AbstractChannelHandlerContext.class:4.1.9.Final]
at io.netty.channel.DefaultChannelPipeline.writeAndFlush(DefaultChannelPipeline.java:1032) ~[DefaultChannelPipeline.class:4.1.9.Final]
at io.netty.channel.AbstractChannel.writeAndFlush(AbstractChannel.java:296) ~[AbstractChannel.class:4.1.9.Final]
at net.minecraft.network.NetworkManager$4.run(NetworkManager.java:261) [NetworkManager$4.class:?]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [AbstractEventExecutor.class:4.1.9.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403) [SingleThreadEventExecutor.class:4.1.9.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:442) [NioEventLoop.class:4.1.9.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858) [SingleThreadEventExecutor$5.class:4.1.9.Final]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_101]
In the output, the a dedicated server outputs "ClientResetPacket ran!" and somtimes the error above, but nothing on an integrated server. In both, the client does not output "packet reset client." is there a problem with the "PlayerEvent.PlayerLoggedOutEvent'" event or is there a problem with my code? Thanks!
I've noticed that in the Event class, there is a ListenerList. Would it be possible in the WorldEvent.Unload event to remove the listeners "DimensionManager.unloadWorlds" and ForgeInternalHandler.onDimensionsUnload(Unload)?" That's what I need mostly.
"PlayerEvent.PlayerLoggedOut" works great for the server side, but some of the values I need to reset include textures and"PlayerEvent.PlayerLoggedOut" doesn't run a client thread. Thanks for the idea though! Are there any other events, or will I just have to use that one and use a packet from server to client?
I am looking for a way to reset specific values when a player logs out of his world on a server or client. The event needs to fire on client and server sides to reset these values. The method WorldEvent.Unload works great, except that it is also fired when the player's dimension changes. Is there a different way I can do this? Thanks!
It works now! For some reason "Boolean.getBoolean(args[0])" always returned false, even when args[0] was "true." Not sure why, but I replaced it with the below code and it worked:
if (args[0].equals("true"))
{
ModConfig.IgnoreGameRuleMobGriefing = true;
}
else if (args[0].equals("false"))
{
ModConfig.IgnoreGameRuleMobGriefing = false;
}
Also, not sure why, but I didn't have to send a packet to each client either, it works just fine without it. Yay!
0
Just found a better way to do what I had in mind, requiring only two comman blocks. The first spawns a horse at the location of all snowballs with the name “Horse.” The next chained command block deletes all snowballs named “Horse.” When the player throws the snowball, the horse immediately spawns. No need to wait for the snowball to hit the ground or to detect age because it’s instantaneous.
Thanks for the help!
0
How would you do that? Would it be through the scoreboard? Perhaps one could set a special tag to the entity that increments by one on the scoreboard every time the player spawns a new one by throwing the snowball?
0
Hello all!
I am trying to create a machine that spawns a tamed saddled horse when a player throws a snowball. I've seen some outdated similar videos like the one below, but they're for 1.8 and use "c=-1" to get the youngest entity. I've seen that "limit" replaces "c" now, but limit does not allow for negative values. How can I recreate the machine in the video, but for 1.13? How can I target the youngest entity?
Thanks in advance!
0
I got started by watching YouTube tutorials for modding (a good up to date series for 1.12.2 can be found here by Loremaster). I also read the Minecraft code and copied it to make similar items/mobs. Reading code and learning how it works is a great way to learn too.
0
The problem is in your Reference.class. You misspelled "doodle" as "dodle" for both the client and common proxy references. They should read:
public static final String CLIENT_PROXY_CLASS = "com.tiki_doodle_p.HighSchoolDxD.proxy.ClientProxy";
public static final String COMMON_PROXY_CLASS = "com.tiki_doodle_p.HighSchoolDxD.proxy.CommonProxy";
Hope that helps!
0
Hello all!
I am trying to search for key words and text in the Minecraft code, but searches only show matches in my own packages. However, when switching to any other workspace, the text finder works just fine. Any ideas of what setting I may have accidentally changed? I am modding in 1.12.2
2
Version 4.0.0 for Minecraft 1.12.2 is out! Happy mining!
1
An update for 1.12.2 is coming out today! Get excited!
0
I got everything to work! It's not a great way to do it, but it works. I used the "FMLNetworkEvent.ClientDisconnectionFromServerEvent," which works for clients on both dedicated and integrated servers.
To answer your question, I needed the client to delete some entity dynamic textures that are created when the player looks at my entity (see my ore sheep mod). I needed to delete these textures when logging out of a world, preventing a memory leak/refreshing the texures for a new world. This new event works, except that trying to delete textures in this event using "Minecraft.getMinecraft().getTextureManager().deleteTexture(/*texture here*/)" gives an error "no openGL in this thread" or something like that. I had to set a boolean to true in "FMLNetworkEvent.ClientDisconnectionFromServerEvent" and then to a boolean check in my entity's render class to delete the textures the next time it is triggered.
Like I said, it works now, but it is super messy! Ideally, I need to be able to delete the textures directly in the event "FMLNetworkEvent.ClientDisconnectionFromServerEvent" or a similar one.
Thanks for your help!
0
I though it wouldn't be too difficult, but the packet doesn't seem to be received on the client side using "PlayerEvent.PlayerLoggedOut." It doesn't receive on the client of an integrated server or dedicated server. Any ideas? Here is my code:
Mod Class:
@EventHandler public void load(FMLInitializationEvent event) { INSTANCE.registerMessage(ClientResetHandler.class, ClientResetPacket.class, 1, Side.CLIENT); MinecraftForge.EVENT_BUS.register(new OreSheepEventHandler()); }Packet Handler Class:
@SubscribeEvent() public void onLogOutServer(PlayerEvent.PlayerLoggedOutEvent event) { //TODO packet works server side, but client seems to "get away" before it receives the message... ModOreSheep.INSTANCE.sendTo(new ClientResetPacket(true), (EntityPlayerMP) event.player); }Custom Packet and Handler: I assume that the "reset" boolean isn't necessary, but I wasn't sure if a message could be empty.
public class ClientResetPacket implements IMessage { boolean reset; public ClientResetPacket() { System.out.println("ClientResetPacket ran!"); } public ClientResetPacket(boolean canExecute) { this.reset = canExecute; } @Override public void toBytes(ByteBuf buf) { buf.writeBoolean(reset); } @Override public void fromBytes(ByteBuf buf) { buf.readBoolean(); } //The params of the IMessageHandler are <REQ, REPLY>, meaning that the first is the packet you are receiving, and the second is the packet you are returning. The returned packet can be used as a "response" from a sent packet. public static class ClientResetHandler implements IMessageHandler<ClientResetPacket, IMessage> { @Override public IMessage onMessage(ClientResetPacket message, MessageContext ctx) { if (message.reset) { System.out.println("packet reset client"); /*method to reset client*/; } return null; } } }Error:
In the output, the a dedicated server outputs "ClientResetPacket ran!" and somtimes the error above, but nothing on an integrated server. In both, the client does not output "packet reset client." is there a problem with the "PlayerEvent.PlayerLoggedOutEvent'" event or is there a problem with my code? Thanks!
0
I've noticed that in the Event class, there is a ListenerList. Would it be possible in the WorldEvent.Unload event to remove the listeners "DimensionManager.unloadWorlds" and ForgeInternalHandler.onDimensionsUnload(Unload)?" That's what I need mostly.
0
"PlayerEvent.PlayerLoggedOut" works great for the server side, but some of the values I need to reset include textures and"PlayerEvent.PlayerLoggedOut" doesn't run a client thread. Thanks for the idea though! Are there any other events, or will I just have to use that one and use a packet from server to client?
0
I am looking for a way to reset specific values when a player logs out of his world on a server or client. The event needs to fire on client and server sides to reset these values. The method WorldEvent.Unload works great, except that it is also fired when the player's dimension changes. Is there a different way I can do this? Thanks!
0
That makes sense. Thanks!
0
It works now! For some reason "Boolean.getBoolean(args[0])" always returned false, even when args[0] was "true." Not sure why, but I replaced it with the below code and it worked:
if (args[0].equals("true")) { ModConfig.IgnoreGameRuleMobGriefing = true; } else if (args[0].equals("false")) { ModConfig.IgnoreGameRuleMobGriefing = false; }Also, not sure why, but I didn't have to send a packet to each client either, it works just fine without it. Yay!