Forum :: EOSERV :: EO+ Script Writer

I didn't want to bring up an old topic, so, does anyone have a download to this? Because the site download doesn't work. Script Writer Topic

get v1 :/ vs.2 is for exiel website member or some crap

---
~~ When life give you pasta, you eat it ~~

Download

Casoni posted: (16th Oct 2011, 08:27 pm)

Download

o.o Cant believe people were too lazy to register on the forum to get the genuine direct download. http://exile-studios.com/EO Plus Script Writer v0.2.0.zip Also if you check I updated that thread with the direct download. :P

---
¨°º¤ø„º°¨ Exile Studios ¨°º„ø¤º°¨

The only problem I see with the EO+ script writer is the fact it can still make logic errors or infinity loops within a quest. Such errors would be a two state loop that causes the server to attempt to process quest rules forever. Here is an example:

State First
{
   rule GotItem(2,10) goto Second
}
State Second
{
   rule LostItems(2,11) goto First
}

What would happen at this point is an ugly server lock up because this quest would simply process these rules as fast as your CPU can run EOSERV. Aside from logic errors, the Script Writer is fairly decent. I am not sure if Deathx implemented it, but a nice config file to add new rules would be a very epic addition to it. In any case, quests aren't hard to write. Most decent scripting programs have "auto" brackets and parenthesis that help avoid those mistakes. Also, it would really help if other revisions of EOSERV would drop the use of the escape character "/" before certain punctuation. The original EO+ syntax Vult used was free of that awful eyesore, as is EOSERV Vodka :P

Apollo posted: (26th Oct 2011, 04:03 pm)

The only problem I see with the EO+ script writer is the fact it can still make logic errors or infinity loops within a quest. Such errors would be a two state loop that causes the server to attempt to process quest rules forever. Here is an example:

State First
{
   rule GotItem(2,10) goto Second
}
State Second
{
   rule LostItems(2,11) goto First
}

What would happen at this point is an ugly server lock up because this quest would simply process these rules as fast as your CPU can run EOSERV. Aside from logic errors, the Script Writer is fairly decent. I am not sure if Deathx implemented it, but a nice config file to add new rules would be a very epic addition to it. In any case, quests aren't hard to write. Most decent scripting programs have "auto" brackets and parenthesis that help avoid those mistakes. Also, it would really help if other revisions of EOSERV would drop the use of the escape character "/" before certain punctuation. The original EO+ syntax Vult used was free of that awful eyesore, as is EOSERV Vodka :P

---
https://www.youtube.com/watch?v=d_DFVzxsEUc

Save as *questnumber*.eqf

Apollo posted: (26th Oct 2011, 04:08 pm)

Save as *questnumber*.eqf

---
https://www.youtube.com/watch?v=d_DFVzxsEUc

I thought you meant filesave, yes the quest is loaded into memory at server start up, just as all other resources are. I am not sure what implication you are trying to make by "how do you store...". Doesn't seem relative to quest writing or logic errors.

Lol, I don't either. Hmm, I been on this forum too long perhaps?

---
https://www.youtube.com/watch?v=d_DFVzxsEUc