Target.OthersSaved

[Shifty Geezer]

I understand what this does, but can someone quickly describe how this works? I'm thinking that the same object that has many changes applied (eg switch or door) could result in a lot of redundant messages being sent to new players, and a big, memory hogging list being generated. Or is OthersSaved smarter than that?

[cmifwdll]

When an RFC is sent a UID is generated for that RFC. This is a combination of the sending TNObject's ID (which itself is unique) and the RFC ID (or function name).
Serverside, when a forwarded packet that's designated to be saved is received, it iterates the channel's saved RFCs searching for the UID. If the UID is found then the value is updated, if it's not then a new saved RFC is created.

In short, the value will be updated if the RFC has been seen before. So, no redundant messages or big lists

[Shifty Geezer]

Good to know, although that also means an overhead in searching for existing UIDs, so ideally I guess it's to be avoided if one can. At least as an optimisation.

[cmifwdll]

Hardly any overhead at all:

1. for (int i = 0; i < rfcs.size; ++i)
2. {
3.         RFC r = rfcs[i];
4.  
5.         if (r.uid == inID && r.functionName == funcName)
6.         {
7.                 if (r.buffer != null) r.buffer.Recycle();
8.                 r.buffer = b;
9.                 return;
10.         }
11. }
12.  

As someone that often optimizes *too* much, I wouldn't bother limiting OthersSaved usage. The utility it provides is extremely valuable, and its cost is practically nil.

[ArenMook]

What cmifwdll said. There is pretty much no cost, although if you're really worried you can use IDs instead of function names to eliminate string comparisons.