SphereServer BugTracker - SphereServer
View Issue Details
0002023SphereServerexecutable - windows buildpublic30-08-11 20:0501-09-11 00:28
daskaras 
ShiryuX 
normalminoralways
resolvedfixed 
windows7
20-09-2009, 0.56b Prerelease 
0.56c Nightly 
Automated (specify build number)
None
None
0002023: using "new" items with LOCAL.CREATEOBJECT1 in Spell for Field Spells doesn´t work
I created two new items with a script

[ITEMDEF i_fx_field_fire_black_1]
ID=i_fx_field_fire
NAME=Schattenbrand
CATEGORY=Animations
SUBSECTION=Fire Field Shadow 1
DESCRIPTION=@

ON=@CREATE
COLOR=0455

[ITEMDEF i_fx_field_fire_black_2]
ID=i_fx_field_fire_ns
NAME=Schattenbrand
CATEGORY=Animations
SUBSECTION=Fire Field Shadow 2
DESCRIPTION=@

ON=@CREATE
COLOR=0455

and want to use them in my spell script like

ON=@SUCCESS
LOCAL.CREATEOBJECT1 = <eval i_fx_field_fire_black_1>
LOCAL.CREATEOBJECT2 = <eval i_fx_field_fire_black_2>

I only cast gold coins there. When I use the normal fire field, it works.
sphere gives me this error message

ERROR:CreateBase invalid item 0462a

newest nightly build
No tags attached.
Issue History
30-08-11 20:05daskarasNew Issue
30-08-11 21:09ShiryuXNote Added: 0001224
31-08-11 21:20daskarasNote Added: 0001226
31-08-11 23:07darksun84Note Added: 0001227
01-09-11 00:28ShiryuXNote Added: 0001228
01-09-11 00:28ShiryuXStatusnew => resolved
01-09-11 00:28ShiryuXFixed in Version => 0.56c Nightly
01-09-11 00:28ShiryuXResolutionopen => fixed
01-09-11 00:28ShiryuXAssigned To => ShiryuX

Notes
(0001224)
ShiryuX   
30-08-11 21:09   
Looks weird, since the ID of those are 0398c/03996 not 0462a. Try changing the 'ID=' values to the ones I used, and also try removing the EVAL. I'll try to reproduce it tonight.
(0001226)
daskaras   
31-08-11 21:20   
tried it with the id and without using the eval.
same error
(0001227)
darksun84   
31-08-11 23:07   
Doesn't work for me too , instead it works with "new" summoned npcs !
(0001228)
ShiryuX   
01-09-11 00:28   
You were right, custom items didn't work, so I tweaked the code a little.
It should be fixed in the next automatic build.