Author Topic: Props (DTS bricks) - Why not?  (Read 4373 times)

Just so happens I remade my own prop system. It removes all console errors. The only problems I know of is when you duplicate props they loose their rotation and when destroying multiple props at once they tend to stick around for a few seconds.

Ephialtes duplicator forgets up practically every mod related to bricks. Send me a PM if you want it.
Edit: I'll also throw in an example prop to get you started.
« Last Edit: August 11, 2011, 11:10:30 PM by Jasa1 »

Why not just use rotondo's health locker code? all it does is spawn an item inside the brick that looks like the health locker, and then plays an animation/heals the player when he touches it :/

Why not just use rotondo's health locker code? all it does is spawn an item inside the brick that looks like the health locker, and then plays an animation/heals the player when he touches it :/
That's ingenious! How does it differ from a prop though?

Well, for one, I have never heard of rotondo's mod causing extreme console spam

Why not just use rotondo's health locker code? all it does is spawn an item inside the brick that looks like the health locker, and then plays an animation/heals the player when he touches it :/
Rotondo's health lockers are not rescaled.

Rotondo's health lockers are not rescaled.
I know that, he made the health locker shape the size of the brick, then made it an item and used some code to make it spawn inside the brick, and stuff like that

Jasa1's fix for the Prop system works flawlessly.

One little error at line 96:
Quote
      if(%datablock.modelScale! $= "")
      {
         %brick.prop.setScale(%datablock.modelScale);
      }
Change to
Quote
      if(%datablock.modelScale !$= "")
      {
         %brick.prop.setScale(%datablock.modelScale);
      }
If you change that, the prop system is even better than JVS, if you compare no console spam to JVS console spam.
Thank you Jasa1 :D

Does it fix fake-killing it? then? or when you break it, how the model sometimes stays there for a short time?

Does it fix fake-killing it? then? or when you break it, how the model sometimes stays there for a short time?
When you fake kill it, the prop won't dissapear but the invisible brick will. Being able to walk through.
Hammer works.
Wand works.
Delete works.
Disapear does not work properly. (it instantly reapears)
Fake killing does not work properly. (instantly reapears)
Duplicating does not work properly. (always pointing north)

Conclusion: WE CAN USE PROPS ONCE AGAIN SAFELY!!!
« Last Edit: August 12, 2011, 07:23:58 PM by Kiwi »

Send2me, I have some plans for it then

Just so happens I remade my own prop system. It removes all console errors. The only problems I know of is when you duplicate props they loose their rotation and when destroying multiple props at once they tend to stick around for a few seconds.

Ephialtes duplicator forgets up practically every mod related to bricks. Send me a PM if you want it.
Edit: I'll also throw in an example prop to get you started.

Lol. I thought I'd clean up my code a tad bit before uploading. That was the one error.

I made it so you can't edit the raycasting/colliding/rendering on the props so that is why dissappearing and fakekilling/blowing up doesn't work.

Lol. I thought I'd clean up my code a tad bit before uploading. That was the one error.

I made it so you can't edit the raycasting/colliding/rendering on the props so that is why dissappearing and fakekilling/blowing up doesn't work.
I'm now working on making it so you can fakekill bricks.

I can't remember, but why can't we do what the Tree brick does? It is compatible with the brick physics, that would be nice for whoever wants to use props.

I can't remember, but why can't we do what the Tree brick does? It is compatible with the brick physics, that would be nice for whoever wants to use props.
The tree brick uses a BLB file for the model. Not a DTS. BLB files are very hard for doing models.