-
Notifications
You must be signed in to change notification settings - Fork 1
/
TokenConfig.ecf
65 lines (59 loc) · 3.4 KB
/
TokenConfig.ecf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
# Tokens are instances of the item 'GenericToken' that will get their purpose in game.
# F.e. you can define a lock code for a door to be opened by a token that has the id of this lock code. Or you can
# define a quest or a PDA mission that needs a token to get finished.
# You don't need to define every token here, but if defined, the name and description will show up correctly.
# Set RemoveOnUse: true to remove it from the inventory of the player as soon as it was used.
# === Possible Usage ====
# 1. Place a Token with a certain key (= Meta ) to a inventory (f.ex. Container in an Alien POI): Open Console > 'give item Token 0001' > This will add a token to your inventory > place it in a container > Save POI (Only works with admin core POI at the moment)
# 2. Give a Token with a certain Meta to a player via PDA via Reward or InventoryOps: Use 'Token:0001' to give the Red Keycard for example
# 3. Give a Token in a dialogue: Use a function, f.ex AddItem('KeyCardBlack', 3, 1234) = Will give the player 3x Keycard Black with the Meta 1234
# 4. Let a Trader sell/buy tokens: Enter an item to Trader config. Example: 'Item3: "Token:0001, 1, 1-2, 1-1, 1-2" = will buy and sell the Red Keycard from below
# 5. Use a Token in a loot table. Same as with a Trader. Use 'Token:0001' in your loot table/config
# ========== IMPORTANT ===========
# - Currently only the item 'Token' (Itemsconfig.ecf id: 1305) can have a 4-digit META element. Any OTHER "keycard" named item or other items in general can NOT have meta info attached!
# - When working with the TokenConfig.ecf, adding custom names for the Token:Meta combination, you can use the console command 'token reload' when you are ingame. You do not need to restart the game when working with this file!
# =================================
# Example Token
{ Token Id: 1, Name: KeyCardRed
Description: The red key card will open red doors
}
{ Token Id: 2, Name: KeyCardGreen
Description: The green key card will open green doors
}
{ Token Id: 1234, Name: Golden Key
Description: With the golden key you can open all golden doors
#RemoveOnUse: true
}
# === Story Tokens (Do not change! ===
{ Token Id: 9999, Name: AI Routine 32 Key
Description: Activates a station or the telporter in that station. We need to find out.
#RemoveOnUse: true
}
{ Token Id: 9998, Name: Chief Palant
Description: The Log of Chief Engineer Palant found in the wreckage of the UCH Heidelberg
#RemoveOnUse: true
}
{ Token Id: 9997, Name: Ensign Emmerson
Description: The Log of Ensign Emmerson found in the wreckage of the UCH Heidelberg
#RemoveOnUse: true
}
{ Token Id: 9996, Name: M
Description: The log of a crewman with the mysterious short-handle M found in the wreckage of the UCH Heidelberg
#RemoveOnUse: true
}
{ Token Id: 9995, Name: Titan Code Recovery Main Key
Description: Required to reveal a code fragment each with one of the 3 prepared consoles in the TITAN
#RemoveOnUse: true
}
{ Token Id: 9994, Name: Titan Code Fragment
Description: Code fragment required to generate the override code for the TITAN failsave datacache
#RemoveOnUse: true
}
{ Token Id: 9993, Name: Zirax Commander Keycard
Description: A full-access keycard for any base on the moon dropped accidentally while stumbling in your weapon fire
#RemoveOnUse: true
}
{ Token Id: 9992, Name: Root Beer Formula
Description: The secret formula of the delicious Totally Overpowered Brewery low-gravity root beer
#RemoveOnUse: true
}