Opticraft Community
Discussion forum => Legacy => Archives => Suggestions => Topic started by: 2468avc on April 05, 2013, 09:43:54 pm
-
Hi Everyone,
My suggestion is pretty much the topic. Lava buckets are by far the most efficient fuel in minecraft, it would be awesome to be able to use them in auto-smelters. There would have to be some code to make sure non- staff can't actually place lava, but I think this would be a good addition to the server.
2468avc
Also, there was an old post here...
http://www.opticraft.net/index.php/topic,14376.15.html (http://www.opticraft.net/index.php/topic,14376.15.html)
I didn't reply there because you all would've told me not to necro-post.
-
Non-staff already can't place lava avc.
-
totally got shot down the first time i suggested. main arguments were, A) we'd harvest out the nether's lava, B) you get more overall time from blaze rods, 7680 secs for a stack vs 1000 secs for 1 lava bucket, (assuming u have infinite blaze rods :-\ ) C) you'd have to sit at the furnace to keep adding blocks to not waste the time, and D)people would use it for griefing.
course with the addition of hoppers it's even more plausible to use since u could set up an hopper + minecart track that auto transports buckets right to a smelting area, so all you'd have to do is sit at a pool and scoop up 200 buckets, toss it into a hopper conveyor belt n woosh off to ur smelting area.
not to mention have a hopper feeding a constant flow of blocks into the furnaces/out of the furnaces so that non of the 1000 secs of smelting time goes to waste.
also we have 3 nethers now, so farming all the lava in all 3 in any amount of time is just unfathomable
and assuming the plugin keeping us from placing lava function correctly, griefing with it is a non issue.
supported it wen i suggested it the first time around, still support it now. it's a shame to lose items/blocks that are extremely useful like this one and still call ourselves a survival server, especially wen the plugin could just prevent placement to stop griefing, instead of preventing picking up and placement.
-
Non-staff already can't place lava avc.
Completely missing the point... *sighs*
totally got shot down the first time i suggested. main arguments were, A) we'd harvest out the nether's lava
To restate, we have 3 nethers. One was recently expanded, and all of them have HUGE lava lakes.
B) you get more overall time from blaze rods, 7680 secs for a stack vs 1000 secs for 1 lava bucket, (assuming u have infinite blaze rods :-\ )
Assuming, of course, that you have infinite blaze rods...
C) you'd have to sit at the furnace to keep adding blocks to not waste the time
Um, I have a hopper system at my house that does this automatically.
D)people would use it for griefing.
And, as 360OLLIE already said, (completely missing the point [he knows i'm kidding, we're friends irl])
Non-staff already can't place lava avc.
Thats pretty much it, just wanted to summarize and restate some main points.
-
Those weren't his points he was making, he was stating reasons his suggestion got shot down
-
Those weren't his points he was making, he was stating reasons his suggestion got shot down
followed by a bunch of reasons why the reasons it got shot down are irrelevant.....
but im pretty sure he was just summarizing for the lazies
-
Non-staff already can't place lava avc.
Completely missing the point... *sighs*
I feel so pathetic. :p
-
I have tried using lava buckets and I was disappointed when I learned it was not possible, and I vowed to make a topic about it, but I was too lazy to start one.
That being said, I fully support this idea. Please implement it! Can't be that hard... can it?
-
I don't think the problem is that we will run out of lava. The problem would be the increased amount of lava flow. Flowing lava causes more lag then stagnant lava.
-
I don't think the problem is that we will run out of lava. The problem would be the increased amount of lava flow. Flowing lava causes more lag then stagnant lava.
was another one of the topics of discussion in my original post, turns out flowing lava/stagnant lava makes no difference on lag, the only time it comes into play is when a lava bucket gets filled and it performs the calculations to produce the flowing lava. but unless everyone's grabbing lava buckets at the exact same time the calculations would never be overwhelming.
once the lava is done spreading it's basically stagnant lava with a different animation.
-
I don't think the problem is that we will run out of lava. The problem would be the increased amount of lava flow. Flowing lava causes more lag then stagnant lava.
You could always only be able to get lava buckets at the market for $100. Myabe
-
That could definitely work. Though maybe $125, we wouldn't want a noob going to the market saying "Hmm, lava... And I dont even have to go to the nether... Imma gonna buy! What!!!??? That was all my cash!!!??? Unfair!!!!!! (etc.)"
Edit: So... Do you think this will be added?
Do not double post - Merged.
-
Don't double post.
Anyways, this idea should be implemented IF two criteria are met.
1: Nothing more important is being worked on.
2: It is easy to code.
-
Basically to implement this:
1) Register a BlockPlaceEvent handler to the Opticraft server plugin (if not already done).
2) On the onBlockPlace method call add this:
public void onBlockPlace(BlockPlaceEvent bpEvent)
{
if(bpEvent.getBlockPlaced().getType() == Material.STATIONARY_LAVA)
{
if(!bpEvent.getPlayer().hasPermission("some.override.permission.for.moderators")))
{
bpEvent.setCancelled(true);
}
}
}
Personally I would have preffered to combine the two IF statements into one using &&, but since the forum text editor was being wierd I found it to look nicer for viewing with two seperate statements.
Basically, on each and every block placement, the above method is called. Then we check if the block placed is STATIONARY_LAVA, or a lava source block which is what is placed by a filled lava bucket. If I'm wrong then simply change the Material.<material> part on the first IF statement.
If it is a lava block, then check to see if the player who placed the lava has the override permission (such as a moderator permission). Notice I have the ! in front of the hasPermission() call. For those who don't know how to program, that simply stands for if the player DOESNT have the permission. If not, then we set the event state to be cancelled, and Bukkit does the rest.
Add that to the opticraft plugin, and allow lava buckets to be used. That code will block lava placement, but not picking up lava. So long as we can fill a lava bucket, we can use it in a furnace. No harm can be done as long as players can't place the lava.
-
Basically to implement this:
1) Register a BlockPlaceEvent handler to the Opticraft server plugin (if not already done).
2) On the onBlockPlace method call add this:
public void onBlockPlace(BlockPlaceEvent bpEvent)
{
if(bpEvent.getBlockPlaced().getType() == Material.STATIONARY_LAVA)
{
if(!bpEvent.getPlayer().hasPermission("some.override.permission.for.moderators")))
{
bpEvent.setCancelled(true);
}
}
}
Personally I would have preffered to combine the two IF statements into one using &&, but since the forum text editor was being wierd I found it to look nicer for viewing with two seperate statements.
Basically, on each and every block placement, the above method is called. Then we check if the block placed is STATIONARY_LAVA, or a lava source block which is what is placed by a filled lava bucket. If I'm wrong then simply change the Material.<material> part on the first IF statement.
If it is a lava block, then check to see if the player who placed the lava has the override permission (such as a moderator permission). Notice I have the ! in front of the hasPermission() call. For those who don't know how to program, that simply stands for if the player DOESNT have the permission. If not, then we set the event state to be cancelled, and Bukkit does the rest.
Add that to the opticraft plugin, and allow lava buckets to be used. That code will block lava placement, but not picking up lava. So long as we can fill a lava bucket, we can use it in a furnace. No harm can be done as long as players can't place the lava.
lol you made the same mistake as cschurz :P
what about lava that isn't stationary? ;D
-
I find it funny when you guys post code to show off. You obviously know that opti can do this stuff so the code you put in the topic is purely to show off.
-
100101101
-
This sounds like a VERY good idea to me, I mean like many others have said, If there's a way to prevent us from placing it but still let us pick it up and use it as fuel. This would be my solution to having to use all my coal to smelt connlestone into stone for stone bricks, instead, I could just use this, MUCH easier? But then again, that would defeat the whole point of us all even collection coal other than for torches? I support this idea anyways, It would make my life MUCH MUCH simpler.
-
This sounds like a VERY good idea to me, I mean like many others have said, If there's a way to prevent us from placing it but still let us pick it up and use it as fuel. This would be my solution to having to use all my coal to smelt connlestone into stone for stone bricks, instead, I could just use this, MUCH easier? But then again, that would defeat the whole point of us all even collection coal other than for torches? I support this idea anyways, It would make my life MUCH MUCH simpler.
You could always only be able to get lava buckets at the market for $100. Myabe
-
Yes that should happen, where you can only get lava buckets at the market, so only people really serious about wanting them would get them. Ahere would be no extra lag in the nether. Very good idea, I didn't see it earlier, nice.
-
I find it funny when you guys post code to show off. You obviously know that opti can do this stuff so the code you put in the topic is purely to show off.
well there's that... and the fact that people like to say suggestions wont work because "it'd be too hard to code" so showing that it takes 5 lines of code usually prevents that from happening...
course u kno me, big showoffy jerk.... but there are other motivations..... :D
-
I find it funny when you guys post code to show off. You obviously know that opti can do this stuff so the code you put in the topic is purely to show off.
Way to be an ass. Just assume I'm being a showoff when I did not have that intention. It was purely to show that the implementation wouldn't be that difficult. In other words, just a supporting argument for why this should be implemented.
Its like saying that xDeeKay is a showoff because opti also knows what binary is.
Tiggy, to answer your question about flowing lava, that isn't an issue. Flowing lava must originate from the source block placed by the player holding a lava bucket. Basically each "event" which is triggered somehow has a state that says whether or not it should be cancelled. These events are created before any info about them is sent to the player. When the server finally processes each event, it looks at the cancelled state. If the cancelled state is true then the event is never processed. Because of this, the lava block is never placed, and therefore flowing lava is never created.
The game client on the other hand places a lava block as that is what it thinks should happen. But the lava block immediately disappears because the server says "No that isn't supposed to be there" so the placed block disappears.
-
I find it funny when you guys post code to show off. You obviously know that opti can do this stuff so the code you put in the topic is purely to show off.
Way to be an ass. Just assume I'm being a showoff when I did not have that intention. It was purely to show that the implementation wouldn't be that difficult. In other words, just a supporting argument for why this should be implemented.
Its like saying that xDeeKay is a showoff because opti also knows what binary is.
Tiggy, to answer your question about flowing lava, that isn't an issue. Flowing lava must originate from the source block placed by the player holding a lava bucket. Basically each "event" which is triggered somehow has a state that says whether or not it should be cancelled. These events are created before any info about them is sent to the player. When the server finally processes each event, it looks at the cancelled state. If the cancelled state is true then the event is never processed. Because of this, the lava block is never placed, and therefore flowing lava is never created.
The game client on the other hand places a lava block as that is what it thinks should happen. But the lava block immediately disappears because the server says "No that isn't supposed to be there" so the placed block disappears.
Writing code is not a supporting argument. No one in this topic said it would be hard to code. The question is should we add it, showing us how to add it is irrelevant to the discussion.
-
I still was not, as you stated, "showing off"
It's not worth showing off. Now using the JNI and JNA libraries to make a working Java RunPE would be worth showing off lol. I haven't been able to even fully understand all of the code in a .NET runPE :'(
Getting back on topic now, do you have any reasons this shouldn't be implemented? Here's my check:
Is this necessary? Not really. We have coal and blaze rods.
Would this cause issues in the server? Unless we are wrong about the lag part caused by flowing lava, not really since this wouldn't allow placement of lava, and no extra lag as far as we know.
Is this easy to implement, and can this be implemented quickly? Yes.
-
Is this necessary? Not really. We have coal and blaze rods.
Untrue. Coal doesn't smelt enough stuff to be effective in huge jobs, and blaze rods are fairly hard to come by in large quantites.
-
Basically to implement this:
1) Register a BlockPlaceEvent handler to the Opticraft server plugin (if not already done).
2) On the onBlockPlace method call add this:
public void onBlockPlace(BlockPlaceEvent bpEvent)
{
if(bpEvent.getBlockPlaced().getType() == Material.STATIONARY_LAVA)
{
if(!bpEvent.getPlayer().hasPermission("some.override.permission.for.moderators")))
{
bpEvent.setCancelled(true);
}
}
}
Personally I would have preffered to combine the two IF statements into one using &&, but since the forum text editor was being wierd I found it to look nicer for viewing with two seperate statements.
Basically, on each and every block placement, the above method is called. Then we check if the block placed is STATIONARY_LAVA, or a lava source block which is what is placed by a filled lava bucket. If I'm wrong then simply change the Material.<material> part on the first IF statement.
If it is a lava block, then check to see if the player who placed the lava has the override permission (such as a moderator permission). Notice I have the ! in front of the hasPermission() call. For those who don't know how to program, that simply stands for if the player DOESNT have the permission. If not, then we set the event state to be cancelled, and Bukkit does the rest.
Add that to the opticraft plugin, and allow lava buckets to be used. That code will block lava placement, but not picking up lava. So long as we can fill a lava bucket, we can use it in a furnace. No harm can be done as long as players can't place the lava.
lol you made the same mistake as cschurz :P
what about lava that isn't stationary? ;D
optical made that mistake, not me :)
Basically to implement this:
1) Register a BlockPlaceEvent handler to the Opticraft server plugin (if not already done).
2) On the onBlockPlace method call add this:
public void onBlockPlace(BlockPlaceEvent bpEvent)
{
if(bpEvent.getBlockPlaced().getType() == Material.STATIONARY_LAVA)
{
if(!bpEvent.getPlayer().hasPermission("some.override.permission.for.moderators")))
{
bpEvent.setCancelled(true);
}
}
}
this prevents users from placing stationary lava, yes. we already have that. the problem is that we have code that prevents members from collecting water/lava into buckets. i just removed that, but it's up to optical to approve it and update the server. i don't see why members shouldn't be allowed to collect stuff into buckets.
-
Basically to implement this:
1) Register a BlockPlaceEvent handler to the Opticraft server plugin (if not already done).
2) On the onBlockPlace method call add this:
public void onBlockPlace(BlockPlaceEvent bpEvent)
{
if(bpEvent.getBlockPlaced().getType() == Material.STATIONARY_LAVA)
{
if(!bpEvent.getPlayer().hasPermission("some.override.permission.for.moderators")))
{
bpEvent.setCancelled(true);
}
}
}
Personally I would have preffered to combine the two IF statements into one using &&, but since the forum text editor was being wierd I found it to look nicer for viewing with two seperate statements.
Basically, on each and every block placement, the above method is called. Then we check if the block placed is STATIONARY_LAVA, or a lava source block which is what is placed by a filled lava bucket. If I'm wrong then simply change the Material.<material> part on the first IF statement.
If it is a lava block, then check to see if the player who placed the lava has the override permission (such as a moderator permission). Notice I have the ! in front of the hasPermission() call. For those who don't know how to program, that simply stands for if the player DOESNT have the permission. If not, then we set the event state to be cancelled, and Bukkit does the rest.
Add that to the opticraft plugin, and allow lava buckets to be used. That code will block lava placement, but not picking up lava. So long as we can fill a lava bucket, we can use it in a furnace. No harm can be done as long as players can't place the lava.
lol you made the same mistake as cschurz :P
what about lava that isn't stationary? ;D
optical made that mistake, not me :)
Basically to implement this:
1) Register a BlockPlaceEvent handler to the Opticraft server plugin (if not already done).
2) On the onBlockPlace method call add this:
public void onBlockPlace(BlockPlaceEvent bpEvent)
{
if(bpEvent.getBlockPlaced().getType() == Material.STATIONARY_LAVA)
{
if(!bpEvent.getPlayer().hasPermission("some.override.permission.for.moderators")))
{
bpEvent.setCancelled(true);
}
}
}
this prevents users from placing stationary lava, yes. we already have that. the problem is that we have code that prevents members from collecting water/lava into buckets. i just removed that, but it's up to optical to approve it and update the server. i don't see why members shouldn't be allowed to collect stuff into buckets.
Optical made it that way because they cant place it. We were getting tons of complaints about people wasting iron on buckets to have them filled with lava and then they can't do anything with it. Of course this suggestion gives it a use. There were also a lot of bugs with stopping members from placing water/lava. We had numerous cases where placing lava or water was possible even with the restriction.
-
The only way the restriction could be bypassed would be if another plugin is setting the cancelled state to false. Otherwise its impossible for that bug to be happening.
-
The only way the restriction could be bypassed would be if another plugin is setting the cancelled state to false. Otherwise its impossible for that bug to be happening.
Hey, I'm just telling you what was happening. I don't have an explanation for it.
-
The only way the restriction could be bypassed would be if another plugin is setting the cancelled state to false. Otherwise its impossible for that bug to be happening.
Hey, I'm just telling you what was happening. I don't have an explanation for it.
Yeah I understand. I just mentioned the most likely explanation for it. I think it might be worldguard
-
Sorry for the double post. I'd delete the first post if I could, and editing doesn't show any sort of notification for the thread.
Basically the problem statement with this idea is that players are somehow able to get around the block to prevent lava from being placed.
Two things are possible:
1) Back when players could originally exploit a bug to get around the lava placement blocker, this might have been an issue with Bukkit itself not properly blocking events. Maybe the newer bukkit version won't do this?
2) I am honestly against there being more privileges for Trusted members, but maybe picking up lava could be a Trusted only thing entirely because Trusted members are less likely to exploit the lava bug, and even if they do, they are less likely to exploit the bug to cause problems.
Perhaps this could be given a chance, and if players placing lava (exploiting a bug in bukkit allowing them to get past our lava placement blocker) gets out of hand, then the lava buckets can be taken away just as quickly as they were given.
-
So Optical/Nick/Nyssa/Relkeb, is this accepted? We've proven that the coding is easy and that it would benefit the server.
-
Well, 2468, we still have an issue to be thought out.
It was pointed out that even by allowing lava to be picked up, but not placed, some players can still place lava through some exploit, or by some means. This was pointed out according to a past attempt apparently. Unless this problem were to be corrected, this idea would most likely need to be put on hold.
Would like some updated staff input though.
-
Yes, but is that in protected areas? Also, didn't someone say that the server had to be very laggy for this to happen, and the person has to place it in the first place. so unless all three of those line up, no lava problems.
Would like some updated staff input though.
-
Sorry for the double post. I spoke to Nyssa ingame and she said that it might/will happen IF* two of the plugins are coded or something. So I guess that's that until the plugins are coded/updated/whatever.
-
Well, I could code a plugin that would block placement of lava except for if a player places it who has the right permission if all of the Opticraft programmers are too busy with other things. I could also make the plugin block lava pick up by players who don't have a special permission. Perhaps it would be a good idea to only allow members+ to pick up lava into buckets (but still not place the lava), or even trusted users (strictly because trusted players are less likely to try to exploit a bug to place lava and get around the plugin's blocks, but I personally wouldn't fully support that).
-
I think it's some more general plugins. Speak with Nyssa, she'll tell you.
-
Well, I could code a plugin that would block placement of lava except for if a player places it who has the right permission if all of the Opticraft programmers are too busy with other things. I could also make the plugin block lava pick up by players who don't have a special permission. Perhaps it would be a good idea to only allow members+ to pick up lava into buckets (but still not place the lava), or even trusted users (strictly because trusted players are less likely to try to exploit a bug to place lava and get around the plugin's blocks, but I personally wouldn't fully support that).
We already have these in place, no need. Not sure what 2468 is talking about.
-
Well, I could code a plugin that would block placement of lava except for if a player places it who has the right permission if all of the Opticraft programmers are too busy with other things. I could also make the plugin block lava pick up by players who don't have a special permission. Perhaps it would be a good idea to only allow members+ to pick up lava into buckets (but still not place the lava), or even trusted users (strictly because trusted players are less likely to try to exploit a bug to place lava and get around the plugin's blocks, but I personally wouldn't fully support that).
We already have these in place, no need. Not sure what 2468 is talking about.
I don't either. :P Ask Nyssa, she seemed to know.
-
Might be offtopic from the current conversation above me. But I would really like to be able to pick up lava to use for furnaces. (only if it is possible) :)
-
I'm assuming that we can now since I just picked up lava?
-
I'm assuming that we can now since I just picked up lava?
No that's just a visual glitch client side, try and place it, it wont work.
-
Yep. I was going to edit the post but got sidetracked...
-
Welp, we have coal blocks now at least...they can cook up to 72 blocks at one time...not as good as lava buckets, but totally still worth it! ;D
-
Welp, we have coal blocks now at least...they can cook up to 72 blocks at one time...not as good as lava buckets, but totally still worth it! ;D
dont necropost