安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
2 
举报此帖
And it sounds like 7 spawn after going loud
I can only assume the "guard" gangsters are the stationary ones who block doorways, moving to let you up to the apartment?
Mission scripts are not lua but a kind of binary XML, which describes a flow graph. I've written a lossy converter from the original format to a somewhat legible text representation (with a Python-ish formatting). The editor used by the devs places the nodes directly on the map at reasonable places. Those editor coordinates are stored in the files as well but not shown in the text representation. Regardless of method, the system is a bit of a mess. It's a write-only language, so to speak (except that, well, you cannot modify the text output because it is lossy). I've written the converter so I know what each line of text means; I suppose that's another challenge for you.
The first thing you pasted is part of an ElementEnemyDummyTrigger node. It tells the game that it wants to be informed when any of those specified events occur. When such an event happens, the node is executed, and upon execution it executes the nodes given after "Execute:". So when any of those gangsters goes weapons_hot (which means uncool, basically), the deal is interrupted. The trigger node does not spawn any of these enemy groups, as group spawns are governed by nodes of other types. The trigger COULD cause spawns if it executed group spawn nodes (but it does not, it raises the alarm).
A few pointers:
The game executes ´hide_all_safes´ as soon as the script is done loading, while still in the loadout screen (as indicated by EXECUTE ON STARTUP). First it hides (removes) all safes, then it makes 2 of them show up again in different apartments. An apartment with a safe is also "enabled" for later on. That stuff can happen while still in the loadout screen should not be a surprise: http://psteamcommunity.yuanyoumao.com/app/218620/discussions/14/523897277918949896/
Player spawn is checked by ´player_spawned_trigger´ which is a relatively small box around the spawn location that asks the game to be informed as soon as a player enters it. The game then makes a check every "Interval: 0.1" seconds whether there is a player in that box. This is the standard way of checking player spawns. With some *bad* luck it is possible to escape (leave without informing the trigger) boxes on certain maps, e.g. Dockyard ended up with no keycards if you moved instantly (may or may not be fixed). I personally managed to get out of the box on Diamond Store.
0.5 s after player spawn, the game spawns some gangsters:
I've added the number of people per group or spawn at the end of each line, so there are 1+2+1+1+1+2+1+1+1+1+1 = 13 gangsters after the players spawn. Now, one question is why that first gangster is inlined, whereas the other nodes are not. Did my converter mess up? The thing is, the first gangster is never referenced by other nodes. As we've seen already, the game checks for weapons_hot of gangsters and groups. That's the kind of reference I mean. So this particular gangster is not affected by anything in the mission script. He can go uncool without consequences. Is that intended? I believe it to be a bug. Super easy to spot with my converted files, but then again I HAD to write an inlining algorithm to make the text files somewhat understandable while the devs have their fancy 3D editor. I'm sure they could write their own algorithms to detect this kind of behavior, it's just that they had no need.
2 s after player spawn, execute ´spawn_apartment´. This tries to spawn gangsters associated with all apartments. However, apartments are disabled by default. Only the 2 apartments enabled by the safes do spawn those gangsters.
2.5 s after player spawn, execute ´choose_decoy_apartment´. This selects one of the remaining two apartments and adds gangsters there. If the gangsters later on decide to ambush, this is where they will lead you to.
The aggressive inlining by the converter makes it a bit hard to recognize that the decoy and the ordinary apartments spawn the same amount of gangsters, so it takes a bit of copypasting to get all the relevant parts neatly grouped together.
I've added gangster numbers for the apartment part. Anyway, they do look pretty similar, right? Except that there is another bug. ´spawn_apartment003´ does not evaluate the 75% chance for corridor gangsters, whereas ´decoy003´ does. That corridor is special however as it appears to be the shared corridor in the right building. Take a closer look at the hallway
When the node is executed, TRIGGER TIMES is reduced by 1. If it reaches 0, the node is disabled (execution of a disabled node does nothing at all). So if either apartment decides to spawn gangsters in this hallway, those spawns will not occur again if the other apartment also decides to spawn those gangsters. Trigger times is also the reason the other hallways are inlined, but the shared one is not. Inlining the hallway would remove the crucial knowledge that the node can be executed only once.
So that's 3 gangsters per apartment except apartment #3 which has 4. Each unbugged apartment has a 75% chance to spawn 3 gangsters in the hallway, except apartment #4 which spawns 5.
Lower bound for gangsters is 13 + 3+3+3 = 22 (no gangsters in the hallways). Upper bound for gangsters is 13 + 3+3+4 + 3+3+5 = 34.
This is assuming that I haven't missed any nodes that spawn more gangsters.