[Not a Bug] 7D2D Errores en el servidor dedicado

Tueris

New member
Jan 8, 2021
7
0
0
39
Hola a todos.
Tengo montado un servidor dedicado en mi casa para jugar con los amigos a 7D2D, y me salen estos errores. No se a que son debidos.
 

Attachments

  • errores.jpg
    errores.jpg
    358.7 KB · Views: 23
Telnet disconnection errors are pretty normal, if its from RAT, RAT will reconnect. The connections in your screenshot, appear to be from multiple IPs. So it looks like someone was either doing a port scan, or otherwise attempting to telnet into your server. The red color just means the connection was closed (usually that they failed to sign in with the right password).

Ultimately, it isn't anything to worry about. But you can always change your telnet port (and reconfigure RAT to match it) if it bothers you.
 
Para cambiar los puerto, solo es necesario hacerlo en RAT o en el servidor también. ¿Como se cambian en el servidor si era necesario?
Gracias TREKKAN.
 
Just as long as you have a password on the telnet connection, you should be good.

Are you renting a server??
 
No es un servidor alquilado, es uno físico que tengo en mi casa, monte el servidor de 7D2D viendo videos. Veo que da unos errores, uno de ellos es que he puesto, pero da algunos mas, no se los motivos por los que salen.
Descargue el SteamCMD y después el RAT. El servidor utiliza windows server 2019.
 
Estos son los otros errores que salen.
 

Attachments

  • errores 7D2D.jpg
    errores 7D2D.jpg
    394.9 KB · Views: 10
I don't think that windows server is the best to use. Windows 10 is better if you want windows.

Linux is better in my opinion.

The errors in your last screenshot are from a modlet you have installed. A modlet that adds blocks?
 
Puse el mod de Undead Legacy, aunque al parecer no lo puse del todo bien o que hay algo que no esta bien en el mod.
 
Sorry, i don't do any modding and wouldn't know how to help. Try removing the mod though and see if that fixes the issue (make sure you shut down your server, remove the mod, restart the server).
 
Yeah, they have a block problem. I saw they did have an update a few days ago. But it is experimental.
 
Windows server works great for 7d2d dedicated. Windows 10 vs Windows server does not make a difference unless you want to use the video card in your computer which requires Windows 10 for drivers. However I have ran multiple tests and found that the dedicated server does not benefit from the video card even when changing the boot.config entry to tell it to use it. It takes up video memory but then never uses the video card for any rendering.

In A18 Linux used to run better but now after much testing I have found with the same hardware Windows runs better FPS and seems to execute commands quicker than Linux. It used to be the opposite.

On a side note if you get any weird block issues where there are blocks that show up in the world you cannot destroy and you can just walk through them. To fix this just run "rendermap" without the quotes and it rerenders all visited areas that the server has already rendered. I have to do this sometimes and I started to run this on a daily basis when I restart the server service. It takes about 10 minutes to run (depending on how much of the map has been visited) on my 10 year old server and runs even quicker on newer hardware.

For my 8k maps I run "visitmap -4096 -4096 4096 4096" once and then "rendermap" each time I restart the service which makes traveling for players much quicker. This is because the map is prerendered and just sends chunks as they visit them instead of having the render and then send. The visitmap command only needs to be ran once per save. You do this in a telnet session and it does it for the system. It does not reveal the map to the player unless the player has permission to run in the F1 console while logged into the server. The reason I run rendermap each time I restart is to prevent any weird block issues.
 
Last edited: