-= Gametoast.com =-

i need to know if there is some sort of way to make it so that if you unlock an award weapon then it will always be unlocked (for the rest of the map at least). it would be like the 30 second grace period but longer, as in forever, and would last through more than one death. does anyone know how to do this?

That happens automatically when you unlock "Legendary" status or something. I'm not sure if you can do it otherwise.

Fiodis wrote:That happens automatically when you unlock "Legendary" status or something.

It's been awhile, but I think you hit Legendary around 60 medals or so, I forget. Fiodis is right, when you reach Lengendary status in that award you start the match with the award and keep it forever.

im rather sure the awardsystem is hardcoded becuase its works together with the profilestats and ive never seen or heard of any script for it.

You could possibly simulate this effect through LUA. Use SetProperty to change the weaponname of the slot that would be replaced by the award weapon. You would have to respawn, though.

I may be wrong about using SetProperty in conjunction with WeaponName, though.

let me rephase this.

i need this to work on multiplayer and i need it to make you have to unlock the award at least once then you can have it the rest of the match. would there be anyway to do this or as duck said is it hardcoded?

CressAlbane wrote:I may be wrong about using SetProperty in conjunction with WeaponName, though.

You're close; it's SetClassProperty rather than SetProperty.

And that wouldn't work on MP. As duck said, the awards system is probably hardcoded, though whether you can achieve what you want through some other means I don't know.

Fiodis wrote:

CressAlbane wrote:I may be wrong about using SetProperty in conjunction with WeaponName, though.

You're close; it's SetClassProperty rather than SetProperty.

And that wouldn't work on MP. As duck said, the awards system is probably hardcoded, though whether you can achieve what you want through some other means I don't know.

Thanks. I've been wondering why SetProperty didn't work sometimes.

Fiodis wrote:

CressAlbane wrote:I may be wrong about using SetProperty in conjunction with WeaponName, though.

You're close; it's SetClassProperty rather than SetProperty.

And that wouldn't work on MP. As duck said, the awards system is probably hardcoded, though whether you can achieve what you want through some other means I don't know.

ok then, i guess people will just need to be extra careful if they get an award.

CressAlbane wrote:

Fiodis wrote:

CressAlbane wrote:I may be wrong about using SetProperty in conjunction with WeaponName, though.

You're close; it's SetClassProperty rather than SetProperty.

And that wouldn't work on MP. As duck said, the awards system is probably hardcoded, though whether you can achieve what you want through some other means I don't know.

Thanks. I've been wondering why SetProperty didn't work sometimes.

SetClassProperty works on most things in an odf file, and it affects the entire class of units with that odf. Changes made via SetClassProperty will require a unit to respawn (or at least re-enter and exit a CP) to take effect.

SetProperty only works with instance properties. Instance properties are properties of single units/objects, and don't require a unit to respawn before taking effect. A list of valid instance properties can be found in Battlefront2_scripting_system.doc. Also,

AceMastermind wrote:

DarthD.U.C.K. wrote:...i discovered that you could put any ODF property under the [InstanceProperties] tag and they would become editable in ZE...

There's nothing in the documentation that says you can't do this but it's cool to know you can. Instance properties allow you to customize specific objects in ZE, for example if you place a destructable crate ODF in ZE 10 times and you want 1 of those crates to have a different MaxHealth value than the other 9 then you can customize this property for that particular crate instance. You can't just use any ODF property though, the properties you use must be supported by whatever classlabel that object ODF uses.

Hope that clears things up.

Ontopic: The real solution to this is to have everyone who plays go and get legendary in the weapons. Hardcore players can do it in a couple days(I know, I did it on the PS2 )
Matter of fact, I was pretty sure someone made a mod designed for getting loads of awards.

THEWULFMAN wrote: I personally have more use in my mods for SetProperty, for instance I use it to change the plant's model depending on the weather, so that they glow at night. The only issue is you have to do it for every plant, and there is like 150 plants

that makes me wonder why you dont use classproperty on them?!

DarthD.U.C.K. wrote:

THEWULFMAN wrote: I personally have more use in my mods for SetProperty, for instance I use it to change the plant's model depending on the weather, so that they glow at night. The only issue is you have to do it for every plant, and there is like 150 plants

that makes me wonder why you dont use classproperty on them?!

Well I doubted it would work. Like Fiodis said, it would need to respawn. Unless props work entirely different with SetClassProperty.