I wished that would have crashed when i was allowed on G3d, i REALLY wanted to go play with the dragons :)

Hmm that example makes gscript 2 look better. Seems as if for certain things converting to it won't be too hard. Im geussing the for (pl: allplayers) means that it is defining pl as allplayers and will be looking at everyone's values for that.

I understand it ^^

So do i, and Gscript1 just went right over my head.

<3 for GScript2. Like Kai said before, if you've ever used a language like C then you should be right at home with GScript2. :-D

I've been using gscript1 since I first started playing Graal back in like 99 or so..

"I started playing Graal in 1982, but then we called it 'Zelda Offline' in those days.."

:rolleyes:

And the simpler one looks more complicated. I hate it when you have to put it in: "&&.{#, script enabled}+!!@#.. @!}" or at least thats how it looks to me. I'll get used to it. >_<

Ruby (hackish):

NPC Code:

---

def compile_script

  script = "function onCreated() {\n"\

    "  #{@containers.map{|con| control_creation_script(con, 0)}.join("\n  ")}\n"\

    "}"

  File.open('weapon.txt', 'w') {|f| f.puts script }

  ScriptEditor.open_script_window(script)

end

---

I'm a ruby nuby, please explain it :O.
Btw, I'd love -c on #gscript, pls.

Is there an 'estimated' date for the release of a solid v3/GScript2?

This is Graal Online...so...nope ^^

Exactly, and if they did say one....well let's just all look at G3D lol

There was supposed to be a preview in first quarter 2003 haha.

My sentiments exactly.

Query me on freenode ;)

It looks simple to me o.o
Although I did learn Torque Engine script in 2 hours just from looking at the sample files...

I am completely and unsarcastically certain that this is true!

Stefan that warping script for graal 3d looks simple. Even I understand it.

Ehh...?

hey, question. WIll you be able to use Gscript 1 and 2 in the exact same script, like:

NPC Code:

---

if (playerenters) {

for (q: players//not sure if this is usable, just trying to use a gs2 command) {



if (q.x>30) setplayerprop#c, HOLY CRAP! I have been seen with my x above 30 with a combined script that uses GS1 and 2!;



}





}

---

This has already been answered in the thread. Recap: Yes, but don't.

Oh, geuss i misunderstood that part

it should be released soon :( ,expecially for the ones that want everything to be done in Gscript2 like Element.

Hope you're right...

I'll most likely use mainly Gscript1 but adding in things from gscript2 that make the script more efficient.

I'll probably redo Element in GS2.

;)

We are currently testing the new scripting engine and new mudlib with Graal Kingdoms (on hidden server "Scriper Server"). Those are the incompatibilities which I have seen yet:

- this.timeout, this.x, this.y etc. are mapped to timeout,x,y in the new engine, while in the old engine they are normal variables; this is not simple to fix, so it would be better if the scripts are fixed, the npcserver could eventually give a warning if such variables are found when compiling the script

- if (x,y in |0,64|) doesn't work because the comma makes problems; it would be better to write if (x in |0,64| && y in |0,64|)

- function SetAni() { setani sword,; } doesn't work, because "setani sword,;" is internally converted to "setani("sword","")" and function names are case-insensitive, so it would either cause an "endless" loop (if it is allowed to overwrite default functions, like it is currently), or calls to SetAni() wouldn't work because it would call the default function (if overwriting of default functions is not allowed); in the old engine it was not a problem because functions and commands were handled differently

Sounds much better handled then Gscript1 :)

Release the old mudlib for Graal Kingdoms :cool:

Give me money :cool: