Hi all, not sure if this is quite the right place for this because the issue is with a modded server, but I run into the same problem when I try to run the modded client in SSP, so I figured I'd put it here.
To start, here are all of the mods I currently have installed:
Simply put, Nether portals are temperamental at best with this collection of mods. When I construct a portal frame out of the standard 10 blocks, and then attempt to light it, one of two things will happen:
The flint and steel will set fire to the obsidian, but the portal will not light
The flint and steel will expend one use, but the portal will not light and the block is not set on fire.
I don't have anything (e.g. extra obsidian blocks) around the portal that would cause it to not light, the Nether is enabled in the server config, and spawn protection is disabled. In fact, there are now two working Nether portals in the world.
I did some searching on this issue before, and found someone having a similar problem, and the advice was to delete all of the config files and let Minecraft / Forge regenerate them. I tried this, and it worked - I was finally able to light portals, and created the two I just mentioned. However, it seems that the config files are getting corrupted over time, or some such thing. After a couple of days, the problem returned.
I feel like this problem is related to another issue on the server, related to redstone and block updates. I set up a piston door on my house and wired it up with redstone. It worked when I tried it at first, but when I left and came back, some of the pistons would not extend, leaving holes in the door when it was closed. The issue is not with the wiring; I placed a piston (facing air) nearby the door and placed a redstone torch next to it, and it would not extend. The nonfunctioning pistons seem to be based on totally random world locations. That is, I can place a piston one block and it will extend, and then move it over one and it will not. Also, I have seen pistons extend while the piston below it refuses to extend.
At this point, I have one solution that seems to have worked before -- delete all of the config files and regenerate them. I'd like to avoid this, however, since I've made many modifications to the config files (including resolving some block ID conflicts and fiddling with world gen), meaning that it's a hassle to set everything back up again and I've already clobbered some stuff on the server by accident when I missed a spot where I'd changed the configs.
Anyone have any suggestions for a more permanent fix? This is my first time compiling a modpack and running a modded server for Minecraft, and I'm learning the hard way just how fragile they can be.
I can't say that I know anything about Minecraft Forge because I personally don't use it. But based on that list of mods you have installed, I'd think that one of the mods is conflicting with another (possibly more than one). When I had two mods that modified the same class, they battled it out for who could control it (camera studio and better sprinting). You should try doing 'trial and error' to find out which mod is conflicting with another. Remove the ones that you use less often first as they are more likely to conflict with anything.
Hope this helps!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
To start, here are all of the mods I currently have installed:
Simply put, Nether portals are temperamental at best with this collection of mods. When I construct a portal frame out of the standard 10 blocks, and then attempt to light it, one of two things will happen:
- The flint and steel will set fire to the obsidian, but the portal will not light
- The flint and steel will expend one use, but the portal will not light and the block is not set on fire.
I don't have anything (e.g. extra obsidian blocks) around the portal that would cause it to not light, the Nether is enabled in the server config, and spawn protection is disabled. In fact, there are now two working Nether portals in the world.I did some searching on this issue before, and found someone having a similar problem, and the advice was to delete all of the config files and let Minecraft / Forge regenerate them. I tried this, and it worked - I was finally able to light portals, and created the two I just mentioned. However, it seems that the config files are getting corrupted over time, or some such thing. After a couple of days, the problem returned.
I feel like this problem is related to another issue on the server, related to redstone and block updates. I set up a piston door on my house and wired it up with redstone. It worked when I tried it at first, but when I left and came back, some of the pistons would not extend, leaving holes in the door when it was closed. The issue is not with the wiring; I placed a piston (facing air) nearby the door and placed a redstone torch next to it, and it would not extend. The nonfunctioning pistons seem to be based on totally random world locations. That is, I can place a piston one block and it will extend, and then move it over one and it will not. Also, I have seen pistons extend while the piston below it refuses to extend.
At this point, I have one solution that seems to have worked before -- delete all of the config files and regenerate them. I'd like to avoid this, however, since I've made many modifications to the config files (including resolving some block ID conflicts and fiddling with world gen), meaning that it's a hassle to set everything back up again and I've already clobbered some stuff on the server by accident when I missed a spot where I'd changed the configs.
Anyone have any suggestions for a more permanent fix? This is my first time compiling a modpack and running a modded server for Minecraft, and I'm learning the hard way just how fragile they can be.
Hope this helps!