changing what box dropper drops
So, i've been building my first level, and i've hit a problem.
The basis for my level is keeping the same box throughout the entire level, while still allowing for the player to fizzle the box, whether by accident, or just out of stupidity.
At the start of the level is a prop_weighted_cube, "companion_cube". It has 2 outputs: OnFizzled room1_box_dropper instance:cube_dropper:trigger, and OnFizzled room1_box_dropper instance:cube_dropper_autorespawn:enable.
Of course, there's a box dropper instance (VMF filename being "instances/gameplay/cube_dropper_multiple_normal.vmf") by the Fix Up name of room1_box_dropper.
my problem is that later in this level, the player does not have access to this box dropper, but i still want them to be able to fizzle a box and get a new one from a box dropper later in the level.
I've set all the fizzlers in the second section of the level to have outputs that say: OnFizzleBox room2_box_dropper instance:box_dropper:trigger, and OnFizzleBox room2_box_dropper instance:box_dropper_autospawn:enable, but whenever the box (whether companion cube or normal cube that's spawned by the box dropper, it's the same) is fizzled, a new box spawns from the box dropper at the start of the level, and not the second dropper that's accessible to the player.
any help is appreciated and much desired, and i give thanks ahead of time to anyone who contributes.
You need a different instance if you have multiple box droppers.
instances/gameplay/cube_dropper_multiple_normal.vmf
I used that instance. That isn't the problem at all. That problem has already been discovered and fixed.
Maybe you should read what the problem is before you try to solve it.
instances/gameplay/cube_dropper_multiple_normal.vmf
If you don't have anything useful to say ould you please not say anything at all.. 
The basis for my level is keeping the same box throughout the entire level, while still allowing for the player to fizzle the box, whether by accident, or just out of stupidity.
At the start of the level is a prop_weighted_cube, "companion_cube". It has 2 outputs: OnFizzled room1_box_dropper instance:cube_dropper:trigger, and OnFizzled room1_box_dropper instance:cube_dropper_autorespawn:enable.
Of course, there's a box dropper instance (VMF filename being "instances/gameplay/cube_dropper_multiple_normal.vmf") by the Fix Up name of room1_box_dropper.
my problem is that later in this level, the player does not have access to this box dropper, but i still want them to be able to fizzle a box and get a new one from a box dropper later in the level.
I've set all the fizzlers in the second section of the level to have outputs that say: OnFizzleBox room2_box_dropper instance:box_dropper:trigger, and OnFizzleBox room2_box_dropper instance:box_dropper_autospawn:enable, but whenever the box (whether companion cube or normal cube that's spawned by the box dropper, it's the same) is fizzled, a new box spawns from the box dropper at the start of the level, and not the second dropper that's accessible to the player.
any help is appreciated and much desired, and i give thanks ahead of time to anyone who contributes.
What I would do is to disable the actions from the first dropper and enable the actions of the second wen you enter the second room with the cunning use of logic_relay's. Set the actions you have for the cube such as OnFizzled > relay 1 > trigger then have a trigger when you enter the second room to disable the first relay and enable the second. I made a demo map using this a couple of seconds ago and it worked fine.
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."
Sorry for misdiagnosing a problem, I'll be sure to accurately read future walls of text.
I mean, really, I try to help and you both reply telling me to, essentially, screw off? There was absolutely no need for the rudeness.
Honestly, it's like you're actively driving people away from this forum if this is how you're going to react.
There's no need to reply, I won't be checking back.
Thanks iWork925, I've been working with it some more, and there are still a few bugs with the droppers, but I think with what you explained, I've figured the rest out.
Cool, glad I could help out. Even if it was only slightly.
I mean, really, I try to help and you both reply telling me to, essentially, screw off? There was absolutely no need for the rudeness.
Honestly, it's like you're actively driving people away from this forum if this is how you're going to react.
There's no need to reply, I won't be checking back.
Good, I think your being sarcastic but you SHOULD read the problem before answering. If reading a 'wall' is too difficult for you, I think map troubleshooting is a bit out of your scope. Try reading 'The Very Hungry Caterpillar' and work your way up from there.
I wasnt telling you to screwoff, I was telling you to READ the problem and think about your answer BEFORE posting it. You signed up to TWP only one day before the thread was posted, your post count is still in the single digits and your answer did not help at all. It actually wasted precious seconds, which could have been used for someone to actually help.
Honestly, I am not trying to drive people away or go out of my way to get them to stay, I honestly dont car either way. Its not my site, active members do not affect me at all. If you did choose to leave, not a single fuck will be given, I can guarantee you that sir.
I replied anyway, just in case you dont follow your won advice.
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."