Freelancer Community Network
Reminder: Internet Explorer 6 or below are NOT supported.
HomeHome
ForumForum
WikiWiki
DownloadsDownloads
ForgeForge
Multiplayer Connection Tutorial
Collapse/Expand Random Image
Collapse/Expand Login
Username:

Password:

Remember me



Lost Password?

Register now!
Collapse/Expand Chat
Collapse/Expand Who's Online
75 user(s) are online (50 user(s) are browsing Forum)

Members: 0
Guests: 75

more...
Collapse/Expand Donations
Monthly costs: -30€
Income (ads): +5€
Donations (last month): +0€

Current balance: 55€
(last updated 04/2021)

Please make a donation if you want to help keeping The-Starport online:

Thanks!
Collapse/Expand Links
Collapse/Expand Advertisement
There are currently 34 users playing Freelancer on 37 servers.
September. 17, 2021
The Starport Forum Index > All Posts (Blinky)

Bottom Bottom   Previous Topic   Next Topic



Re: Vanilla Server - Advice for Retaining Equipment After Death
Just popping in
Joined:
2020/6/24 8:44
From South Africa
Group:
Registered Users
Posts: 5
Offline
An update on the above, upon further digging I discovered that the PlayerControl plugin wasn't being loaded, it appears to be due to the way PlayerControl's files should be installed, which don't work with FLHook 2.0.0. Here's what I've tried so far:

1 . FLHook 2.0.0 works with my server, but the PlayerControl plugin requires a "dlls" folder in the "flhook_plugins" folder, which isn't there by default. Creating it manually does not rectify the problem.

2 . FLHook 1.6.0 and 1.6.0-p3 both do not work with my vanilla 1.1 server, where FLHook.dll fails to load upon the server starting up. These versions of FLHook do however have the "dlls" folder that PlayerControl requires.

Can anyone advise how PlayerControl should be installed to a 1.1 vanilla server? Specifically, which versions of both FLHook and plugin should be used?

I have done my best to try and find different versions of both, mixing and matching to try and get both to work together as intended, with no success so far.

My thanks for your patience in advance. I'm very new to Freelancer modding, and have little in the way of programming experience.

Posted on: 7/19 9:41
Top
Topic | Forum


Vanilla Server - Advice for Retaining Equipment After Death
Just popping in
Joined:
2020/6/24 8:44
From South Africa
Group:
Registered Users
Posts: 5
Offline
Hello all,

I've been hosting a public vanilla server for a while now, where exploration and co-op is the primary goal, instead of PVP. As such, for the sake of improving the player experience, I am trying to let players retain unmounted equipment and cargo upon death.

It appears that the "death_penalty" option in the freelancer.ini file does not actually do anything, and applying any value from 0 to 100 has no intended effect.

I understand that the only alternative is to make use of FLHook with the "PlayerControl" plugin.

I have been able to install and configure FLHook to my server, but upon repeated testing and tweaking, regrettably I cannot successfully configure things so that unmounted weapons and cargo are indeed retained upon dying.

Does anyone perhaps have experience with this kind of setup? I was not able to find a previous forum post here or on Lancers Reactor on this topic with a confirmed solution.

For context, the primary reason for wanting to implement this change, is because of the famously buggy mine fields. Dangerous enemy ships are simple enough to avoid, and dying to them feels more fair. In contrast, dying to an invisible mine, which all do significantly more damage than the visible ones, feels like being cheated out of the intended experience.
Even the strongest VHF shield in the game can't take more than a handful of hits from invisible mines, so the situation is even more hopeless for players with middle or lower-end shields.

To sum up, my intention is to run the server as close to vanilla as possible, with only this relatively minor change, so that a player keeps their equipment and cargo after dying.

If anyone has any advice, or a potential solution in this context, I would greatly appreciate the help

Posted on: 7/18 17:52
Top
Topic | Forum


Re: Failed to make connection to list server
Just popping in
Joined:
2020/6/24 8:44
From South Africa
Group:
Registered Users
Posts: 5
Offline
Many thanks for your feedback. At the time of writing, I can confirm my server was able to connect to the list server again, much appreciated.

Posted on: 7/12 9:47
Top
Topic | Forum


Failed to make connection to list server
Just popping in
Joined:
2020/6/24 8:44
From South Africa
Group:
Registered Users
Posts: 5
Offline
Hello,

For approximately a year I have hosted a server titled " [ZA] South African Freelancers". In the last few days, my server has unfortunately not been able to connect to the regular list server. I can connect to my server over my own network, but looking at the graphs on flserver.de, it hasn't shown as online since about a week ago.

The only recent change of note is that I moved my server from an older machine to a newer, significantly faster one. After the move, my server was able to connect to the list server exactly as before, until the console started showing a repeating error of it failing to connect. Nothing changed on the machine I'm hosting from, or on my router.

This is what I have tried to resolve the issue so far:

• Ensured that the workaround patch is correctly installed. Both the gls_workaround and libcurl files are present, and added to the dacom.ini Libraries section.

• Port 2302 is forwarded for ports 2300-2400 in my router as before.

• IPv6 is disabled in that machine's Local Area Connection settings.

• No special mods are installed, apart from an HD Textures pack and a widescreen fix, which had not caused any problems before.

• The old machine still retains the original installation that's been running for about a year. Upon starting that older installation of the server up, it also fails to connect to the list server. I assume this means that the given installation of Freelancer and its settings are not at fault?

• Ensured that the Official 1.1 Patch is indeed installed.

• Disabled both my antivirus and firewall temporarily, but the issue persisted.

I am able to see and connect to other servers in-game, so I assume the issue lies with my own server or its machine somehow. What's perplexing is that the problem started abruptly, in the middle of a hosted session. Given my current situation, I do need to occasionally shut the server'machine off for extended periods, as the graphs on flserver.de show.

Can anyone advise whether the list server itself is having trouble right now, or if there is anything else I can try to get the server back online?
Could the list server have blacklisted or otherwise blocked my address as a result of my server starting up and connecting too often in a given time frame?

My sincere thanks in advance for your time and attention to this post.

- Blinky

Posted on: 7/9 16:31
Top
Topic | Forum


Greetings from South Africa
Just popping in
Joined:
2020/6/24 8:44
From South Africa
Group:
Registered Users
Posts: 5
Offline
Hello! Long-time visitor, first-time poster.

I'm based in the Western Cape of South Africa, and have been a serious fan of Freelancer since first playing it in 2005.

It was a big hit between my circle of friends in that time all throughout high school. We had no proper access to the internet then, so we had fun speculating about various ships and areas in the game amongst ourselves. Trying to determine where you could find the best equipment, which ships were optimal in certain scenarios, how many systems and secrets we were yet to find, etc.

The Borderworlds like the Omicron, Omega and Tau systems have a serious mystique, and were a real challenge for us to get to, so their unknown possibilities were especially fun to discuss.

I now run my own Freelancer server, something I've been meaning to do for many years. You can find it as "[ZA] South African Freelancers" if you're ever in the mood for a vanilla PvE experience!

The latency for European and Russian players is likely around 200, whereas North American connections range from 230 and up. Admittedly it's not ideal, but I've spent a lot of time playing with this kind of latency on "overseas" servers myself, so it should still be playable as long as the connection remains consistent. You're welcome to message me here if it isn't

Thank you for reading, and I look forward to contributing here in the future where appropriate.

Posted on: 2020/6/24 10:10
Top
Topic | Forum



Top Top



[Advanced Search]