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






So i created my own tick system that runs client side when the player is actually playing the game.
Basically There is 1 file to check for the current time, that only starts and stops when the game is on a mission/campaign. vs storing all the start/stop times, reading those values and subtracting and adding based on the current delta time to correctly add the game-play time. There is potentially a lot of edge cases to deal with.
For multiplayer I can make the assumption that the delta time would also run even in the lobby, so would need to replicate the system,
Just need time to sit down plan it out and test it, and time is a luxury atm for me.
How involved do you think it'd be? Generally i've seen mp handled by using a conditional in the init that'll only trigger if the executer is either a server or a directly singleplayer client.