Some issues regarding feedback from players on my server about tenseimc

[Euphillya]

Try the latest version (after #30) as I've updated Folia, which has also updated its code on Paper.

[Virgil692]

Did it fix the problem?

This issue has been basically solved, and players connecting to the server have reported that the server is not stuck

[Euphillya]

This problem seems to me independent of the project, it's just that the server didn't manage to connect to the Mojang server, maybe they had a breakdown. If possible, the best thing to do would be to also provide me with a report using Spark, which I've recompiled for 1.20.1, to better pinpoint any problems.

[Euphillya]

he is in folder config

[Euphillya]

A Spark report might help. Also I could only watch at weekends as I work.

[Euphillya]

On which version? 1.19 or 1.20? Also, is it reproducible on Folia?

[Virgil692]

Problems encountered on TenseiMC 1.20 # 29 build

[Virgil692]

You can take a look at this video, which was recorded by the player
QQ视频20230611204518.zip

[Euphillya]

For the time being, I'd advise against building a production server with version 1.20. As Paper is not yet considered stable, Folia is even less so. TenseiMC is therefore at the same stability stage as Folia. Nevertheless, I'll try to have a look and if I find the problem, I'll inform Folia so they can fix it.

[Virgil692]

Try the latest version (after #30) as I've updated Folia, which has also updated its code on Paper.

Okay, I'll give it a try
My player has provided two more videos for review
Downloads.zip

[Virgil692]

Now the players still feel that the server is a bit stuck, I don't know if I used internal network penetration technology
I really can't find the core download for Folia😅

[Virgil692]

I have collected the issues with TenseiMC so far:

1. The delay in pinging the server has exceeded 200ms, but in reality, the delay in connecting to the server has exceeded 1-2 minutes. Using the accelerator does not work
2. Secondly, the multithreading optimization mentioned by Folia may have a significant burden on average or even poor CPUs due to the high core computing load
3. Thirdly, due to the significant changes made to the core of the original version by Folia, many original features were lost, and even a large number of errors were encountered, such as the Nk end of the bedrock version, which required the operation of the original version. We hope this can be optimized in the future
   Finally, I am still optimistic about the future development of Folia and even TenseiMC cores, but it also requires more time and testing to fix these issues

[Euphillya]

I'll do my best in the hopefully near future. TenseiMC is still quite young, so it's very unstable. Then I know that Folia really requires a CPU with a lot of cores, so it won't perform very well on an average CPU.

[Euphillya]

What's more, Spark is currently unavailable for Folia 1.20, which is really annoying because I can't retrieve any data since Paper Timings is no longer functional on Folia.

[Virgil692]

Okay, support!

[Virgil692]

I have a guess: Folia, I guess to ensure that the server doesn't get stuck, I keep sending data packets. When players connect to the server, they receive a large amount of data packets and cannot process them, so the client starts to get stuck

[Euphillya]

You use Velocity, Waterfall or only TenseiMc ?

[Virgil692]

You use Velocity, Waterfall or only TenseiMc ?

I only use TenseiMC

[Euphillya]

I have compiled a version of Spark for Folia 1.20.1 (TenseiMC compatible), can you give me more logs with this? Euphillya/spark#1

[Virgil692]

I thought about it for a moment, maybe it was a problem with geyser at the time, because these errors were from players in the bedrock version who connected to the TenseiMC server through geyser

[Virgil692]

I have compiled a version of Spark for Folia 1.20.1 (TenseiMC compatible), can you give me more logs with this? DoctaEnkoda/spark#1

That's okay

[Euphillya]

I thought about it for a moment, maybe it was a problem with geyser at the time, because these errors were from players in the bedrock version who connected to the TenseiMC server through geyser

If it's from Geyser, try checking them out with the replays. There's nothing to lose by trying.

[Virgil692]

I thought about it for a moment, maybe it was a problem with geyser at the time, because these errors were from players in the bedrock version who connected to the TenseiMC server through geyser

If it's from Geyser, try checking them out with the replays. There's nothing to lose by trying.

I am currently deploying the latest geyser (# 195), originally using version # 182

[Euphillya]

Did it fix the problem?

[Virgil692]

Recently, I have been busy with exams at school, so I'm sorry to tell you now

[Virgil692]

Sometimes this error message may appear when starting the latest TenseiMC server, but it does not affect the entire core process

[Virgil692]

This problem seems to me independent of the project, it's just that the server didn't manage to connect to the Mojang server, maybe they had a breakdown. If possible, the best thing to do would be to also provide me with a report using Spark, which I've recompiled for 1.20.1, to better pinpoint any problems.

spark profiler open [17:24:38 WARN]: [spark] A command execution has not completed after 5 seconds, it might be stuck. Trace: java.base/jdk.internal.misc.Unsafe.park(Native Method) java.base/java.util.concurrent.locks.LockSupport.park(LockSupport.java:221) java.base/java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1864) java.base/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3780) java.base/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3725) java.base/java.util.concurrent.CompletableFuture.waitingGet(CompletableFuture.java:1898) java.base/java.util.concurrent.CompletableFuture.join(CompletableFuture.java:2117) spark-bukkit-1.10-SNAPSHOT.jar//me.lucko.spark.lib.bytesocks.BytesocksClientImpl.connect(BytesocksClientImpl.java:84) spark-bukkit-1.10-SNAPSHOT.jar//me.lucko.spark.lib.bytesocks.BytesocksClientImpl.createAndConnect(BytesocksClientImpl.java:75) spark-bukkit-1.10-SNAPSHOT.jar//me.lucko.spark.common.ws.ViewerSocketConnection.<init>(ViewerSocketConnection.java:61) spark-bukkit-1.10-SNAPSHOT.jar//me.lucko.spark.common.ws.ViewerSocket.<init>(ViewerSocket.java:71) spark-bukkit-1.10-SNAPSHOT.jar//me.lucko.spark.common.command.modules.SamplerModule.handleOpen(SamplerModule.java:467) spark-bukkit-1.10-SNAPSHOT.jar//me.lucko.spark.common.command.modules.SamplerModule.profilerOpen(SamplerModule.java:355) spark-bukkit-1.10-SNAPSHOT.jar//me.lucko.spark.common.command.modules.SamplerModule.profiler(SamplerModule.java:126) spark-bukkit-1.10-SNAPSHOT.jar//me.lucko.spark.common.SparkPlatform.executeCommand0(SparkPlatform.java:430) spark-bukkit-1.10-SNAPSHOT.jar//me.lucko.spark.common.SparkPlatform.lambda$executeCommand$2(SparkPlatform.java:339) spark-bukkit-1.10-SNAPSHOT.jar//me.lucko.spark.bukkit.folia.FoliaScheduler.lambda$executeAsync$0(FoliaScheduler.java:42) io.papermc.paper.threadedregions.scheduler.FoliaAsyncScheduler$AsyncScheduledTask.run(FoliaAsyncScheduler.java:216) java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) java.base/java.lang.Thread.run(Thread.java:1623) [17:24:40 INFO]: [?] An error occurred whilst opening the live profiler. [17:24:40 WARN]: java.util.concurrent.CompletionException: java.net.http.HttpConnectTimeoutException: HTTP connect timed out [17:24:40 WARN]: at java.base/java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:368) [17:24:40 WARN]: at java.base/java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:377) [17:24:40 WARN]: at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1152) [17:24:40 WARN]: at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) [17:24:40 WARN]: at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2194) [17:24:40 WARN]: at java.net.http/jdk.internal.net.http.Http1Exchange.lambda$cancelImpl$9(Http1Exchange.java:591) [17:24:40 WARN]: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) [17:24:40 WARN]: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) [17:24:40 WARN]: at java.base/java.lang.Thread.run(Thread.java:1623) [17:24:40 WARN]: Caused by: java.net.http.HttpConnectTimeoutException: HTTP connect timed out [17:24:40 WARN]: at java.net.http/jdk.internal.net.http.ResponseTimerEvent.handle(ResponseTimerEvent.java:68) [17:24:40 WARN]: at java.net.http/jdk.internal.net.http.HttpClientImpl.purgeTimeoutsAndReturnNextDeadline(HttpClientImpl.java:1689) [17:24:40 WARN]: at java.net.http/jdk.internal.net.http.HttpClientImpl$SelectorManager.run(HttpClientImpl.java:1299) [17:24:40 WARN]: Caused by: java.net.ConnectException: HTTP connect timed out [17:24:40 WARN]: at java.net.http/jdk.internal.net.http.ResponseTimerEvent.handle(ResponseTimerEvent.java:69) [17:24:40 WARN]: ... 2 more

