I am creating a chamber where I am having a personality core run on rails around a room talking to the player. Unfortunately, I am having problems finding a way to keep the player from being able to grab the core, which breaks immersion into the chamber. I want entrance door to open with the core right in front of the player, so I don't want to just put the core out of the players reach. If I can't find a way to do it, I can still play it off like it is an easter egg by having text pop up on the screan saying that the player found a cool little secret, but I would prefer to actually make it so the player cannot pick it up. Can anyone help me with this?

Hey!

A quick workaround would be to surround it by a func_physbox textured with the invisible texture and checking its flag "ignore +USE for Pickup", and parent this func_physbox to the personality core.

Ok, Ill give that a try.

Make a logic_auto fire "OnMapSpawn -> Personalit_core -> disablepickup

portal2tenacious wrote:
Make a logic_auto fire "OnMapSpawn -> Personalit_core -> disablepickup

Oh lol, I didn't check out for this entity's inputs

I tried the first idea, and it didn't work. But the second Idea worked perfectly. Thank you so much.

Goldenknighttim wrote:
I tried the first idea, and it didn't work. But the second Idea worked perfectly. Thank you so much.

Excuse me but the first idea DOES work... you might haven't set it up correctly.

It's important to:

• Tick the flag "Ignore +USE for Pickup"
• Untick the flag "Generate output on +USE" (obviously)
• And make sure that you surround all the model's bounding box with the func_physbox, otherwise you can confuse the engine when pressing +Use!

LOL, yesterday I spent like 45 minutes myself checking for the reasons why the player "got tired" and dropped the radio prop (surrounded by and parented to a func_physbox) after carrying it on for a while... and that was because I dismissed the little thin antenna coming from it upwards >.<, and didn't surrround it completely; therefore I was confusing the engine everytime I pressed +Use and sometimes this +Use was applied to the radio prop itself (a prop_dynamic) not to the func_physbox, and I only discovered all that after turning 'developer' to 1 and checking that a +Use input was generated to the radio itself instead of the physbox

I'm attaching a test map for you to check. There are both, the .VMF and .BSP, take a look.