>...and deletes the selected triggers/aliases/timers/ plugins from the main MUSHclient file...
Umm.. Doesn't this sort of assume that the subs involved are in the final form you want released? For my Druid Potions plugin I am currently doing I have no immediate plans to replace the hard coded version I use with the final plugin (which builds the lists it uses as one plays). You may want to make this an optional effect.
Also.. What happens if the plugins script calls some secondary sub or function . One thing I have considered doing was making a function like>
I see two problems here. The first problem that such a function (which imho should be a standard library function for arrays in languages) may be used by more than just that plugin. The second problem is, does the wizard look for such occurances in the subs and automatically include them?
Umm.. Doesn't this sort of assume that the subs involved are in the final form you want released? For my Druid Potions plugin I am currently doing I have no immediate plans to replace the hard coded version I use with the final plugin (which builds the lists it uses as one plays). You may want to make this an optional effect.
Also.. What happens if the plugins script calls some secondary sub or function . One thing I have considered doing was making a function like>
function Array_Remove(original, position)
dim temp
temp = split(original,",")
dim temp2(ubound(temp - 1))
for count = 0 to ubound(temp) - 1
if count < position then
temp2(count) = temp(count)
else
temp2(count) = temp(count + 1)
end if
next
Array_Remove = join(temp2,",")
end functionI see two problems here. The first problem that such a function (which imho should be a standard library function for arrays in languages) may be used by more than just that plugin. The second problem is, does the wizard look for such occurances in the subs and automatically include them?