Question Server works great, with WARN error?

[Scrufdog]

Everything is great, but I see this WARN on every server start. Not sure if I should care or not?

Linux Mint 21, running Multicraft

Here's a clip of the log. I spaced out the error to make it easier to find.

10.01 20:27:53 [Multicraft] Loading server properties
10.01 20:27:53 [Multicraft] Starting server!
10.01 20:27:53 [Multicraft] Loaded config for "[PaperMC-Scruf] 1.19.3"
10.01 20:27:54 [Server] INFO Applying patches
10.01 20:27:56 [Server] INFO Starting org.bukkit.craftbukkit.Main
10.01 20:27:56 [Server] INFO System Info: Java 17 (Java HotSpot(TM) 64-Bit Server VM 17.0.5+9-LTS-191) Host: Linux 5.15.0-57-generic (amd64)
10.01 20:27:56 [Server] INFO Loading libraries, please wait...


10.01 20:27:56 [Server] INFO 2023-01-10 20:27:56,939 ServerMain WARN Advanced terminal features are not available in this environment


10.01 20:27:59 [Server] INFO Building unoptimized datafixer
10.01 20:28:00 [Server] INFO Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD'
10.01 20:28:02 [Server] INFO Loaded 7 recipes
10.01 20:28:02 [Server] INFO Starting minecraft server version 1.19.3
10.01 20:28:02 [Server] INFO Loading properties
10.01 20:28:02 [Server] INFO This server is running Paper version git-Paper-375 (MC: 1.19.3) (Implementing API version 1.19.3-R0.1-SNAPSHOT) (Git: 7a64b85)
10.01 20:28:02 [Server] INFO Server Ping Player Sample Count: 12
10.01 20:28:02 [Server] INFO Using 4 threads for Netty based IO
10.01 20:28:02 [Server] INFO [ChunkTaskScheduler] Chunk system is using 1 I/O threads, 2 worker threads, and gen parallelism of 2 threads
10.01 20:28:03 [Server] INFO Default game type: SURVIVAL
10.01 20:28:03 [Server] INFO Generating keypair

 

[ClientDNS]

You mean the "Advances terminal features are not available in this environment" message?
To say it easy, Paper starts a console, which is not really supported on Windows or NT systems.
I don't have a clue why it's also throwing this warning on Unix-based systems. You can ignore it except you find a bug, but no one ever reported. I guess it should work fine.