Solved ItemContainer dropped through spam

O... New update and new bugs... This error very annoying!

Code:

ItemContainer.dropPosition dropped through
ItemContainer.dropVelocity dropped through
ItemContainer.dropPosition dropped through
ItemContainer.dropVelocity dropped through
ItemContainer.dropPosition dropped through
ItemContainer.dropVelocity dropped through
ItemContainer.dropPosition dropped through
ItemContainer.dropVelocity dropped through

 

any way to stop that shit?

 

Any fix for that? Can't see it any more!

When I started server without oxide - no this message pupup!

 

same problem

 

@Wulf can u fx it?

 

Command:
dropvelocity.fix
in the console

 

Thanks!

Oh my! This command deletes all FURNACES!

 

doesn't delete all the furnaces,
but it's the furnaces that are bugged that does this error
so if the furnace is bugged it will get deleted yes.
and if it's all ACTIVE furnaces (as it must be active ...) that does this error, then all ACTIVE furnaces are deleted ...
you wanted a fix to this error, nothing else i can do exept remove what is causing this error.
[DOUBLEPOST=1424273720][/DOUBLEPOST]exept rewrite rust XD but that's not our job lol

 

Why this problem? Of stacks, or what?
[DOUBLEPOST=1424273931][/DOUBLEPOST]I found, that if stack of ore 1000 - its not smelting

When smaller - smelts.

 

I got it error too...and furnace don't work

 

Use Reneb's fix

 

ok so this happens when a furnace is full and tries to throw items out of the furnace.

 

Thanks for your fix

 

not really a fix ... but yeah you should ask players to be carefull and not stack stuff.

 

So! FRESH NEEEEEWS!

Tommorow will be update, that will fix this problem.

 

Where where where did you read that

 

http://www.rustafied.com/

 

I deleted and reloaded my StackSizes.cs file and the error went away. Let's see if it happens tomorrow. I also deleted my changes of adding in ammo stacks to 1000. Didn't work, so I deleted those changes.

Well it fixed the error, but since the new Rust is out they might of fixed it permanently now.

 

Nothing to do with this error ^^