poopoodice

For entities to do "AI tick logic". e.g. movements not called when it is no longer "alive"

Actually I have a one last question, if I managed to compress the images to lower qualities, e.g. size of around 100 KB or even less (hopefully not!), will it still be an issue to communicate them with clients? Or it really depends on the situation (user end)?

Was curious more on the custom server i/o (without using resource packs), and the image transfer since the image will be way larger than a map does. In fact I just realised that some of the images are around 4~5 MB... probably not a good idea to transfer them then... sorry for bothering and thanks for the help.

Hi, first of all, thanks for the reply. How about only send the data when requested? For example the client can decide whether they want to requesting and get the images. I'm also not considering using external links and such, maybe something like how maps are handled?

Normally this should (probably?) be done with resource packs but it is not something I like much. So, as title, how viable, is reading resources, e.g. pictures and images from the server and send them to clients? Thanks in advance.

I'm honestly not sure how Vanilla handle that with potion, but maybe try register your own ItemColors, then you can give different tint index to the different cubes, or more specifically, faces. Those values will be given when asking you to calculate your own colour. For example, I have north tint index 3, south index 2, then I will have something like: return tintIndex == 2 ? red : blue; or something like that, depends on what you want

Hi, what's the trade-off here? I've recently used java model for blocks (TESR) to render lots of repeating units in a block instead of direct rendering call, is it not recommended? And how? Thanks.

There is writeToNBT and readFromNBT?

You can achieve it using java models (more specific rotations), like tridents and shields.

https://github.com/Tucky143/Buzz/blob/main/src/main/java/example/examplemod/villager/ModVillagers.java#L35 I think you need to use the SRGG nname instead of mapped ones Ah, wrong thread.

You should be passing your own menu type into super

TE = Tile Entity, or Block Entity in recent versions. I believe you need one for yourself (both MenuType and BlockEntityType) since certain TE/BEs only allows certain blocks (e.g. Vanilla Furnace TE/BE does not work on a custom furnace). It's also better to post your TE/BE and Menu class along with where and how you register your custom types.

I can find it in both latest 1.18 and 1.19 Forge version, right below the reach distance.

The warning means the block and the TE does not match, where and how do you register your TE? Is your block added to the list when constructing your TE?

I don't know what a TickHandler is, but you can store the stack in the tile entity, after a duration (maybe just an int field increment every tick), and spawn after time expires. Check BlockEntityTicker, or ITickableTileEntity in older versions (1.16/1.18? I can't remember.)

Can you find your sound in command /playsound? Is there any error in the log? Have you configured your sound in sounds.json? Is your sound in the correct directory? Is your sound low-volumed? Is your sound in .ogg format?

Because towards North is -z, so the origin in on upper left corner. Easy way is just flip the direction in getShape, or just swap them manually.

Use ListNBT/ListTag

Rotate the pose stack (e.g. PoseStack#mulPose(Vector3f.ZP.rotateDegrees(45)), not sure about the names), or just put their vertexes at the desired location.

You can use MaterialColor#getPackedId and provide the brightness then.

You need to specify the AT file in your build.gradle, and reimport/refresh the gradle.

Maybe something's wrong with your packet?

Access Transformers allows you do get rid of the final modifier.

You are directly using the plain material colour of the block currrently. If you want anything more

Just noticed some potential problems: 1. You are always using the same instance of DynamicTexture, but closes/dispose it every update. 2. RenderGameOverlayEvent.Post is called multiple times every render tick, it means you are refreshing your map every 1~2 seconds, depend on the render rate. 3. Continue with 2., you are rendering multiple times (it gets called whenever an element is being rendered, e.g. health bar, crosshair, helmet... if you are using 1.16, otherwise you need to register your overlay instead of using the event) every frame, check for ElementType.ALL (or something similar) and do the render.