Node UTStats 2 Version 2.14.2

[UT Sniper (SJA94)]

I don't think I ever added delete user function to the admin area, you can ban the user to stop it being logged in.(I haven't really touched node-ustats-2 since I started work on node-utstats-lite it does have less features though)

If the user you want to delete is the only account you can run in a terminal <b>node deleteusers.js</b> in the main installed directory to delete all user accounts.

[gachimusa]

I don't think I ever added delete user function to the admin area, you can ban the user to stop it being logged in.(I haven't really touched node-ustats-2 since I started work on node-utstats-lite it does have less features though)

If the user you want to delete is the only account you can run in a terminal <b>node deleteusers.js</b> in the main installed directory to delete all user accounts.

thanks for the answering.
I run it(deleteusers.js) and worked fine

If I have performance issue on my server, I will plan to install node-utstats-lite.
(Personally, I want to record weapon-accuracy on utstats.)

[UT Sniper (SJA94)]

Yeah it's only an issue if your players are very anal about any sort of issue on servers with high tick rates.

It only took 20 years for the utstats issue to be noticed so you'll be fine on a casual/fun server.


Also updated first post with latest version:

Build v2.14.1 https://github.com/scottadkin/node-utst ... ag/v2.14.1

## Change Log:

**** V 2.14.1 Change Log:
- Added a new tab to match weapon stats, you can now view data by stats type, for example just kills for all weapons in one table.
- Added missing team total item usage tables.
- Item usage tables will now only show selected item table instead of all of the same type.
- Fixed dropdowns not being set to correct value on page refresh.
- Clicking on a Country in Most Popular Countries will now take you to the player search page with said country pre-selected.
- Fixed wrong player profiles being displayed in recent players(sometimes it would show the gametype or map profile instead of the real profile).

**** V 2.14.0 Change Log:
- New experimental player HWID admin tools(needs testing):
- Added force HWID to use a selected player name admin tool, you can assign a hwid to always import as a certain player name no matter the used name in the match.
- Added merge HWID usage into a single player, this will merge all player data with the selected HWID no matter what name is used, into a single player profile.
- Added HWID usage tool to admin area, shows hwid info and what names have been linked to it.
- Rewrote most of the player merging tools.
- Rewrote admin servers tools.
- Added new servers tool, merge servers, use this to combine two server stats into one.
- Servers are now updated by name instead of ip:port combination.
- Admins must now manually set server ip/port and passwords for the join servers url to be displayed.
- Rewrote the DropDown component as a function component.
- Fixed some country flags info being too big when you hover over a few country flags.
- Updated next.js to version 14

**** V 2.13.2 Change Log:
- Fixed efficiency column being type INT instead of FLOAT in table nstats_player_weapon_totals(node upgrade required).
- Fixed backup creator reporting it was finished before it was done.
- Added force HWID to use a player name admin tool.
- Added HWID usage tool to admin area.
- Added view current settings to view applied hwid to name settings.

[Skillz]

Question before I get started on this.

Well, couple questions, sort of. Anyway...

I intend to run this version of the stats on multiple UT servers. The web server will be hosted on a different physical server and the database will be hosted on a different physical server.

Will this handle this ability out the box or am I going to have to do some coding/modifying to get it to work like this?

[UT Sniper (SJA94)]

There shouldn't be any issues, just make the correct changes to the mysql variables in the config file to point to the server with the mysql database.
https://github.com/scottadkin/node-utst ... g.json#L13

I did start upgrading the site a few weeks ago but real life stuff has made it difficult to focus atm, but it's only a few more days and I'll get back to upgrading and refactoring. Version 2.15 will also be using a different mysql package so if you do run into issues it may be fixed when I release 2.15.

[Skillz]

Thanks, I'm going to start working on this tonight. Hopefully it goes smoothly.