SphereServer BugTracker - SphereServer | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0002200 | SphereServer | executable - windows build | public | 02-09-13 06:32 | 03-09-13 00:08 |
| Reporter | Coruja | ||||
| Assigned To | Ben | ||||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | 0.56c Nightly | |||
| Nightly Version | Automated (specify build number) | ||||
| Experimental Flags | None | ||||
| Option Flags | None | ||||
| Internal Build Number | |||||
| Summary | 0002200: Latest nightly build doesnt fire custom triggers anymore [MAJOR BUG] | ||||
| Description | As the title says, on latest 02 sept 2013 build the function <TRIGGER @SomeTriggerHere> doesnt work anymore with custom triggers. It works only with default sphere triggers This brokes many scripts and in some cases will drop out the entire script since important triggers doesnt fire anymore :( | ||||
| Steps To Reproduce | |||||
| Additional Information | Probably its something related to this: 25-08-2013, Ben -Added: Auto detection of in use triggers (Vjaka's code from 0.57 source) -Removed: ExperienceMode 0x20 and 0x40 since Auto trigger detection is enabled. -Removed: EF_New_Triggers, EF_Minimize_Triggers, and EF_NPCAct_Triggers since Auto trigger detection is enabled. | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 02-09-13 06:32 | Coruja | New Issue | |||
| 03-09-13 00:08 | Ben | Note Added: 0001646 | |||
| 03-09-13 00:08 | Ben | Status | new => resolved | ||
| 03-09-13 00:08 | Ben | Fixed in Version | => 0.56c Nightly | ||
| 03-09-13 00:08 | Ben | Resolution | open => fixed | ||
| 03-09-13 00:08 | Ben | Assigned To | => Ben | ||
| Notes | |||||
|
|
|||||
|
|
||||