Arphahat

Thanks, gentlemen. I was able to copy the contents of "portal.json" into my own portal file and it is displaying properly.

Thanks. How can I find where the portal blocks model is? The structure of the vanilla stuff seems to be different than the Forge, which is not unexpected, but I'm not clear on how to find the existing model.

I'm trying to alter the behavior of a the vanilla portal and want to re-use the portal block (the purple block that fills a portal frame). Just extending the BlockPortal doesn't do it; while my new portal block gains the functionality, it uses the texture-not-found texture. I've created new blocks before, and created JSON files for the models. But, I'm not sure how to go about doing that for an existing texture, or if there is a better way to do that. Any help is appreciated, thanks.

Thanks! Where can I find the Javadocs? That would help a bunch, I think. Also, I neighborChanged is listed as deprecated, which to me implies that there is supposed to be some other way to accomplish what I am trying to do. I'll go ahead with using it, but I just wonder why. Thanks.

I made a new block and I want to detect when a change is made next to it. However, the onNeighborChange() is not being triggered when blocks are added or removed next or on the block, nor is it triggering on fire being added. It does trigger when a chest is placed next to it, however. Any ideas on either how to get onNeighborChange() to trigger properly or if there is a different function I want to be using? Thanks.

I made a mod several versions ago, but let it fall to the side. Now, I see a potential use for it and would like to get it working again, but I am have no clue how to update to the new system. Looking through tutorials, I am finding a mishmash of old and new stuff and am hoping that someone can direct me to a reliable resource. Thanks.

Updated for 1.51. You will need the latest version of Forge Mod Loader if you want to run that one. Otherwise, v1.0.0 is the one you want.

Updated for 1.51. You will need the latest version of Forge Mod Loader if you want to run that one. Otherwise, v1.0.0 is the one you want.

OK, I experimented a little bit and it seems that the logic is reversed from how it used to behave. The block id that is used in the notify neighbor is of the block that was there before the update. So, if you are placing fire in a spot that was just air, it will be a 0, but if you knock down a block, it will give the id of the block. So, to look for fire, I just have to let it check for 0 and then check the status of the block as it is now. It will call the check more frequently, since it will also be 0 whenever any block is placed, but it won't call it abusively nor generate lag, so it is tolerable.

OK, I experimented a little bit and it seems that the logic is reversed from how it used to behave. The block id that is used in the notify neighbor is of the block that was there before the update. So, if you are placing fire in a spot that was just air, it will be a 0, but if you knock down a block, it will give the id of the block. So, to look for fire, I just have to let it check for 0 and then check the status of the block as it is now. It will call the check more frequently, since it will also be 0 whenever any block is placed, but it won't call it abusively nor generate lag, so it is tolerable.

I am trying to update my mod to work in 1.5. Much of it was trivial or little changes, but a core mechanic I was relying on seems different and I'm not sure what it is doing or how to adjust. I was relying on setBlock to in World to call notifyBlockChange with the id of the block, in this case, the fire block (id 51). Before, it worked great. Now, however, instead of just passing the block id (par4), it passes k1 which is "k1 = chunk.getBlockID(par1 & 15, par2, par3 & 15);" Why is it ANDing the coordinates of the block with 15? Tracing it through that area, it seems to find 51 again, but then decides to return 0. It then uses this 0 instead of passing the 51 in par4 into notifyBlockChange. Grrrr!!! Anyhow, my important question is this: I need to know when a block is next to a fire block. I was previously overriding the "onNeighborBlockChange" and checking to see if the id was fire. Now the id is always 0. Is there another way I can do this?

I am trying to update my mod to work in 1.5. Much of it was trivial or little changes, but a core mechanic I was relying on seems different and I'm not sure what it is doing or how to adjust. I was relying on setBlock to in World to call notifyBlockChange with the id of the block, in this case, the fire block (id 51). Before, it worked great. Now, however, instead of just passing the block id (par4), it passes k1 which is "k1 = chunk.getBlockID(par1 & 15, par2, par3 & 15);" Why is it ANDing the coordinates of the block with 15? Tracing it through that area, it seems to find 51 again, but then decides to return 0. It then uses this 0 instead of passing the 51 in par4 into notifyBlockChange. Grrrr!!! Anyhow, my important question is this: I need to know when a block is next to a fire block. I was previously overriding the "onNeighborBlockChange" and checking to see if the id was fire. Now the id is always 0. Is there another way I can do this?

