Pleas and Troubleshooting > Bugs and glitches

Jobs - Netherworker - Furnace not paying

(1/4) > >>

1869_Flame:
It seems  for some reason the netherworker is a bit buggy.
When i have my furnaces connected with a hopper above (feed netherrack) in the back (feed burning material) and below (take out finished product) it seems all to work just perfect, and i get payed for making netherbrick.

When i log off, or leave the furnace chunk for a longer time (lets say 15 minutes) and i come back, it is not paying anymore, although it is still smelting.
It seems as if the furnace has forgotten that i was the owner of all the netherrack in the furnace and all that is in the hopper ready to get in.
I had 25 furnaces burning, and checked /balance a few times, and wasnt increasing.

I will also try to post this bug at the jobs plugin (if i can find where finally) but im also posting it here, because i am not sure if this might be server related or plugin related.

badbh222:
After looking at the source code of Jobs some more, I *think* I know what the problem is, Jobs stores the name of the player that started smelting as an NBT Tag in the block, and when the fuel runs out and the furnace is changed from a lit furnace to an unlit furnace for a split second, it loses that NBT Tag... Maybe.  :-\

1869_Flame:
No that can not be it. If i stay around within the chunk, there is no problem and all works just fine.
In the sreenshot you can see the design of the smelter. Works just perfect as long as you are around.

If you leave the place for over 10 to 15 minutes and come back (or log off) it still is smelting, but not paying anymore.
It seems to be forgotten that Tag on all the netherrack in the furnace, but also in the hoppers and if there was, the chest feeding the hopper again.

I tried making a ticket at the Jobs plugin page, but it was rejected as they also want 2 config files to be posted, else its no valid support ticket.
Maybe a admin might be able to post a ticket on this one.

badbh222:
It is still the same problem, when you leave and the chunk unloads, the custom MetaData for that block is lost, custom MetaData applied by Bukkit is not persistent, when the chunk is unloaded and reloaded, a new instance of that Block is loaded into memory with none of the previous custom MetaData.

It *is* fixable by the Jobs dev, but it would cause a bit of overhead and would not be as practical as this, plus it kind of limits players to be around their furnaces until they are done smelting to get the full payment, which is nice in my opinion.

1869_Flame:

--- Quote from: badbh222 on June 26, 2013, 03:33:37 AM ---It is still the same problem, when you leave and the chunk unloads, the custom MetaData for that block is lost, custom MetaData applied by Bukkit is not persistent, when the chunk is unloaded and reloaded, a new instance of that Block is loaded into memory with none of the previous custom MetaData.

It *is* fixable by the Jobs dev, but it would cause a bit of overhead and would not be as practical as this, plus it kind of limits players to be around their furnaces until they are done smelting to get the full payment, which is nice in my opinion.

--- End quote ---
Well it is not always possible to stay around at your furnace. For example when a new player joins i go to spawn, and maybe give a tour if needed. When i go back, it seems that i need to get everything out again, and put it back in, but even that this doesnt seem to work all thimes. So i end up needing to break the furnaces and make them again. Still i think after doing that, some of the blocks that came out and be put back in seems not to pay. Ill need to test this last statement some better though

Navigation

[0] Message Index

[#] Next page