[FEATURE] Feature Parity + QoL Improvements

[dlikedior]

Overall, I think fxManager is a great alternative to txAdmin. It has a much cleaner design, but it's currently missing several core features that are available in txAdmin. I know it's new and will take some time but these are some suggestions, as well I am not sure if you can track the "users" activity on the server similar

Feature Suggestions

FxServer

Under the FxServer section, consider adding the following options:

• Startup Arguments
  • Allow additional command-line arguments to be passed to the FXServer instance (e.g., Node.js CLI flags).
  • Warning: This option should rarely be used. Commands and convars should be configured in server.cfg instead.
• Auto Start
  • Automatically start the server when FxManager launches.
• Path Completion
  • When linking a server, automatically append the appropriate executable (FXServer.exe on Windows or the Linux FXServer binary) if the user selects the server directory instead of the executable itself.
  • I ran into this issue when I selected the server folder without specifying FXServer.exe. Automatically completing the executable path would make the setup process more user-friendly and help prevent configuration errors.

Allowlist Options

• Add support for the External Allowlist Resource recently introduced by FiveM.
• Add the remaining allowlist configuration options that are currently available in txAdmin.

Networking

• Allow the web/UI port to be changed so it can coexist with, or match, the port used by txAdmin.

Login with Cfx.re / Discord

• Add support for OAuth authentication using Cfx.re and/or Discord.
• Allow administrators and moderators to be assigned using their FiveM (Cfx.re) identifier or Discord identifier, rather than creating separate local accounts.

Insights Tab

• Add an Insights tab that provides an overview of server and player statistics, similar to the analytics dashboard found in other server management panels.
• Include metrics such as:
  • Top crash reasons
  • Total player playtime
  • Top 10 players by playtime
  • Peak and average player counts
  • Session statistics and trends
• Enhance player profile pages with activity insights, including:
  • Monthly activity heatmap, similar to GitHub's contribution graph
  • Days active
  • Total playtime
  • Recent sessions and play history

Migration

When migrating from txAdmin, also migrate the following settings:

• Restart schedule
• Allowlist settings
• Discord settings
• Ban settings

[Maximus7474]

Happy to hear that the project pleases you, thanks for the suggestions here are a few initial comments I've got about it:

• FXServer
  The current phase of the project is initially based on providing a stable solution with base features before expanding the usability of it further.
  Startup parameters will be added during this early access phase, auto-start can also be considered.

• Allowlist
  The "External allowlist" system is only a convar, txAdmin didn't technically need to add that feature into it, you could just put it in your server.cfg instead. We talked about all the convars that can be used on a server, and have been looking into solutions for using them on the panel. But yes, I can see the use of having an extra field in settings for setting that.
  I'm unsure what "remaining allowlist configuration options" you're referring to.

• Networking
  You can already set the port via the environment variable PANEL_PORT

• OAuth
  It's planned, as seen on the login page. Just need to get around implementing it, which ofc will lead to changes on creating admin accounts.

• Insights
  To be honest, the ideas a neat but some are a bit out of scope for the project with our current plan. We'll definitely be talking more about them internally.

[dlikedior]

Thanks for the response to the suggestion;

Allowlist
The "External allowlist" system is only a convar, txAdmin didn't technically need to add that feature into it, you could just put it in your server.cfg instead. We talked about all the convars that can be used on a server, and have been looking into solutions for using them on the panel. But yes, I can see the use of having an extra field in settings for setting that.
I'm unsure what "remaining allowlist configuration options" you're referring to.

I'm talking about the "External Whitelist Resource" and "Approved Identifiers" method.

Insights
To be honest, the ideas a neat but some are a bit out of scope for the project with our current plan. We'll definitely be talking more about them internally.

This was a good feature in the other panel that was just deleted for reasons, I think it provided server owners valuable insight like your most popular days, times, etc. Shows your server player count over days, and shows a lot which is pretty good to help server owners.

[Maximus7474]

I'm talking about the "External Whitelist Resource" and "Approved Identifiers" method.

That is already possible, just set the whitelist setting in fxManager to none disabling it (which is effectively what tx's "External Whitelist Resource" does) and the "Approved Identifiers" method is also present, still in it's early stages as players connecting to the server won't send a request that can be approuved (not sure how widely used that one is).

This was a good feature in the other panel that was just deleted for reasons, I think it provided server owners valuable insight like your most popular days, times, etc. Shows your server player count over days, and shows a lot which is pretty good to help server owners.

@FjamZoo has taking it up to do these, he liked the idea #54

[dlikedior]

That is already possible, just set the whitelist setting in fxManager to none disabling it (which is effectively what tx's "External Whitelist Resource" does) and the "Approved Identifiers" method is also present, still in it's early stages as players connecting to the server won't send a request that can be approuved (not sure how widely used that one is).

That's good I didn't see it there when I checked.

@FjamZoo has taking it up to do these, he liked the idea #54

Looks great, I am just saying an "Insight" page would be good? Also, what a migrating the whole txData folder you just point to it?

[Maximus7474]

Looks great, I am just saying an "Insight" page would be good? Also, what a migrating the whole txData folder you just point to it?

No only the playersDB.json is imported during the setup process.

[FjamZoo]

Theres a few things we are doing, scoping convars to ONLY having whitelist stuff is quite stupid.

There are 10s of undocumented very need to know convars in fivem that I also want to intergrate and a single user interface telling players what each convar does and what we would recommend using, something one cannot just do with asking ai and with our 10+ year accumulated experience I think fxmanager is the place to do it.

I already started scaffolding and documentation shit here: https://github.com/fxManagerProject/fxManager/tree/feat/settings-convars-tab

feel free to take a look if you wish.

[dlikedior]

Can you add a feature where we can re-import our txAdmin data settings that override everything? Including players, etc?

[Maximus7474]

Sorry forgot to answer, those last few settings that have equivalents only take little time to set.

Not really worth creating an extra importer just for that.