-
Posts
-
-
.thumb.png.b8c670f34de56a5b725691b17807071d.png)
First of all, its great to finally have something meaningful to discuss on this forum and good job pushing this community forward, even if its mostly dead. I always wondered why, in the last 15 years, no one has properly documented any of the source code (acis mobius) or at least exposed common functionality through something like a rest api, which is straightforward enough for most people to understand and use. I have some technical questions since im really interested Regarding real time features like maps and enchanting are you using technologies like grpc? And what happens when both a logged in player and panel try to enchant the same item at the same time? Do we run into a race condition how do you handle that ? Regarding fake player system external models calls typically take 1-2 seconds to respond, while an local models might take around 200-300ms. During that time a lot can happen in game. So when the plan becomes stale you override it and wait for the new one meaning the node handles everything in real time and the LLM simply sets the goal asynchronously. Is that the correct understanding ? Regarding the security aspect a lot can go wrong when exposing crucial server logic to the open web (experimental is good). My real concern is the mcp in the panel where a lot can go wrong with bad user input. Wasn't the game client always the limiting factor for l2j? -
Migrating a legacy Interlude server to PostgreSQL while adding real observability is basically forcing 2006 MMO engineering to attend a 2026 infrastructure conference at gunpoint. PS: which revision of aCis? PS: 🧻what was broken during this whatever you call it. AAC Guard beign asked to adapt to this be like: - Creating bugs since early 2018 -
-
-
-
Topics
-
.thumb.png.779cbf1c3e4339ec59bca10063c412ab.png)
Recommended Posts