Tannar on 20/9/2015 at 14:39
Quote Posted by Nameless Voice
Yes please. Changing the first-post title used to do that, but it doesn't seem to do so anymore.
Yeah, I'm not sure when that changed. But it's done now.
Daraan on 1/5/2016 at 13:59
Quote Posted by Nameless Voice
Updated to v.1.2.4.
This is mostly to make an official version with all the recent fixes that I've given to various people privately, though it also has a few new scripts and features since v.1.2.3.
This might explain why I have a different 1.2.4. Was wondering why the new(the one larry posted few posts above) was only roughly half the size. Old one was 1.11MB.
So i kept both for 'savety'.
--
And instantly a problem popped up:
I have a setup with
NVMetaTrapTarget="^physical"
which results in the following crash
Code:
Crash message: Link to invalid source or dest. (
0 --> MetaID
Reverting back to the other 1.2.4 or to 1.2.3 it's working as it did earlier.
After a lot of testing it seems the problem is fixed when I use "^
:physical".
But I'm not sure if you changed something there and this is now the correct way to do? Maybe that's one of the missing documentations Larry talked about?
-------------------------------------------------------------
Secondly I would like to ask if you could modify the NVTrigOBB to behave like the (
http://dromed.whoopdedo.org/public_scripts/trigobbspec) TrigOBBSpec script. So that you can actually choose the archetypes which triggers it. (best would be with a choosable MetaProp (instead/additionally to M-NotifyRegion).
Until now I have a setup which triggers at PhysEnter, but to get a hold on the target to add a metaprop and links I need the .target=^physical
But it's not a 100% save method but it works as intended but can fails when other elements like decoration are to close.
EDIT:
Maybe better alternative: If you could target the first/last object linked with a specific type like "^&Population" this would be a great and could be used elsewhere as well since sometimes only one object is linked.
Nameless Voice on 1/5/2016 at 22:25
It's smaller because it was compiled in a different IDE. The same scripts should all still be there.
What's ^:Physical even supposed to do? Wouldn't that try to find the nearest object that descends from some non-existent ":Physical" archetype?
Daraan on 1/5/2016 at 22:41
Well it needs to find the closest physical(-7) object. Yah
Since ^physical somehow doesn't work anymore I tried ^: similar to range detection ^<4:
All I can say with ^: it works
Nameless Voice on 2/5/2016 at 14:44
Try the new version of NVTrigOBB (see first post.)
R Soul on 2/5/2016 at 14:57
Splendid!
Yandros on 2/5/2016 at 17:42
That is definitely neither a trouchuss nor a greejus!
Daraan on 2/5/2016 at 19:52
Splendid, indeed. I will check it out. Thanks a lot.
Quote Posted by Yandros
That is definitely neither a trouchuss nor a greejus!
I'm not getting that.
Yandros on 2/5/2016 at 20:29
Sorry, it's a reference to a certain thread in CommChat, and not important.
Nameless Voice on 3/5/2016 at 00:51
It's a genius bonus. Or possibly a genious bonus!