Gscript1 and Gscript2 needs new commands :P
 

Why dosnt Gscript1 or 2 have a comment like setstate zeon-state1.png; or something and it dosnt has setsprites zeon-sprites1.png; should u make that stefan spark or annyone? lol

1. Spark just administrates, he doesn't play any role in the programming of the client.
2. This is in entirely the wrong forum.

Anyway, it's redundant. If your server doesn't have scripters capable of reimplementing the GUI then it already has much bigger problems.
Like the fact that it's managed by you

Hm, I've always wanted that type of command aswell.

Though, you can easily just re-script the GUI/state.

Just ask Malinko. He was doing it last night. >_<
Either way, these commands would promote laziness, reduce the likeliness that somebody will learn from creating a GUI using your method, and is a waste of time when again, you could script it.

done
 

Yeah i know i scripted the state myself and now i need to figure out how to add custom sprites lol look at the pictures i need sprites added

[Attachments removed because they contain copyrighted material]

That command could be added yes

It would be good, it's quite long over-due as it would go well with being able to change tilesets.

There is no real need for it to be added though. All of that stuff can easily be rescripted.

No one is saying that it cant be rescripted. It would just save time, and it would be easier.

Either way, there are more important ways in which Graal can improve.

If you wanted the GUI state the same as "default" but with a different look, this would be good.

It would be a poor use of time to script a GUI to simply mimmick the built in GUI with different images.

Not everything can be replaced so easily, e.g. the swamp sprites from sprite.png that are displayed when you are on special tiles - possible to script but requires several scripts.

How would that be hard, just take a picture img of it while ur on it, cut that out and then make it showimg or something while your on the tile? :o

Just a guess, though I am sure that should work.


Also, thankyou for the name change stefan.

We need a way to set and access weapon attributes easier :O
like being able to put
//#ATTR<name> <value>

Would be accessable by weapons[index].attr.<name>

That, or something more dynamic. Perhaps a shared. variable prefix:
shared.a = value;
weapons[index].shared.a == value;