Since most of the active developers have since retired, I have decided to shutter FLHook development from the Forge.

The project is now available on Github: https://github.com/Friendly0Fire/FLHook

Merge requests are welcome by anyone who wishes to. This includes new plugins that may be distributed alongside FLHook itself.

Note that the version on Github has also been modified since the last SVN commit.

The forum post is fine, but the tutorial fox linked in said post is dead.

I believe this was done to sorta cache the systems which improved performance when actually loading the systems later on when a player logged/jumped. Don’t know why it’s iterating over bases though.

It can also be useful while doing system editing since some errors will pop up straight on server startup.

Nx, cut the crap out. That kind of negativity is neither warranted nor acceptable. If you have nothing useful to say, then say nothing.

I have no idea what you’re talking about on either point, sorry.

I’ve stopped believing this community could collaborate to such an extent years ago. We don’t really have the skilled manpower for such an undertaking anymore anyway.

I don’t think there’s any new game in this site’s future. Between developers now hosting their own forums and websites, reddit, and people being on the lookout for new games well before us, I don’t think we have a niche aside from Freelancer.

The only real reason to upgrade the site is to prevent it from eventually falling apart and allow it to remain a resource for future players and modders, however few they are. It’s a miracle this site even exists, considering the troubled times that spawned its foundation, it’d be a bit of a shame to see it just crash or get hacked one day.

I don’t disagree, but rather than trying to make a singular unified CMS as was the trend when The Starport started, I’d favor separate sites with a simple global navigation bar somewhere to go between them. Makes the creation and update process dramatically easier. The wiki can probably be updated directly from what we have now since it’s just MediaWiki with some crap added to fit in Xoops, but the forums are going to be a nightmare to port to anything and the downloads are half broken as is.

It’s just a big time investment for what I mostly see as an archive for a game of days past, which I don’t think w0dk4 or I have time for.

If we’re gonna do something new, it’ll be a new forum software (probably Vanilla or Flarum) without any home screen/news stuff that nobody uses and a separate, better curated/cleaned up downloads section (and maybe the wiki, it’s also pretty dead). I’d also completely redo the branding and color scheme.

Thing is, that transition is a pain in the ass, so it’s highly unlikely to happen.

This is a modified version of the 1.1 EXE which should fix the 25 fps issue. If you still find the need to limit the game’s FPS (which is very likely), I’d recommend using an external tool.

I suspect the session’s lifetime is not always (or ever) refreshed when just opening a new page, so the expiry can happen basically at any point and that’s what prompts a refresh.

I think we’re coming close to the point where we’ll have to ditch Xoops if we want to have a functional website for the future, but unfortunately I don’t think we have the manpower to redesign and port the site right now.

We’ve had that conversation many times already. “Abandonware” is not a legal term. The copyright on Freelancer will not expire for decades. Microsoft simply doesn’t care to sue people for sharing such an old game that wasn’t even that popular in the first place.

At this point, I don’t really care if people share links to download the game. It’s a pain in the ass to find a physical copy and it’s not available online legally. Just don’t interpret this to mean that it’s suddenly legal to download the game. If we’re ever contacted by Microsoft to pull the links, we will do so immediately.

It also of course has absolutely no bearing on whether Microsoft will do anything with the game. They won’t.

Freelancer only does two-sided rendering if the material type ends with “Two” (e.g. DcDtTwo). It’d be wasteful to have two-sided rendering on at all times.

Pretty sure adoxa means a plugin that just does a preprocessing pass to the INIs as they’re read by Freelancer. You’d just be able to use pos_begin and pos_end directly in the INIs.

The fact the game is open source and managed by the community rather than Microsoft also makes it a rather different beast.

If we ever got OpenFL or something, we could probably do a similar thing.

Oh man, I feel bad for you guys… Maybe we could also add a subdomain to Starport aliasing the workaround URL as further backup.

I like the idea of mirrors, don’t know if w0d has the time to work on that though.

That’s not how that works. We don’t have Freelancer’s source code, and please don’t ask about if we can get it. We’ve tried everything under the sun, Microsoft won’t open source the game.

No. You’d need to emulate x86 on the Pi’s ARM core, which is something difficult for a proper computer, let alone a severely underpowered one like the Pi.

Freelancer is best hosted on Windows. The bottleneck we generally see comes from the single-threaded nature of the game rather than any networking issue. You can do it on regular x86 Linux if you want, but it’s just more trouble than it’s worth, I find.

Typically with Freelancer the things either had a use that was removed or were going to be used, but never made it in. Either way, sounds like it’s safe to ignore/remove outright.