"Pickup Energy 25" is a rather small unit, and, in my case (read: zoomed in a lot), the fact that the game considers that the player was near enough to the pickup while in reality being relatively far really bugs me.
I've tried to change the "Movement - Radius" value, but it doesn't seems to be it.

What am I supposed to do?
I'd also like to attach a model on the picking-unit until the Behavior applied by the fact of picking it up ends.

P.S. Also, I've change the text displayed when it's taken to be "Trapped!", but somehow, it doesn't appear when it is taken... why?
Oh, and another thing I'm trying to do is to prevent players from picking it up right after it has spawned (it should spawn as Red Tinted, and become Blue over-time). How to?

Is an ability used to pick up the unit? If it is then check the range on the ability.

Pickups are gay.

You need to adjust the PickUp ability.

Set these fields to whatever range you require:
Ability - Auto Cast Range
Stats - Range

You have to adjust both for there to be any effect. The way that it works is any unit with this ability will try to autocast it's effect on any nearby and eligible units. So for example, the HealthPickup100 will add 100 health to any unit within 1 range (default) and if the unit has less than max health, it will add 100 hitpoints to it.

To attach a model to a unit this way, it's a bit trickier.

Create a new actor, with:
Actor Type: Model
Based On: Model Animation Style Continuous
Doodad Type: Not Doodad

Set the fields
Art - Model to whatever model you wish to be attached to your unit.

Then, the easiest thing to do would be to copy these fields from an object like Carry Mineral Field Minerals.
Events +
Hosting - Host Site Operations +
Properties - Inherited Properties

Once you've copied these fields from the mineral object, and pasted them into your new model object. You'll want to edit the Actor - Events + to whatever you want to trigger this new model being attached to your unit:



In this example, when the Behaviour:Carry Mineral Fields is On, the model is created (presumably according to it's Hosting - Site Operations. And, when this Behaviour, is Off, the animation bracket (which is attaching the Model to the Unit) is turned off (or broken).

Post has been edited 2 time(s), last time on Jan 6 2011, 6:36 pm by Cardinal.

I've set both to 0.005, and I haven't seen a difference. >_>

Then it's to do with the Starcraft 2 limitations, unlike in Warcraft 3, Starcraft ranges operate in integers from say 1 (melee) to 13 (siege tank). Warcraft 3 ranges were more like 80 (ghoul melee) to 1050 (ballista). So you're a lot more limited especially in the lower-end of things.

<1 = 1

Are you sure about that? Anything below 1 will be equal to 1 in terms of range?
I don't think so... just think of the splash effects... they have real numbers as values of range from the center.

Remove the range completely, you don't need it. (Not auto cast range if you are using auto cast, thats something else)

I am pretty sure yes. Splash damage etc is done through the Effect field Search - which is completely different to Range. You could try as Temp says - remove the range from the ability completely and see if that has an effect? Otherwise you might need to create a workaround in which you pretty much copy what a 'pickup' type ability is doing (Create Persistent > Search Area > Validate > Cause Effect > Remove Unit). As far as I am aware that will give you more customisation in terms of the Search Area.