View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002066SphereServernew feature requestpublic26-03-12 20:3902-11-14 00:33
Reporterbabidi 
Assigned ToBen 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionnot fixable 
PlatformOSOS Version
Product Version20-09-2009, 0.56b Prerelease 
Target VersionFixed in Version0.56c Nightly 
Summary0002066: unequip return 1
Descriptioni 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
TagsNo tags attached.
Nightly VersionAutomated (specify build number)
Experimental FlagsNone
Option FlagsNone
Internal Build Number1506
Attached Files

- Relationships

-  Notes
(0002540)
Ben (manager)
02-11-14 00:33

This can't be implemented as it is triggered once the item is already removed from the layer.
Also preventing unequip in this trigger would cause issues with item removal.

Best to just keep using your script fix

- 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


Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker