diff --git a/docs/cache_wiping.md b/docs/cache_wiping.md
deleted file mode 100644
index aa6c2e050..000000000
--- a/docs/cache_wiping.md
+++ /dev/null
@@ -1,7 +0,0 @@
-### Cache Wiping
-
-This feature was requested many times and in the end we decided against putting it into txAdmin for the following reasons:
-- Its just not necessary with the newest builds of FiveM anymore.
-- It can be dangerous considering that not configuring it correctly might end up recursively wiping out important files.
-
-More info: https://forum.fivem.net/t/why-people-delete-the-server-cache-folder/573851
diff --git a/docs/feature_graveyard.md b/docs/feature_graveyard.md
index 419cdad4b..1ad6d6b1a 100644
--- a/docs/feature_graveyard.md
+++ b/docs/feature_graveyard.md
@@ -6,7 +6,7 @@ And as part of the process, we "retired" many features and parts of our code bas
 - **Admin add script:** Now its done via the master account creation UI flow, and the Admin Manager page;
 - **Config tester:** With the gained knowledge of the edge cases, it became way easier to implement better checks and actionable error messages on the settings page;
 - **Resources injector:** With the integration with  FiveM, our plans for it changed drastically. It may or may not come back, meanwhile it was removed to prevent issues;
-- **Automatic cache cleaner:** This feature were created due to the vast number of requests, but in the end this "common knowledge" was based on misinformation, therefore it was removed since we don't actually need it;
+- **Automatic cache cleaner:** This feature were created due to the vast number of requests, but in the end this "common knowledge" was based on misinformation, therefore it was removed since we don't actually need it [(more info)](https://forum.fivem.net/t/why-people-delete-the-server-cache-folder/573851);
 - **SSL support:** With the rework of the entire web layer of txAdmin in preparation with the FiveM integration, we ended up removing this (tricky to implement) feature. As of 2024, we no longer believe that txAdmin is the correct place to deal with HTTPS encryption. If you want SSL, setup a self-hosted reverse proxy (nginx, caddy, etc), or preferably set up a [Cloudflare Tunnel](https://www.cloudflare.com/products/tunnel/);
 - **Experiments:** Well... not much to experience with right now;
 - **Discord static commands:** I don't think anyone ever used it since they can do it with basically any other bot;
diff --git a/panel/src/layout/PlayerlistSidebar/Playerlist.tsx b/panel/src/layout/PlayerlistSidebar/Playerlist.tsx
index 68b02257d..f766ea94f 100644
--- a/panel/src/layout/PlayerlistSidebar/Playerlist.tsx
+++ b/panel/src/layout/PlayerlistSidebar/Playerlist.tsx
@@ -202,7 +202,7 @@ export default function Playerlist() {
 
     // The virtualizer
     const rowVirtualizer = useVirtualizer({
-        scrollingDelay: 0,
+        isScrollingResetDelay: 0,
         count: filteredPlayerlist.length,
         getScrollElement: () => (scrollRef.current as HTMLDivElement)?.getElementsByTagName('div')[0],
         estimateSize: () => 30,