Please or Register to create posts and topics.

Choosing the right reflective cube dropper instance

I've been having problems with the reflective cube dropper instances lately because valve doesn't update the VDC website anymore. The PTI dropper instances are defective and the "shared" instances don't even have an IO proxy. What instance functions like cube dropper normal multiple, but has a laser cube in it?

yishbarr wrote:
because valve doesn't update the VDC website anymore.

I was under the impression that the VDC was written and updated by the community - like pretty much all wikis. (I think thats what the C in VDC stands for.)

yishbarr wrote:
The PTI dropper instances are defective and the "shared" instances don't even have an IO proxy. What instance functions like cube dropper normal multiple, but has a laser cube in it?

I didnt know PeTi instances could (or should) be used in hammer. I also couldnt figure out what the 'shared' ones even do. BUT, its pretty easy to make a multiple reflecto cube dropper by making a copy of instances/gameplay/reflectocube_dropper_normal.vmf and changing it so it drops as many as you want.

Image
PortalStories.com
"Oh, in case you got covered in that repulsion gel, here's some advice the lab boys gave me: DO NOT get covered in the repulsion gel."

What do you mean the PTI instances are defective? I used them for my maps because I prefered their smaller size.

Place the instance in the map and change the keyvalues to what you need. Here's what I use:

item_fall_straight_down = 1

disable_autodrop (0=no/1=yes) = Should the first cube be dropped automatically?

disable_autorespawn = Should a new cube be dropped automatically once the first one is fizzled?

cube_type = use "2" for reflectorcube

connectioncount = 1

I thought that the cube type is reflective, so I wrote reflective instead of 2. I'll try that, thanks. I have a feeling that shared instances are supposed to be copied and modified.

If you have trouble with something like that again, you can just build such a map in the PTI and then export it to Hammer to see how those options are used and what inputs they need. :thumbup:

From the top of my head 1 should be normal cubes, 2 reflective and 3 spheres.

What about companion?

Image
PortalStories.com
"Oh, in case you got covered in that repulsion gel, here's some advice the lab boys gave me: DO NOT get covered in the repulsion gel."
iWork925 wrote:
What about companion?

Cube type 1. Type 0 is regular.

My YouTube Channel: https://www.youtube.com/user/Camben24
Aperture Science: We do our science asbestos we can!
CamBen wrote:
Cube type 1. Type 0 is regular.

Ah, of course, sorry. Oddly enough the Frankencube isn't 4 but 6.

Edit: I had too much time on my hands. 4 is an old-Aperture-cube, 5 is a reflector-cube again.

yishbarr wrote:
The PTI dropper instances are defective and the "shared" instances don't even have an IO proxy

I believe those instances are used to be part of other instances. If for example you check into the normal cube multiple dropper instance you'll see instances inside, those are 'shared' type instances and that's why they haven't got the I/O proxy (the I/O proxy is in the "bigger" instance).

ImageImageImageImageImageuseful tools and stuff here on TWP :thumbup:
[spoiler]ImageImageImageImageImage[/spoiler]

And a lot of those seem to have been before proxies were added. Some include parms for naming a relay to drop the cube, which seems ridiculous.

Falsi sumus crusto!