blockstat | one lab environment at upload time | Continuous Deployment library

There's some good docs on writing lint rules on TypeScript-ESLint's website which can help walk you through custom lint rules

https://typescript-eslint.io/docs/development/custom-rules

You can also use our playground to interrogate the AST and learn its structure so that you can write appropriate selectors

https://typescript-eslint.io/play#showAST=es

Update: I managed to fix it! What I did was make a mixin into World#setBlockState(BlockPos, BlockState, int) and check if the flags were some number I set (999 in my case), and if it where I canceled the method execution right after the block state was set, saving huge amounts of time when placing a lot of blocks. However, it did not send the chunks to the player so what you have to do is simply send all the chunks you changed to the player, I did this by storing all the chunks I changed and for each player in the world I sent a ChunkDataS2CPacket with the new chunk to the player, which fixed my problem entirely, it works like a charm :D

EDIT: It also does not do block updates/lighting updates

Answering my own question.

Instead of using event.getCategory().equals(SomeBiomeCategory) in the if statement in the OreGen class you should use event.getName().equals(YourModBiomeInit.BiomeName.getId(). Because event.getCategory().equals(SomeBiomeCategory) gets the category of the biome currently generating whilst event.getName().equals(YourModBiomeInit.BiomeName.getId() gets the registered name (or id).

So the if statement would look something like this :

If you look closely at that for statement, you'll see that it's body consists only of ;. That's an empty statement. You'd get the same effect with, say,

The problem was that java version mismatch.

There were several version of java that was installed and it was conflicting one another .

So i uninstalled all the versions and then installed just a single java11 version.

Also ran the jmeter using java -jar ApacheJMeter.jar

this made sure that it was using the version of java that i was passing it but not picking it from random location.

Such as you mentionned, it's on the client-side. So, you can change everything, it will only be visual.

It replaced the block when right-click because the server send the real block present on the world (instead of visual one).

If you want to do something like that, it can be difficult. All client that are manually placing block on server are cheat, because they are making something that is not allowed in basic minecraft.

But, maybe there is possibilities :

1. Use event to change the block that will be placed, and instead of placing the default one and change it after, you can directly change it on the server.

2. Run a command to change the block such as /setblock (wiki)

Apparently, it may be a problem with the babel. Copy the folder @babel (specifically @babel/core) that is in the node_modules of a working project into the new project and it runs without problems.

It may be due to an update they did a couple of hours ago.

You can also remove the current @babel/core from the package.json and install this version npm install --save-dev @babel/core@latest.

Or use this:
@babel file: https://drive.google.com/file/d/1-z_4H_z4x075unZqZD41WYUwY_hsrKox/view.

Or replace the following codes in your package.json file then npm install.

this is a known issue caused by a bug in a newly released version of babel. it will impact all new react-native and expo apps. you can resolve it with yarn resolutions in a new project:

I always find it easier to split the line: