fibanocci on 28/10/2014 at 15:23
Looks like the metaproperty FrobInert (and MostlyFrobInert) is broken in my gamesys. It works as usual in a new map.
I tried to delete the property in the hierarchy and made new one, but FrobInert won't work any more :confused:
How to fix that?
ZylonBane on 28/10/2014 at 16:28
Quote Posted by fibanocci
How to fix that?
Do it right this time.
I'm serious. It's not working because you didn't reproduce the metaprop correctly. And since you haven't given us ANY details about what you actually have done, this is pretty much the only advice anyone can give you.
I suppose I could also point out that deleting the metaprop and trying to reproduce it from scratch was a really bad move, since that broke its link with any objects that were already using it. :erg:
Yandros on 28/10/2014 at 17:01
Define "broken". If you add FrobInert to a concrete object which also has an explicit Engine Features > Frobinfo property, the metaproperty will have no effect. Metaproperties are lower priority than explicit properties on a concrete object, but they will take precedence over the same property on the archetype or a parent.
fibanocci on 28/10/2014 at 17:45
Quote Posted by Yandros
Define "broken". If you add FrobInert to a concrete object which also has an explicit Engine Features > Frobinfo property, the metaproperty will have no effect.
This.
If I start a new map and add FrobInert to a door or something, everything works as usual. I've read somewhere that some scripts could break metaproperties.
@ZB: I've put you on the ignore list. You're the only one there. Nice, isn't it? So you can stop trolling me. Find somebody else to play with.
LarryG on 28/10/2014 at 20:03
Quote Posted by fibanocci
I've read somewhere that some scripts could break metaproperties.
Can you be more specific about this? Where did you read this and what did it actually say?
Also, I think Yandros wants to know exactly what the situation is where you say it is "broken." Just what do you mean by "broken"? What is the setup that you are using where you experience this brokenness? Could there be an explicit Engine Features > Frobinfo property on the concrete object to which you are adding the metaproperty FrobInert?
fibanocci on 28/10/2014 at 20:19
I've put the metaproperty FrobInert on a door (add-->) or added via S&R.
This is no problem in a fresh map. I did it pretty often.
But in the current gamesys, FrobInert is not working any more. I wonder if FrobInert was disabled by accident on sim start or by some strange script failure.
Quote:
Can you be more specific about this? Where did you read this and what did it actually say?
I don't remember
LarryG on 28/10/2014 at 20:46
There is nothing to the metaprop if you look at it. It's just a setting of Engine Features > Frobinfo: {[None]; [None]; [None]}. What's there to break? No, my bet is that you either are failing to get the metaprop added by whatever means you are using, and/or you have explicit Engine Features > Frobinfo on the concrete which overrides the use of FrobInert. Also nothing I know of can change the metaprop itself, only add or remove it from an object. So I strongly doubt there is anything wrong with the metaprop itself. My advice is look harder at the concrete object in question.
As to the vague memory of some unidentified script(s) breaking metaprops, I wouldn't give that any credence. Incorrect parameter settings for scripts can result in any number of odd or unexpected behaviors, but unless a script explicitly deals with metaprops, I would discount the possibility that it could affect them on any object.
fibanocci on 28/10/2014 at 21:24
Quote:
...or you have explicit Engine Features > Frobinfo on the concrete which overrides the use of FrobInert.
Well, without the concrete FrobInfo (script) that door can't be frobbed. First I made that another door un-frobable (FrobInfo: None), then I made a copy of it and added the frobinfo again.
So how should I prevent the FrobInfo to override FrobInert in this case?
LarryG on 28/10/2014 at 21:53
You can't. You have to not specify the property on the concrete, and let it inherit it's frobability from its parent. Whatever is placed on the concrete will take precedence. So don't place that property there. The only way I know to avoid this is via property sets, where you use A/Rs to change the property on the concrete itself. But that's more complex to implement than adding / removing a metaprop.
