Adoxa's "Territory" and "Zone" plugins

Thaddeus wrote:

Would it be an idea to ignore ALL spherical zones?

well, no. I would have to object to that because most hazard zones are spherical. I like being warned that I’m in a radiation zone or a gas pocket

Whoops, now i have an idea specially for radiation, and may be drag/interference. Fl can’t handle too much zones in one place(hangs), so let’s define virtual zones that will be overriding “damage”. Plugin should start tracking player position when he’s got in a zone, once his ship in a magic XYZ inside it the damage value gonna be changed. Kind of smoothed change, but not quite smooth, just more variance offer.

?

@Moonhead

I ignore spherical zones >= 100k, assuming they cover the entire system, so basically the system is the zone, there’s no need to say it twice (e.g. Chugoku/Okamura Cloud and Sigma-13/Crow Nebula). Mostly I did it so other zones would show up. E.g. Crow Nebula has interference, which would block the Yanagi Pocket.

You’ve got it the wrong way round - because it is a space, there must be an ids_name which points to it. The process would be:

• activate your mod;

• go to your real systems folder (I guess Freelancer\DATA\UNIVERSE\SYSTEMS\LI07)

• turn off read-only on li07.ini (or change the option in FLMM before activating);

• search each ids_name in [Zone];

• I think you’ve kept vanilla factions (or at least their ids), so renumber starting from 196846;

  [Zone]
  ids_name = 458752 ;whatever FLMM generates

  [Zone]
  ids_name = 458754

  replace with

  [Zone]
  ids_name = 196846 ;458752

  [Zone]
  ids_name = 196847 ;458754

• now when you visit the zone you should see a faction, which you can trace back to the zone;

• alternatively, start with 1286, as that’s just A-N (and 0-9 if you’ve got a lot, or if you’ve only got less than 10 start at 1301 and you’ll get its number directly);

• if it’s still a space, send me li07.ini and I’ll see if I can work with it.

I added those zones to fp7_system (originally li01, but the bottom two zones were swamped by existing zones). Jumped to the center of each, got the expected entered message; jumped out, got the expected left message. The flashing name is probably related, in that it sees overlapping zones, the first resets and only the last gets displayed. Should have been fixed with the above attachment, but it’s always possible I missed something else. Looks like I’m going to need the entire file.

The first test I made, though, did give me a blank name. That’s because my %Zv name remapping only works with standard zone ids, or with Names installed.

I then added unnamed zones before and after.

[zone]
nickname = empty_zone1
pos = 90000, 0, 25000
shape = SPHERE
size = 4800

[zone]
ids_name = 261208
nickname = zone_Li07_pop_colorado_gate
pos = 90000, 0, 15000
shape = SPHERE
size = 4800

[zone]
nickname = empty_zone2
pos = 90000, 0, -25000
shape = SPHERE
size = 4800

Jumped to the named zone, got the entered message; no message jumping to either of the other zones.

Just send me the ids_name-edited file and let me test the same thing you’re testing.

Okay. I found the first three zones above (using 9, 8 and H) to work as expected. The last zone (G) showed up as blank. Aha! However, that was due to the edited ids_name being overridden by its original (590037). Removing that showed the new name of that zone (Zone_Li07_Quarry_West) - it has spacedust, so was given precedence over Zone_Li07_Fargo_exclusion. I didn’t experience repeated names.

Now, after all that, I rewrote Zone so that it initially displays all the zones you’re in, in decreasing order of size. It also treats a name of a single space as no name (for those tradelane zones) and fixes the remapping.

Its caused by some of the vanilla tradelane zones having an ids_name specified. deleting the line (or adding your own specifics) cures it and tadelane zones dont really need names, also Zone_Bw01_Tradelane_1 has the same issue - maybe more haven’t checked through them all yet.

message is 60246 in resources

as in you have “left” zone

not because its a left tradelane ring
edited for writing bs

Moonhead wrote:
Weird, I couldn’t find it with FLED-IDs. Oh wait, iirc FLED-IDs doesn’t check resources.dll. I thought common.dll was the relevant one that was missing, so I used Hex Workshop to look into it. Totally forgot about resources.dll. Why can’t FLED-IDs look into it anyway?

FLED-IDs only reads the dlls specified in the in [Resources] of the corresponding freelancer.ini.
So adding “DLL = resources.dll” in that section will do the job.

Moonhead wrote:
Reminds me I still gotta try swapping those trade lane rings 90°. It would make more sense if they were juxtaposed horizontally. Then Liberty and Rheinland should have Right lanes, and Bretonia and Kusari Left lanes

AFAIK there are issues with this… because the ship will bank/spin/turn its vertical axis to that of the vanilla-vertical-Tradelane and such… Don´t know if this has been already fixed…

Greetings J.R.

I can confirm that horizontal trade lanes work just fine. We’re using them in Broken Bonds.

As to the to subject at hand. We’ve been using the Territory plugin for a while, and the update is very much welcome. As always, adoxa, awesome stuff!

In my mod the Galileo System is not independent but devided as shown in the image (the blue circles are dark matter clouds, and the red line is the interterritorial border).

So when you enter from the Shikoku gate you’re in Kusari, and when you enter from the Colorado gate you’re in Liberty.

If this is the case, in any system (even if it’s crossed by multiple interterritorial borders), would it be possible to expand the territory plugin, or somehow different, to show a message when you enter another territory within the system?

Have you tried to add named zones which are named, for example “Galileo-System, Kusari” etc.?

@Skotty

Thanks for your reply. But I mean a message is only shown when you enter/leave territory, not for any zone.

For example, when a zone has comment = Territory.