View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000167 | RPG Architect | Bug | public | 2024-03-20 22:53 | 2024-09-12 15:50 |
Reporter | Mondune | Assigned To | Locke | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Product Version | Early Access | ||||
Target Version | 1.0 | ||||
Summary | 0000167: Further Escape Codes | ||||
Description | <partymember[index]> Displays name of character in specified party slot. <$> Displays a specified currency name.@amalgamash I’m updating this. Not supporting multiple currencies natively – that’d definitely be something you could do with variables. <item[index]> Displays a specified item name. <gear[index1,index2]> Displays a specified gear. Uses a two-dimensional array to allow reference to defined categories (“weapon,” “chest,” “head,” “ring1,” etc).@amalgamash - I assume this would be based on the character? index1 would be the character, index2 would be the slot? <entity[index]> Displays a specified entity name.@amalgamash - this “kind of” might work. Entities on their own are just constructs inside the map. So, this is inherently a little weird. You can theoretically spawn more entities as well. I’m not sure if this one will be worth working in just yet. <map[index]> Displays a specified map name.@amalgamash - is this actually useful? It’d be a bit taxing on the system, because I’d have to theoretically load all maps and save their names… and it’d get weird if we ever add “instanced” maps that may have a variable name. Let me know. [1/23]Tolin - migrated this issue for completeness' sake | ||||
Tags | Editor | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2024-03-20 22:53 | Mondune | New Issue | |
2024-03-20 22:53 | Mondune | Status | new => assigned |
2024-03-20 22:53 | Mondune | Assigned To | => Locke |
2024-03-20 22:53 | Mondune | Tag Attached: Editor | |
2024-03-20 22:53 | Mondune | Status | assigned => acknowledged |
2024-03-21 02:33 | Locke | Status | acknowledged => confirmed |
2024-03-21 02:34 | Locke | Status | confirmed => acknowledged |
2024-03-21 02:43 | Locke | Target Version | => 1.0 |
2024-04-15 20:02 | Locke | Status | acknowledged => resolved |
2024-04-15 20:02 | Locke | Resolution | open => fixed |
2024-09-12 15:50 | Locke | Status | resolved => closed |