Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
I also have to consider resources, the server has 32GB or RAM and Ark decimates that once you start running multiple instances.
All I can really say is I'll see where I'm at come April when work commiments start to ease off and see if there is any demand for these servers.
Thanks
Honestly, I don't know. I was planning on reopening an Ark server upon its release but that date seems to be streatching infinitly into the future. The problem for me is keeping up with all the updates while we go through busy seasons at work. If there was a way of passing this on to someone else I would but short of writing an entire web frontend to run these tasks I don't have a way of doing this.
Currently I have a Conan server up and running on the same IP. But this has been a walk in the park compared to Ark when you consider the difference in how both companies release updates. Ark is all over the place and unpredictable, this causes upset amoung players when they can't connect due to version conflicts.