安装 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(越南语)
Українська(乌克兰语)
报告翻译问题









Well, this depends on the users what they are willing to do. I have no problem with blocking at all, but can't talk for others.
And beside of that, as already mentioned, there is a lot more as the API (EOS) itself. To "silence" Epic more or less, there are few dozend adresses and countless ipv4 adresses involved.
https://hosts.gameindustry.eu/#Spieleclients Scroll a bit till Epic Games Launcher
https://gameindustry.eu/firmenkatalog/epic-games-inc/ for involved ipv4 adresses and more info (german, you have to use a translator)
For everyone else? Thats the connectionlog from client devices to Epic, made by Tomb Raider itself, while the game is initializing. Also shows the Datarouter telemetry service which is now mandatory. To show the whole structure of this "service" in one picture would be too much here. Already have some detailed reviews about it and a lot additional Infos outsourced with ipv4, host, background and company data as well as different versions of Epic's telemetry.