SphereServer BugTracker - SphereServer | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0002330 | SphereServer | new feature request | public | 06-05-14 03:07 | 29-10-14 11:45 |
| Reporter | Coruja | ||||
| Assigned To | Coruja | ||||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | assigned | Resolution | open | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Nightly Version | Automated (specify build number) | ||||
| Experimental Flags | None | ||||
| Option Flags | None | ||||
| Internal Build Number | |||||
| Summary | 0002330: New CONTAINEROPENID on t_container | ||||
| Description | On OSI some containers have a different DISPID when opened, like armoires (default is closed, and when it open the gump, the DISPID will turn into an opened armoire) the idea is implement this on sphere using a new TDATA5 or CONTAINEROPENID on t_container. When the gump open, sphere will change the item DISPID to CONTAINEROPENID and start a 5sec timer loop, when the char who opened the container get offline or distance > 3, the container get back to default ID (closed) | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 06-05-14 03:07 | Coruja | New Issue | |||
| 29-10-14 11:45 | XuN | Assigned To | => Coruja | ||
| 29-10-14 11:45 | XuN | Status | new => assigned | ||
| There are no notes attached to this issue. |