Author Topic: Fixed JVS content  (Read 421 times)

Quote from: server.cs
   function fxDTSBrick::onClearFakeDeath(%obj)
   {
      Parent::onClearFakeDeath(%obj);
      %contentTypeID = %obj.contentTypeID();

      if(%contentTypeID > -1)
      {
         %obj.setRendering(1);
         %obj.noContentEvents = 1;
         %obj.schedule(600, "contentCreate", 0);
      }
   }
Should be
Code: [Select]
function fxDTSBrick::onClearFakeDeath(%obj)
{
Parent::onClearFakeDeath(%obj);
%contentTypeID = %obj.contentTypeID();

if(%contentTypeID > -1)
{
%obj.noContentEvents = 1;
%obj.schedule(600, "contentCreate", 0);
}
}
I don't see why it sets the rendering to 1 after it respawns. Seems kinda pointless and it breaks the door if it is blown up in a minigame when the owner of the brick isn't on.

That's really weird...
There's already some issues in JVS that spams the console.

I hate how everyone bashes the prop brick system for it's console error spam even though JVS is not much better.
It seems to be the popularity of the creator, really. Sigh.

Back to the point, yes, that needs fixing.

Bump.

This should be fixed considering practically every server has this mod.

Agreed, good sir.
And sometimes, the events seem to screw up on loading and the thing doesn't start right and starting it screws it over.
It's really kinda glitchy, although the glitch that I mention in this post might just be a server with an old version of it that doesn't distinguish certain planting properly.