Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
Palworld does not currently allow for LAN server connection, as server connection has to happen through the in-game server browser (which, by the way, requires both internet and Steam connection at all times in order to work), so local IPs don't work. It's annoying, and I've already written some feedback about it, I suggest you do the same, maybe they'll listen and implement LAN connection someday.
Hope that helps, have a good one!
Also have a look at ripps818/docker-palworld-dedicated-server-wine for the host. I am using it myself and have 0 issues with it, besides the fact that it is slightly outdated, but if you aren't attempting to mod the amount of basses, it works fine, and even then I got a work around with passing a modified /PalWorldSettings.ini.template and /includes/config.sh to the container.
There is also Playit.gg for those who want to port forward without actually doing that. It also functions as a reverse proxy like cloudflair, so it hides you actual IP, so you can give a URL and port to friends(make sure to set a password for the server) and for that I suggest this image pepaondrugs/playitgg-docker
Just make sure both containers are on the docker "bridge" network adapter and you should be off committing various inhumane acts on your server with your GF.
Note: If you use the playit.gg option then I suggest you use the internal docker IP for the server instead of the IP of the machine you are running it on in my case it is 172.17.0.2 but for you it may be different. Use "docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' container_name_or_id" to get it.
If you want to run it on a dedicated system then I suggest you get one of these from amazon dp/B0D6FYTGCJ (just go to amazon.com and paste that after the .com/) I am using the 32G/500G/5700U myself.(I am dual booting it so I still have the original windows image if needed) Its cheep and sometimes has a sale bringing the cost down to $359(on sale at the time of this post) and if needed instead of Ethernet you can run it via WiFi(I am and do not recommend)
I do HIGHLY recommend CasaOS on Ubuntu(or debian). Its about as user friendly as it gets with server panels that manage docker instances. I also have cockpit installed in case I want to use the terminal. As the one in CasaOS is a bit finicky.