Post: #3

Ok lets say i'll try to store many items in a cabinet.

[DIALOG d_cabinet]
50,71
//nodispose
//noclose
File.mode.readflag=1
page 0
resizepic 0 0 2620 300 503
checkertrans 5 5 290 493
resizepic 350 0 2620 300 503
checkertrans 355 5 290 493


dtext 10 25 180 Items :
if (<file.fileexist cabinet/cabinet.txt>)
<file.open cabinet/cabinet.txt>
local.ox=20
local.oy=65
for <file.filelines cabinet/cabinet.txt>
call f_cabinet_resolve <FILE.Readline <local._for>>
//Buttons
button <local.ox> <eval <local.oy> +5> 1209 1210 1 0 <eval <local._for> +1000>
//Text-Entries
dtext <eval <local.ox> +20> <local.oy> 180 <local.name>
local.oy +=20
if <local._for> > 20
local.ox +=100
endif

endfor
endif
FILE.CLOSE


[DIALOG d_cabinet BUTTON]
On=1001 1050
IF (<FILE.FILEEXIST cabinet/cabinet.txt>)
<file.open cabinet/cabinet.txt>
call f_cabinet_resolve <FILE.Readline <eval (<ARGN1>-1000)>> //reads lines 1-50
serv.newitem <local.id>
new.name=<local.name>
new.color=<local.color>
new.attr=<local.flags>
new.more1=<local.more1>
new.bounce <src>
ENDIF
FILE.CLOSE

[Function f_cabinet_resolve]
local.name=<argv[0]>
local.id=<argv[1]>
local.color=<argv[2]>
local.flags=<argv[3]>
local.more1=<argv[4]>

The File cabinet.txt contains informations like :

name1,id1,color1,flags1,more1,.....
name2,id2,color2,flags2,more2,.....
name3,id3,color3,flags3,more3,.....
.....
name50,id50,color50,flags50,more50,.....

So. i can display every line of the File in my Gump. And i can extract/create each item, if wanted.
But the Cabinet is just for storing Items. When you take one out, obviousely it shouldn't "stay" in the Cabinet, so the entry has to be deleted.

You may ask, why does he want to use File-Options, when it is much simpler to just use tags on the Cabinet.
Well.. it is a RP-Server without a Maximum of items per character. So many characters have thousands of Items (in this case sets of clothing). It is definitely not good to store up to hundreds of tags on a item.
The Script is for Item-Reduction without forcing the players to "lose" items.