Bad visit entry 4294967295

robocop

adoxa wrote: After a look at your log (remote desktop helps), it is a faction (65) that is causing the error,…

Do you suppose it could be related to a player’s freelancer.exe file? If they have a modded file that say adds the Order, or maybe even a faction from another mod, could that generate this error?

adoxa

Having another look at the logs, it always seems to occur in space, so here’s another update to include the ship’s position. It also translates the system hash (vanilla only, for others trying this) and removes the indentation.

adoxa

Tracked it down to affiliation. When a player has no affiliation (no faction before their name, nothing flashes in your own rep list), -1 is returned to indicate as such. The client still passes this along to the server as a visited faction, though, which ends up as the bad visit entry. This is either a bug in the original code, or something that wasn’t meant to cause any harm. I don’t really think it’s anything to worry about, but if it bothers admins, I could write a simpler plugin to remove it (or perhaps FLAC/FLHook authors might like to add it directly there).

adoxa

Here’s what I can glean of the visit values. It’s a bit mask, so add these together.

0 - default value, not visited, nothing special
    1 - visited, will show on Nav Map/rep list
    2 - unknown, doesn’t seem used
    4 - mineable zone
    8 - “actively” visited (looted wreck is the only real meaning)
  16 - wreck
  32 - zone
  64 - faction
128 - hidden, never shows on Nav Map

Objects containing bases have 31 (with the exception of New York (Li01_01) having 30, presumably due to visit = 1 in the system file, or perhaps it’s just special).

? Offline

Just like to add to Visit 0. Can be applied to planets or moons or anything come to think of it that doesn’t show up on your navmap when you first visit a system but will do once you’ve been close to them. Haven’t figured out due to not trying that if you leave the visit = 0 entry off, will the object still behave as if the entry were still there?

adoxa

0 is the default, so no visit line is the same as visit = 0. I was even thinking of removing them all for the next JFLP.

? Offline

Thanks for clearing that up, was never completely sure that was the case

robocop

Well then, let me ask this.
Chips’ ServerOperator2 mod and FLAC (as well as IFSO) both allow you to change the reps of your players. With the SO2 mod you can set what rep the player will have on character creation. With FLAC you can change the character’s rep by profile (preset reps), or by individually modifying each faction rep.

With the SO2 mod there’s an option for a neutral rep. Upon character creation the new character is neutral to all factions and has no rep_group line in their file.

With FLAC there’s an option to ‘unlabel’ the players faction. This is typically done with players with a neutral rep.

Now, does each player HAVE to have a rep_group entry? that line typically looks like rep_group = li_n_grp or something like that. What if the player is completely neutral but has that rep_group added? Would they still show up in space as being affiliated with the Liberty Navy?

I’m not sure the lack of a rep_group is causing the 429 errors and if it is, I’m not sure that’s why my server keeps dumping. We’ve been running either the SO2 mod or our FLU mod for at least 5 years now and this dumping issue is only a year old.

Just curious… I’m not saying you’re wrong, I’m just not entirely convinced that’s the problem.

The list of visit entries is hugely helpful though, thanks.

Chips

Sorry to go off topic, but, someone uses the SO mod? Blimey!

Thanks for highlighting the visit codes and their corresponding uses Adoxa, I never really checked them all out so didn’t know what do which / what / where / when / how

robocop

Your SO2 mod was what got me into modding in the first place. We needed something server side that would add some features to our server without forcing a client mod. SO2 gave us the ability to keep interest involved in FLU and a groundwork to figure out what else we could do. The FLUAddon Mod was basically a continuation of your work. At one point we had about 23 optional serverside components we could activate. Most were separate additions that were incorporated into the FLU mod as time went on. Until they were confirmed to be working properly and not causing any issues they were left selectable.

That mod has been invaluable to us. Thanks for putting it together.

adoxa

I tested the affiliation using a local server (FL Hack’s dual multiplayer). With the rep_group line, no problem. Remove the rep_group line, the 429 entry occurs. Ergo, the 429 entry has always occurred for players with no affiliation, which is why I said I don’t think it’s a problem. I never said it was the reason for your dump, sorry I didn’t make that clear.

As for being neutral, but having rep_group. Well, I haven’t tested, but I suspect that initially you might have the affiliation, but as soon as you do something that changes your rep, you’ll lose it.

FreeBrenter

ok so i understand that to set the wrecks i need o change te visit value from 16 to 0 the only thing i cant get my head around is “where is the file that contains the value visit = 16?”. running a server thru hamachi for me and my mates and i am assuming this will make it so that i may revisit the wrecks in sigma 17 and 13 with the class 10 guns to grab them again. if this is not what will happen can you please point me in the right direction

robocop

The entry you’re looking for will be in the system ini file.

Here’s an edit to the Hosho Maru wreck in Omicron Beta which is configured in Ew02.ini.

<data file=“data\UNIVERSE\SYSTEMS\Ew02\Ew02.ini” method=“sectionreplace”>;Fix Recurring Loot Drops

[Object]
nickname = Ew02_suprise_ku_freighter_1

<dest>visit = 0</dest>
<source>
visit = 16</data>

It changes the visit entry from 0 to 16 making the wreck lootable only once by each character. Changing the values from 16 to 0 would make them lootable multiple times by every character. The wreck once looted, would be empty until the server reboots again…
I believe every wreck is labeled with a ‘suprise’ as part of the nickname. Note the mispelling of ‘suprise’.