(POL2006-01-18 Windows) createscript bug

Core Essence · **Posted:** Sun May 07, 2006 2:14 pm

If I set a createscript on an item and I want to utilize the method .container of the item, it returns error even if the item is in a container (utilizing CreateItemInBackpack())

Code:

use uo;

program create_darkpalabook(item)
  var newspellbook;
  if(!item.container)
    newspellbook:=CreateItemAtLocation(item.x, item.y, item.z, 0x2252, 1, item.realm);
  else
    newspellbook:=CreateItemInContainer(item.container, 0x2252, 1);
  endif
  SetName(newspellbook, item.desc);
  newspellbook.color:=item.color;
  SetObjProperty(newspellbook, "Obs", 1);
  return 0;
endprogram

It always do the CreateItemAtlocation and if the fake item is in a container item.x/y/z are == 0

Marilla · **Posted:** Sun May 07, 2006 6:25 pm

I was under the impression that you shouldn't try to refer to an item's location in it's create script, as it might not actually BE there, yet. Did something here change from 095 to 096?

Austin · **Posted:** Sun May 07, 2006 6:36 pm

Correct - It isnt guarantee to exist yet. Also, try returning 1 at the end of your script.

Core Essence · **Posted:** Mon May 08, 2006 1:15 pm

With return 1; it's the same thing. However, i think it's better that createscript is activated after complete object creation (before loading control script) and then destroyed with return 0;

PenUltima Online

(POL2006-01-18 Windows) createscript bug

Who is online