SphereServer BugTracker - SphereServer | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0002066 | SphereServer | new feature request | public | 26-03-12 20:39 | 02-11-14 00:33 |
| Reporter | babidi | ||||
| Assigned To | Ben | ||||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | not fixable | ||
| Platform | OS | OS Version | |||
| Product Version | 20-09-2009, 0.56b Prerelease | ||||
| Target Version | Fixed in Version | 0.56c Nightly | |||
| Nightly Version | Automated (specify build number) | ||||
| Experimental Flags | None | ||||
| Option Flags | None | ||||
| Internal Build Number | 1506 | ||||
| Summary | 0002066: unequip return 1 | ||||
| Description | i always wondered if the CHAR @ItemUnEquip ITEM @UnEquip does not have the return 1 to avoid unequiping as other triggers it is simply implementable by ---- PACKET7=fix_unequip_paralyze [function fix_unequip_paralyze] REF1=<HVAL <LOCAL.1>000000+<LOCAL.2>0000+<LOCAL.3>00+<LOCAL.4>> REF2=<local.char> if (<ref1.p.z> == <ref1.z>) && (<ref1.cont>==<REF2.UID>) && (<ref2.FINDID.i_rune_paralyze_new>) ref2.SENDPACKET 027 00 //deny pick-up ref2.update return 1 endif | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 26-03-12 20:39 | babidi | New Issue | |||
| 02-11-14 00:33 | Ben | Note Added: 0002540 | |||
| 02-11-14 00:33 | Ben | Status | new => closed | ||
| 02-11-14 00:33 | Ben | Assigned To | => Ben | ||
| 02-11-14 00:33 | Ben | Resolution | open => not fixable | ||
| 02-11-14 00:33 | Ben | Fixed in Version | => 0.56c Nightly | ||
| Notes | |||||
|
|
|||||
|
|
||||