Leaderboard

Use the BlockBreakEvent Get the player's lookVec Do some vector math Break some more blocks (you may wish to do so by first firing off new BlockBreakEvents so that your pickaxe can't break blocks that are in protected areas (other mods cancelling the event, if so, don't break the block) and you will need to insure that when your own event handler is fired again for these positions that you don't do anything).

I was messing with this a little myself, and made a little test thingy while I was playing with it. https://github.com/Ugdhar/structest

@MistaOmega Thanks.

I'm sure I got these from Mekanism once, Hol up, I'll find for you https://github.com/MistaOmega/Opes/blob/master/src/main/java/mistaomega/opes/blocks/CrystalInfuser/CrystalInfuserGUI.java Refer to the bottom of this file, hopefully these are what you're after or at least of some use If you're talking animation like a moving arrow too, that happens in that file too, idk if it's in the same way you'd like, but if so, use away ❤️

Why don't you use Entity#isAirborne? Also, you should use this to get if a keybind is pressed, Minecraft#gameSetiings#"insert keybind here"#isPressed.

Howdy In my experience, the Minecraft AI is difficult. You really need to invest the time to understand exactly what it's doing otherwise random stuff will just happen for no reason. I've found it very helpful to add logging code (print to console) into the AI code (even copying the vanilla classes out) to let you study what's going on without disrupting it using breakpoints. Likewise adding a switch in your code (eg triggered by pressing the control key) to 'freeze' the AI and stop it updating so you can breakpoint and inspect all the variables. It's also very helpful to strip the AI right back to one task and then slowly add them back (or add new) one at a time. I've also found it useful to add a spawn inhibitor which prevents all entities from spawning except your own entity, so there are no other AI tasks running except for your own (makes breakpoints much easier) eg like this https://github.com/TheGreyGhost/MinecraftByExample/blob/master/src/main/java/minecraftbyexample/usefultools/debugging/DebugSpawnInhibitor.java -TGG

Howdy You have a couple of options; if you just want to generate a flat "pizza box" model with your texture, you can use any of the methods in these example classes https://github.com/TheGreyGhost/MinecraftByExample/blob/master/src/main/java/minecraftbyexample/mbe04_block_dynamic_block_models/AltimeterBakedModel.java https://github.com/TheGreyGhost/MinecraftByExample/blob/master/src/main/java/minecraftbyexample/mbe21_tileentityrenderer/RenderQuads.java or BlockModel::bakeVanilla If you want to generate an item model with 'holes' in it, similar to vanillla, then look at ItemModelGenerator to see how vanilla does it or ItemLayerModel forge extension for further clues. Haven't done that myself.... -TGG

When I get this type of error it's normally a sign that I've changed my code (eg added a new item) and re-used an old save. As a rule I always generate a new save after making significant code changes, I've been bitten a couple of times by weird behaviour that looks like a bug in my code but was actually just because I was re-using an old save. -TGG

Your scale isn't a whole number, so yes, you're going to lose pixels. That's what happens when there is no interpolation. There is simply no way to smoothly scale something that is 5 pixels wide down to 4 pixels wide and still have aliased results (i.e. a given pixels is either fully transparent or fully opaque) and not look weird. The only value less than 1 that will produce "acceptable" results is 0.5 due to the fact that Minecraft uses a 2x2 pixel square "per pixel" of detail. But this will not scale to the small UI scale (as that removes the doubling effect present at the default scale).

[FIXED] Silly me... ... when testing the code I last posted, I was attempting to place a stack of honey bottles instead of a single honey bottle... Otherwise, it works fine. Thank you to all who replied.

Update Regarding LTS System: Please read The Big Forge Update Earlier this year, 1.13 was announced and the snapshots started coming out, the update was relatively small, but enough to be a hurdle for mod developers. This combined with 1.12 stabilizing, and a few fundamental Java changes that broke modding in general, made the Forge team decide to use this opportunity and work on cleaning the years of technical debt that Forge had accrued. During this time, it was discovered that a lot of things needed updating. In fact, well, everything did. And so, it was done, a full rewrite of practically everything Forge related. This took a long time, longer than originally anticipated. But what’s the outcome of this you might ask? A lot. cpw’s mod launching system (ModLauncher) allows for parallel mod loading and support for more modern Java versions. (Considering the original was written to target Java 6). The Forge installer now runs tasks at install time once, rather than doing it every time you run the game. These alone provide dramatic reduction in launch times. ForgeGradle, the “devkit” for creating mods, has been rewritten and is faster at, well, everything. It also integrates much better with IDEs. What does that mean, you ask? Simple. Mods are nicer to make. (Also 100% less setupDecompWorkspace.) MCPConfig allows for much easier MCP updates, and is public source too, so people can see exactly what's going on between updates. In short: There was a lot of work to do. And now that it's done, future updates will be much, much smoother. 1.14 and 1.15 The 1.14 release came around, just in time for the rewrite to be finished, so it was time to get the ball rolling again. The bulk of the restructure work was done through 1.13's life, so all that remained was actually seeing how it was to update all of it, and it went pretty well. A lot of improved systems exist now that make developing for these modern versions far easier and just better in general. The 1.15 release was relatively simple, even if Mojang decided to restructure everything and make changes to how the rendering works. (Taking some of our systems in the process, don't worry, this is a good thing.) 1.15's rendering changes were mostly a refactor, and we expect 1.16 to be a large update to rendering. This plus 1.14 seeing growth is why we chose 1.14 to be a candidate for LTS. (More on that further down.) Hopefully this kind of restructure from them is a rare thing in the future, but we welcome the change, since it often brings improvement. Although the rendering changes may pose a tough hurdle for some, the update for most should be relatively straight-forward. Forge support and LTS Forge's support for Minecraft versions will try to follow a predictable cycle, assuming Mojang also follows a predictable cycle. We will always actively target the latest Minecraft version, as ever. We will now also deem a previous major Minecraft version as "LTS" (Long Term Support). The LTS version will receive support for modders and players alike, however all new features must target the latest version first, and then may be backported. An LTS version differs slightly from the latest version, in that any new features you may want to add to it, must target the latest version, only once it has been merged in, can it be backported. (The exception to this is if the feature is non-applicable to the latest version.) The Forge Team will also mostly be focusing on the latest. This is so the community has time to stabilize a bit and gives modpack developers some time to create something special. But still have Forge running full steam ahead. Late last year (Happy 2020!) a vote was held privately with many developers of various Minecraft projects to determine which version will be LTS: Should 1.12 remain LTS or should 1.14? A vast majority chose 1.14, and so, from now on we are dropping 1.12 from support, and 1.14 is now LTS. What does this mean? 1.15 is latest. It will get full support. 1.14 is LTS. It will also get support, and new features, but new features must be made for 1.15 first. 1.12 is no longer supported on this forum, no new features, and no more bugfixes. All other versions are not supported. This means if you come to us for help with those, we will ask you to update. This includes crashes/bugs. To keep with Mojang's history of releases, we expect 1.14 to stay LTS for 12-18 months, giving plenty of time for modders and pack developers alike. However, this may change depending on what surprises Mojang has in store for us. Finally… Thank you. Thank you to all the modders/developers, all the players, and especially to all the contributors. The Minecraft modding community would not be what it is without you. You are responsible for the striving ecosystem we have today. We hope this new year brings you all you desire, and we look forward to seeing what you create. And now time for some shameless plugging, if you like Forge, please consider supporting us. http://www.patreon.com/lexmanos - The Forge Team.