Jump to content

Hetjax

Members
  • Posts

    8
  • Joined

  • Last visited

Hetjax's Achievements

Refugee

Refugee (1/15)

0

Reputation

  1. I also can confirm this bug. its appearing since A20. its seems like the decorations getting regenerated everytime a player enters a chunk for the first time, even if another players already discovered the chunk. we had a workaround in A20 for this. we removed all decorations from xml and before we applied this xml, we let the maprendering of alloc discover all chunks. this would generate all decorations once and prevent them from being generated multipletimes.
  2. This issue is caused by quests. its kinda random if it happens or on a quest or not, maybe its related to the kind of poi. fetch quests causing it the most. As workaround you could simply edit the dialog.xml and remove the possibility to start quests at trader.
  3. ah, yes then you missunderstood that. I meant the both logline didnt appear anymore: [EOS-ACS] Got message for unknown client number[EOS-ACS] Got action for unknown client number
  4. Hi thanks for your affort and fast response! I dont understand what you mean with "you said you don't get log files from the server anymore" i get logfiles all the time. maybe you missunderstood something. My server is validated completely and multiple times. since the A21 Naiwazi Gateway version came out today, this problem is obsolete for me since it only appears on vanilla hosted server. but i heared from other high pop servers which hosts vanilla, that they are running into the same issue. maybe this needs a certain amount of players online, or multiple players with an older build to reproduce. very hard to guess tho 😕. did you had a b324 client connected while you joined with an b317/b321 client? it could be possible that just the b324 client will be disconnected and not the one with the wrong build. i could suggest you the following scenario: 1. Server on b324 with an b324 client online. 2. keep the b324 client on the server while joining with an b321 client 3. keep the b324 client on the server while joining with an b317 client hope thats gonna help somehow :)
  5. Summary: Connecting to an b324 A21 Stable server with an older build will disconnect all players. This bug can be used to attack other servers and constantly kick all the players. during this behaivor the following logs will be thrown: [EOS-ACS] Got message for unknown client number [EOS-ACS] Got action for unknown client number Logs: https://pastebin.com/zZYnmvH1 password: vi1rLu5H3k Game Version: A21 b324 OS/Version: Windows CPU Model: - System Memory: - GPU Model and VRAM: - Screen Resolution: - Video Settings: - Game mode: Dedicated server Did you wipe old saves? yes Did you start a new game? yes Did you validate your files? yes Are you using any mods? yes EAC on or off? on and off. i switched it off to test if it still appears because i found out that the log "Got message for unknown client number" getting thrown in the EAC implementation. the bug still appears with EAC on AND off. Status: NEW Bug Description: In addition to the description above: i did apply a password to my server and only gave it to the ones which send me a screenshot of their game having b324. during this phase the issue didnt appeared anymore. Detailed steps to reproduce the bug: I cant test it by myself because i dont have the game in an older build anymore. but im pretty sure the different build is what causes it, because the same 2 log lines from above appeared when b323 was released and players where joining with the older b317 because the server wasnt updated at that moment. after updating the server to b323, the logs didnt appear anymore. 1) connecting with b317 or b323 (im not sure which of them is causing it) to an b324 dedicated server 2) the server should start throwing the 2 log lines from above multiple times 3) players on the server getting disconnected Actual result: (description of what is occurring) when connecting to a server, only the version number is checked if it matches to the Server. The buildnumber isnt checked. since the version number wasnt increased during the experimental and first stable release, its possible to join to a server with an different build. Expected result: (what you expect to occur) the buildnumber needs to be checked when a player connects to a server to prevent issues like this in the future. Or at least increase the game version once to make this bug obsolete
×
×
  • Create New...