When I input the spark profiler open command using the console, the spark plugin reports an error

[Euphillya]

I think it's your firewall in this case that cuts off the connection to Spark and also to Mojang because at home I can upload the result.

[Virgil692]

Another question, can TenseiMC core enable features such as TNT, sand brushing, and carpet brushing? The tutorials I have seen here all need to be opened in paper.yml, but I did not find papermc.yml in the server's main directory

[Virgil692]

I think it's your firewall in this case that cuts off the connection to Spark and also to Mojang because at home I can upload the result.

Okay, I know where the problem lies

[Virgil692]

I feedback a problem: when a block of the server is blocked, other blocks are affected by server multithreading, and all blocks of the server will be affected by the delay

[Virgil692]

Tenseimc currently runs well on my machine, and it still works normally when 10 people are connected, but now spark plug-in still has that problem when it is started with instructions. At present, my machine is an Intranet environment, I don't know if this is the reason

[Virgil692]

I have compiled a version of Spark for Folia 1.20.1 (TenseiMC compatible), can you give me more logs with this? DoctaEnkoda/spark#1

https://spark.lucko.me/9tFIRXbI1t
This is my most recent spark analysis, with the core running on a #64 build

[Euphillya]

Sorry, the link dont work :/

[Virgil692]

Sorry, the link dont work :/

https://spark.lucko.me/dh1d1uyz2T

[Euphillya]

The link still doesn't work. "Unable to load the data. Perhaps it expired? Are you using a recent version?". I think we need to open an issue on the spark github.

[Euphillya]

Due to the inactivity of the issue, I close it.