Wow im surprised i found this... But im glad TM has made his own page to support a great cimmunty.. Im back on board to help out with testing and have great conversation people i see that are here already.. great familiar faces.

Howdy Knight, I'm glad you found my little place!  I'll be at WinUO.org as well, freddy and I are strategically allied it would seem, so no worries.  I may even post a couple scripts over there like the Heartwood quester 1.xx.  But I'm glad the good people are still around. We're just here because we love the game of UO and the extra "cool feeling" you get from being able to play it while you goto the beach. 

Yes, I kinda needed my own site after all that's gone on.  I'm tired of re-inventing the wheel.  lol.  Plus there's my little extra thing here at ScriptUO that's been taking up most of my spare time.

Ok, I fixed this little bug.  It's easy to handle when you are looking for it.  I will probably be posting a revision to his program this weekend sometime. I want to address a couple other crash issues I've found, but I'm thinking it's nearly ready for public consumption.

So, perhaps, just as simple as that, it might be able to be done?

Yeh, I'm pretty sure I'm not going to break any existing precedence rules or any other rule for that matter.  I'll check into it.  Good idea.

no kidding.  I've never really quit; I've always had a main account that I've paid for since the beginning.  But I've let it go unplayed for months at a time.  Then there have been times, especially in my IDOC days when I'd have 5 paid accounts to hold all the houses back in the day when you couldn't place a house anywhere on a shard.  Those were crazy days; I miss that.

well, how about a colon ?   :  I don't think it's used for anything

Code: [Select]

int %count1 : %count2
float %realmath : %candivide

Yeh, I was going to look at what doesn't impact EasyUO too much, and can be included in the syntax that won't mess up EasyUO itself.  But I'm scheming..

Well not really.  If you look an many other languages (i.e. all) there's not really a way to initialize them unless you do it by hand.  There are compiler directives that allow you to assign a null value to the respective data type (kinda like what Hardyz suggests) but mostly all of them require you to do SOMETHING with the value.

For EasyUO, you can just have faith that math on a N/A value will default to zero, i.e. set %test %test + 1 = 1.  Otherwise, it gets kinda convoluted because of EasyUO's basic typeless structure.  I'm actually having to institute a way to differentiate that since I'm wanting to include decimal math, but you also have to be able to tell the difference between 0.0 (string) and 0.0 (float).

Right now I have a hirarchy of promotion/demotion from string->int->float, but I still need to allow for a way to let the user specify this.

I didn't know about winuo.org until I just saw your post in another thread. I think I will take it there heh, but the offer is still open here. I love scripting, just more on the scripting for bugs side.

Oh, you'd love my orange cloth generator then.

Am I the only one that wants/uses/does this?

Like, initializing variables to 0. I don't want to check for a variable by n/a. What if I ran the script, stopped it, and I'm running it again and it is holding a value? so, now I have 5 variables, I am setting to 0... I want to set them with 1 line of code, can SUO do that?

I've often wanted to do something exactly like that.  It really makes sense to initialize a variable to a number rather than some obscure reference that's not even a NaN or something more accepted like that.  Really, it would be pretty easy to add a system variable like #INITVAR which you can set that'll allow you set a variable initialization value. If you want to change to another block of initialization, you can just change the initializer.  I'll add that to the list of new features.