- Anonymous
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000899 | The Dark Mod | Coding | public | 26.06.2008 16:30 | 28.06.2008 18:10 |
| Reporter | SneaksieDave | Assigned To | |||
| Priority | normal | Severity | normal | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | SVN | ||||
| Fixed in Version | SVN | ||||
| Summary | 0000899: Buttons don't fire without Translate property | ||||
| Description | Note: this may very well apply to all such movers (doors which pass triggers, etc). Just spent a while pulling hair out trying to figure out why my test button wasn't firing its triggers. Tried rebuilding it, triple checked all the targets, made sure the targets worked independently; just couldn't see anything wrong. 'Till I looked at snow.map for an example, and noticed the one difference: a missing "translate" "0 1 0" pair. 1. why should a button need to move, to work? Maybe the script only activates within the move routines? It doesn't look like it fires on finishing moving, so I'm not sure what's the issue here. 2. while undesirable, if this property IS essential to it working though, it should be defaulted or forced on the user (I haven't yet figured out why a frobable func_static doesn't trigger its targets; maybe it doesn't have that script. Will revisit that next...) | ||||
| Tags | No tags attached. | ||||
 |
In the case that the user wants a button which doesn't move, they can use the atdm:frobable_base class, which fills the role perfectly. Create it, give it targets, and it's done. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 26.06.2008 16:30 | SneaksieDave | New Issue | |
| 26.06.2008 18:30 | SneaksieDave | Status | new => closed |
| 26.06.2008 18:30 | SneaksieDave | Note Added: 0001374 | |
| 26.06.2008 18:30 | SneaksieDave | Resolution | open => fixed |
| 28.06.2008 18:10 | greebo | Fixed in Version | => SVN |