Tired of making a portal into the nether, exploring a bit and then returning through that portal... only to find yourself hundreds of blocks away from where you were expecting? Do you want a portal that spawns exactly where the coordinates calculate it should, regardless of the consequences? Well, if you do, then XPP is for you! eXact Portal Placement is a mod I wrote because the inexactness of the portal location always frustrated me. The mod currently has two blocks, Obsidian Brick and Obsidian Brick Corner Stone. Obsidian Brick has two recipes, 4 obsidian surrounding 1 soulsand for 4 Obsidian Bricks, or 2 Obsidian sandwiching a soulsand for 2. Obsidian Brick Corner Stone is made by smelting an Obsidian Brick. The XPP portal can be made with either. To make this function, you build a portal out of either obsidian brick or the obsidian brick corner stone block. Light it as normal. The positioning of the portal in the nether will be exactly 1/8 the x and z values in the over world. The y value will remain exactly the same. So, you might spawn a portal in the middle of netherrack and need to dig out. Or, you might have a portal floating in mid air. Or, you might be under a pool of lava (be careful!) The Y value remaining the same allows you to build 2 different portals to the nether at different heights at the same x/z coordinates. Because of the 2 wide portal entrance and each one calculating to a different spot, there is a minimum x/z distance of 16 blocks necessary between portals in the overworld and minimum x/z distance of 2 blocks in the nether. This is a mod for 1.47. Also, just updated for 1.51! Configuration: The mod generates an XPP.cfg file that has a few settings right now. You can alter the block ids of the obsidian brick, the obsidian brick corner stone and also the portal that it spawns. The defaults are 2500, 2501 and 2502. There is also a cool-down timer that prevents endless accidental portaling up and back between the two dimensions. It is in milliseconds and the default is 5000, five seconds. If you run into issues where you are bouncing up and back because of lag, you can increase this value. Future Plans: I intend to add ways to upgrade the corner stones that will alter the behavior of the portals. One of the ideas include having the spawned portal build a safe room so that spawning under lava won't kill you. I am open to suggestions. I've tested this in single player and also have had a couple of iterations on a server I am on. However, I bet there are going to be problems that I haven't encountered. Please, feel free to post them here. Here is the mod: xpp_v1.0.0.zip for mc 1.47. xpp_v1.5.0.zip for mc 1.51. Installation: I made it with this with Forge and that will need to be installed for it to work. I recommend the Forge mod loader, used by FTB. After running FTB and selecting the mod pack you wish to play with, click "edit mod pack" and then browse to the xpp zip and add it. If you don't want to use FTB, however, to install manually, copy the xpp zip to the "minecraft\mods" directory after first installing Forge. Honestly, most of my experience with mods has been via FTB and it makes it very, very easy to add and remove mods. If someone else has experience with installing mods manually and would like to help with a writeup of how-to for mine, I'd appreciate it. Recipes: Obsidian Brick: Obsidian Brick Corner Stone: A little of each: Copyright statement: This mod (plugin, a patch to Minecraft source, henceforth "Mod" or "The Mod"), by the terms of http://www.minecraft.net/copyright.jsp is sole property of the Mod author (Arphahat, henceforth "Owner" or "The Owner"). By default it may only be distributed on minecraftforums.net, mcmodcenter.net, minecraftforge.net and http://feed-the-beast.com. It may only be mirrored or reposted with advance written permission of the Owner. Electronic Mail is fine if you wait for a response. URL shorteners or other attempts to make money off The Owner's Mod are strictly forbidden without advance written permission

Tired of making a portal into the nether, exploring a bit and then returning through that portal... only to find yourself hundreds of blocks away from where you were expecting? Do you want a portal that spawns exactly where the coordinates calculate it should, regardless of the consequences? Well, if you do, then XPP is for you! eXact Portal Placement is a mod I wrote because the inexactness of the portal location always frustrated me. The mod currently has two blocks, Obsidian Brick and Obsidian Brick Corner Stone. Obsidian Brick has two recipes, 4 obsidian surrounding 1 soulsand for 4 Obsidian Bricks, or 2 Obsidian sandwiching a soulsand for 2. Obsidian Brick Corner Stone is made by smelting an Obsidian Brick. The XPP portal can be made with either. To make this function, you build a portal out of either obsidian brick or the obsidian brick corner stone block. Light it as normal. The positioning of the portal in the nether will be exactly 1/8 the x and z values in the over world. The y value will remain exactly the same. So, you might spawn a portal in the middle of netherrack and need to dig out. Or, you might have a portal floating in mid air. Or, you might be under a pool of lava (be careful!) The Y value remaining the same allows you to build 2 different portals to the nether at different heights at the same x/z coordinates. Because of the 2 wide portal entrance and each one calculating to a different spot, there is a minimum x/z distance of 16 blocks necessary between portals in the overworld and minimum x/z distance of 2 blocks in the nether. This is a mod for 1.47. Also, just updated for 1.51! Configuration: The mod generates an XPP.cfg file that has a few settings right now. You can alter the block ids of the obsidian brick, the obsidian brick corner stone and also the portal that it spawns. The defaults are 2500, 2501 and 2502. There is also a cool-down timer that prevents endless accidental portaling up and back between the two dimensions. It is in milliseconds and the default is 5000, five seconds. If you run into issues where you are bouncing up and back because of lag, you can increase this value. Future Plans: I intend to add ways to upgrade the corner stones that will alter the behavior of the portals. One of the ideas include having the spawned portal build a safe room so that spawning under lava won't kill you. I am open to suggestions. I've tested this in single player and also have had a couple of iterations on a server I am on. However, I bet there are going to be problems that I haven't encountered. Please, feel free to post them here. Here is the mod: xpp_v1.0.0.zip for mc 1.47. xpp_v1.5.0.zip for mc 1.51. Installation: I made it with this with Forge and that will need to be installed for it to work. I recommend the Forge mod loader, used by FTB. After running FTB and selecting the mod pack you wish to play with, click "edit mod pack" and then browse to the xpp zip and add it. If you don't want to use FTB, however, to install manually, copy the xpp zip to the "minecraft\mods" directory after first installing Forge. Honestly, most of my experience with mods has been via FTB and it makes it very, very easy to add and remove mods. If someone else has experience with installing mods manually and would like to help with a writeup of how-to for mine, I'd appreciate it. Recipes: Obsidian Brick: Obsidian Brick Corner Stone: A little of each: Copyright statement: This mod (plugin, a patch to Minecraft source, henceforth "Mod" or "The Mod"), by the terms of http://www.minecraft.net/copyright.jsp is sole property of the Mod author (Arphahat, henceforth "Owner" or "The Owner"). By default it may only be distributed on minecraftforums.net, mcmodcenter.net, minecraftforge.net and http://feed-the-beast.com. It may only be mirrored or reposted with advance written permission of the Owner. Electronic Mail is fine if you wait for a response. URL shorteners or other attempts to make money off The Owner's Mod are strictly forbidden without advance written permission

How do I output text to the chat window? Right now, I am trying just to use it for debug purposes, but it is something that could prove useful to me later.