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.

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

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

iWork925 wrote:
What about companion?

Cube type 1. Type 0 is regular.

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).