Since Krinadon made all those back-end changes, I've been experiencing significant lag on Sylestia. (Just Sylestia, no other sites). The lag occurs all over Sylestia but seems to be at its worst on the Inventory page.

On the Inventory page, seconds pass before the arrow changes to a hand when I hover over a clickable item, and sometimes it won't change at all, meaning I can't click the item. Refreshing the page a time or three takes care of this, but then there's another lag when I succeed in clicking the item. Accompanying this weirdness is another weirdness: when the click is successful, sometimes the entire page view "bounces." Refreshing the page may also cause a bounce. These problems occur both with and without my VPN--no apparent difference.

Thought I should let you know. It doesn't make the game unplayable, but it is annoying and probably indicates that something is wrong.

The issue you're describing sounds like just the natural lag a device has downloading all of the raw HTML data from the server on a page load and the Inventory is very guilty of being bad at that with how it's built. Exploration is another really bad source of that.

The changes made to the server actually should have improved this very issue as it was one of the core things I changed to the http server - better/modern bundling of pages with a lot of heavy assets (images). For me, it was a night and day difference loading some admin pages I have - one literally went from ~20-30 seconds to less than 2-3 seconds.

What device/OS are you using where you're experiencing this lag?

Do you experience the lag every single time you load the page?

Device is a PC, an Inspiron 3670, Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz (2.90 GHz). OS is Windows 11 Home, version 25H2, build 26200.8655.

The lag happens every time I do anything on the Inventory page; however, the duration of the lag varies a great deal from one action to the next. So far I can't identify a pattern to the incidents of greatest lag.

During Exploration, there's sometimes no discernible lag at all, and when there is lag, it seems brief.

So, I do think that what I said in my previous post was correct. So our http server, which is basically the 'server' (software) that runs on our server (the hardware) and is the handshake between you and the physical server on every single connection. We have been using a very outdated method of processing these handshakes that limited how many things could be passed from one to the other at a time. This caused asset-heavy pages, like the Inventory, to take a very long time to load - connection wise. Meaning, you'd navigate to your Inventory and for a literal few seconds, your browser and our server were handshaking to transfer the hundreds of images from our server to your browser. However, from your perspective, things were 'fine', but the total load time was quite literally probably seconds as the whole page filled in.

A few days ago, I updated our http server's configuration to use modern standards, especially for asset-heavy sites, such as Sylestia. So now, when that handshake happens, our server can bundle the literal 1000+ images all in one package and send the entire thing to your browser super fast (micro seconds). So, server-side speaking, the speed was magnitudes faster. However, now your browser has to figure out what to do with these 1000+ images. If the device was powerful enough, it could just churn through it w/o much issue. However, most people don't have powerful devices so parsing through 1000+ images simultaneously was causing browser bottlenecking - this was the lag you were experiencing.

The proper solution is to fix the problem rather than handicap our http server. So I went ahead and basically refactored the whole back-end code for the Inventory page. I made three significant changes. First, the Inventory now only loads one single tab at a time instead of all 20 tabs. So you're literally now only loading 5% of the data per page load. Second, all "Empty" slots were actually images previously. These have now been converted to CSS. So now there are way less images to load based on however many empty slots you have. And third, you're no longer forced to reload the page when opening containers and such - the page is persistent and the Inventory just automatically updates.

So, in conclusion, for your specific issue with the Inventory, it should be pretty much completely resolved now. It should be very smooth for everyone to operate the Inventory page now.