posted                      

EmeraldBlyze wanted to know more about cookies and seeing how they confused the hell out of me when I just got started I figured it might help other people as well, therefore I'm making a new topic about it.

Basicly you only have 2 types of cookies, the stock cookie list and the self made cookies.

Self made cookies:
Self made cookies are really easy to make, all you have to do is think of a (logical) name and then SET the cookie. For example we'll call the cookie apple, because we want to see how many times somebodies has earned apples during some sort of (in this case imaginary) minigame.
The current amount of apples will be zero.

SET apple, "0"

You have now succesfully made your first cookie. This hopefully didn't seem to hard yet.
With cookies you can also do some basic math, like adding numbers, subtracting, multiplying and dividing. For example somebody won 1 apple with that minigame. In that case you'll have to add 1 apple to the current cookie:
ADD apple, "1"

The scene host scored a bonus and his amount of apples will be multiplied with 6 now.
MUL apple, "6"

6 x 1 = 6, the current cookie value will be 6 right now.
Next the scene host will spend 2 apples in exchange for something else, in other words we'll have to substract 2 apples from the cookie:
SUB apple, "2"

(6 - 2 = 4, the current cookie value is 4 now)
Finally if we also want to divide the current amount of apples by 2 we'll have to do this:
DIV apple, "2"

In short the math commands are MUL (for MULtiplying), DIV (for DIViding), ADD (for ADDing) and SUB (for substracting).

You could let the actor tell how many apples you have right now. To do that you'll need to read the cookie. This might seem confusing first, but just try it out in a script:
1: You have #<apple> apples right now %1.

In WoS it will show up as:
Farmer: You have 2 apples right now Silver.

Most bugs in cookies are caused by typos (aplle instead of apple) or because people try this:
ADD #<apple>, "10"
instead of
ADD apple, "10"

You can't do any math or set cookies in the read only mode, that's impossible, please keep that in mind when you're working with cookies. (I even fell for this myself several times.)

Basic explaining compare commands you need:
Cookies are mostly useful if you compare them with other values. For example if you have 10 apples you will win something special in that minigame quest.
To do so we need to compare if the apple cookie has 10 apples or not. We can use the COMPARE command to do that:
COMPARE #<apple>, "10"
IF< @notenoughapplesyet
IF= @enoughapples
IF> @hasmoreapples

Please note that WoS needs to read the cookie now, therefore we use #<apple> and not apple. (You can also store letters, words, even sentences in cookies if you want, I'll talk about that later.)

IF< checks if the value in the cookie is smaller then 10. IF= checks if the value is exactly the same and IF> checks if the value is greater then 10.

If you want you can also compare 1 cookie with a 2nd cookie, this goes like this:
COMPARE #<cookie1>, #<cookie2>
IF< @1issmaller
IF= @thesame
IF> @1islarger

We also have the STRCMP command, STRCMP stands for string compare, basicly you'll use this cookie for checking cookies who have letters and numbers in them, or words. This is mostly useful in to see if cookie 1 is the same as cookie 2.
For example:
SET banana, "yellow"
SET melon, "green"
SET strawberry, "red"
SET colour, "red"

In this example we're going to compare which fruit has the same colour as the current colour in cookie #<colour>. As you can see the strawberry and the #<colour> cookie match, but since WoS isn't as smart as us we'll have to use the STRCMP command to figure that out:
STRCMP #<banana>, #<colour>
IF= @colourmatch1
1: I'm sorry but the banana is colour #<banana> and the colour we're looking for is not.
STRCMP #<melon>, #<colour>
IF= @colourmatch
1: I'm sorry but the melon is not the colour we're looking for.
STRCMP #<strawberry>,#<colour>
IF= @colourmatch3
1: I'm sorry but this strawberry does not have the right colour.
END
@colourmatch
1: Yay you found the right colour!
END

I hope this made some sense... In case it didn't then just reply and I'll try to explain it better.

Last we also have the STRSTR command to play with. STRSTR stands for string in string. Cookie values (the numbers and letters) are also called strings. Sometimes you have a cookie that is partially in cookie 2 also. This makes probably more sense with an example so here goes:
SET cookie1, "Bush"
SET cookie2, "I don't like Bush."
STRSTR #<cookie1>, #<cookie2>
IF> @foundtheword
1: Cookie 1 was not found in cookie 2.
END

You have to use IF> here instead of IF= because of some C stuff which samsyn explains a lot better then I did.

quote:

---

NOTE: use IF= to see if the string was NOT inside the other. It's odd, but it's easier to remember the behaviour if you are a 'c' programmer, since strstr returns NULL if the string is not found.

---

You can off course also do something like this:
STRSTR #<cookie1>, "We all love Clinton."
IF> @foundtheword
END

In short:
COMPARE - Use this one to compare numbers only, it won't work with letters and other characters.
STRCMP - Use this one to find out if cookies who contain letters and numbers are a match with your other cookie (or word, soul ID, whatever you want.)
STRSTR - Use this one to see if the first cookie is in the 2nd cookie (or to put it more corrent, if the first string is in the 2nd string).
IF= - Use this one to see if cookie 1 equals cookie 2.
IF> - Use this to see if cookie 1 is larger then cookie 2.
IF< - Use this one to see if cookie 1 is smaller then cookie 2.

Things to watch out for:
You can use COMPARE for numbers only! Else it simply won't work, some people forget this sometimes.
Don't forget that WoS needs to read cookies, if you write COMPARE apple, "10" instead of COMPARE #<apple>, "10" this will make a major difference for WoS.
Use the IF commands as I wrote them down, Between the IF and =,> or < may NOT be a space. So either use IF=, IF< or IF> and not IF =, IF < or IF >.
After writing down the IF as it should you always have to follow it up with a link, like @gohere and not gohere Also DON'T put any commas between IF= and @link, most likely WoS won't read the line in that case. A good IF command looks like this:
IF= @link
a completely wrong one like this:
IF =, link
This is one of the most caused bugs when working with cookies and is often one of the hardest bugs to find. Even experienced world developers still have this bug sometimes.

If you like you can also read all this info at http://www.synthetic-reality.com/wosquest.htm#Quest
Sometimes this may be confusing though, so I hope that my examples cleared up some of that confusion. Actually I recommend looking up all the above on that webpage, that's the main source I used to learn how to use everything myself.

Stock cookie list:
Basicly the stock cookie list is a long list with mostly read only cookies made by samsyn. These cookies give all kinds of useful values (numbers/letters) about the scene hosts character, the scene itself, monsters, spells, items, pets, real life time, gender and even the server.

Mostly these cookies are read only, but some of them you can set yourself.
For the full list of stock cookies and which ones you can set I have to refer to http://www.synthetic-reality.com/wosCookies.htm#Stock%20Cookies

Let's see what you can use them for though.

Example:[
You have made a quest and to finish the quest the scene host needs at least 45 Wisdom (more is allowed), a pet of level 70 (can't be higher or lower), full HP, at least half MP, he must be carring lesser then 50,000 GP and it has to be 5 pm in real life.

Nice quest huh?

To check if somebody has at least 45 wisdom you'll first have to look up the stock cookie for the scene hosts wisdom, this cookie is called #<num.hostWIS> as you can see in the stock cookie list (the link I gave earlier).
To make it easy on myself I'll just write down the entire thing, with some self study you should be able to figure out what happens where. Read carefully what has to be done and then check what's happening in the script written below.

COMPARE #<num.hostWIS>, "45"
IF= @questpart2
IF> @questpart2
1: I'm sorry but you're not smart enough yet, so you can not do the quest until you gain more wisdom.
END
@questpart2
COMPARE #<num.hostPetLevel>, "70"
IF= @questpart3
1: I'm sorry but your best pet is to high or to low in level. Get it to level 70.
END
@questpart3
COMPARE #<num.hostHP>,#<num.hostMaxHP>
IF= @questpart4
1: I'm sorry but it seems like you don't have full HP right now.
1: Your HP is current #<num.hostHP> HP and it should be #<num.hostMaxHP> HP.
END
@questpart4
SET checkMP, #<num.hostMaxMP>
DIV checkMP, "2"
COMPARE #<num.hostMP>, #<checkMP>
IF= @questpart5
IF> @questpart5
1: I'm sorry but your MP is to low right now.
1: You need to get your MP up to #<checkMP> MP.
END
@questpart5
COMPARE #<num.hostGP>, "50000"
IF< @questpart6
1: I'm sorry but you're carrying to much GP right now.
1: You have to carry lesser then 50,000 GP.
END
@questpart6
COMPARE #<num.timeHour>,"17"
IF= @questpart7
1: I'm sorry but entered this scene at the wrong time, try again later.
END
@questpart7
1: Yay, you're meeting all my requirements to do this quest.
END

Please note that since all my cookies that I used only contain numbers I only have to use the COMPARE command and not the other 2 compare commands.

Morphing into another class:
This seems to give problems to from time to time and you should be able to handle it now if you understand everything I wrote so far, but to show how easy it is to morph I might as well explain it here too.

As you know there is a cookie called #<num.hostClass> To morph into a new class you have to set this cookie to a new value (the class ID you want to morph in). All you have to do is:
SET num.hostClass, "5"
and you'll morph into class 5 now. (In levels.txt you have to divide the class ID with 100 to find the actual class ID.)
Please note that you're setting a cookie and not reading it, so don't use SET #<num.hostClass> cause that won't work.


I hope this covered the basics of cookies, so far writing this thing took me 1,5 hour so I think it's time to stop. If you have anymore questions about cookies then please post them in a reply and I'll try to respond a.s.a.p.

Silver

[ 10-18-2003, 01:47 AM: Message edited by: IceFox/ Silver ]

--------------------
Silver
RoT's Homepage - ProxBeta

posted                      

quote:

---

SET <cookieName>, <cookieValue>

This command sets the named cookie to the specified value. A cookie is just a named string variable, stored in the scene host's character file. Once set, you can pull a cookie back out of thin air by using the #<...> syntax.

---

It's a bit hard to explain what cookies exactly are if you really don't have a clue. Basicly cookies is data that can store real time information, like answers that were given to questions, how long it took somebody to solve a quest, how much somebodies strength increased from level 54 to 67. That are just a few examples, cookies can be used for many things and they make my life as a scripter a lot easier.

I hope this helped you a bit.

Silver

[ 11-23-2003, 01:07 AM: Message edited by: IceFox/ Silver ]

--------------------
Silver
RoT's Homepage - ProxBeta

posted                      

quote:

---

On Topic
I need help with cookies Ice fox I wanna make a cookie system...Well you tell me if I need cookies to do this.. If youvve played Final Fantasy 9 you'll know about Stallizios if not there are 13 special coins you collect and give to someone to get prizes....I am going to scatter about 20-100 Items called the Feathers of the Eaglet or something like that around my world.....But Do I need cookies or Heaps of tokens? Because when you get a certain number of em i want something to happen.

---

As a dedicated FFF (Final Fantasy Fan) I have indeed a FF9 copy here, in fact the original idea for my auction script came from FF9. I never got to collect more then 2 or 3 coins though... Anyways you won't be needing cookies for this script and you only need 13 items (those coins) and perhaps a few tokens.

Basicly your script would look like this:


Info:
I'm only doing 4 coins in this script else it's to much work for a short example, with some experimentating you can figure out the rest yourself.
Using item 301 as coin 1, 302 as coin 2 etc. You should make this soul items and you could write new quests for people to get/ find these coins.


SCENE 500, grass,SCENE, "Coin Man",0,0

ACTOR 1, "Coin Master", coinman, 4, 20,80

IF T401, @didquest
IF T400, @back
1: Hi there, I'm the Coin Master,
1: if you find the 4 hidden coins in this world then I'll give you a special reward!
HOST_GIVE T400

@back
1: Hey you're back...
1: Let me see if you got all 4 coins already.
WAIT 5.0
IF I301+I302+I303+I304, @coins
1: Hey man!
1: Don't be pulling weird tricks on me!
1: You don't have all 4 coins yet, don't get back here unless you do.
END
@coins
1: Great!
1: You got all coins!!
WAIT 3.0
N: The Coin Master takes your 4 coins...
HOST_TAKE I301
HOST_TAKE I302
HOST_TAKE I303
HOST_TAKE I304
1: Alright, fair is fair, here is your reward.
WAIT 3.0
N: You learnt %S600!
HOST_GIVE S600
HOST_GIVE T401
1: Time for me to enjoy my nifty lookin' coins.
1: See you later %1
MOVE 1,-20,80
END
@didquest
1: Hey %1, thanks for giving me those coins.
END

I hope I kept it easy enough to understand.

Makarei, worlds have simple, normal and advanced scripts mostly. RoT isn't all uber 1337 scripting lol, it'd probably give me a large headache if I would only make advanced scripts. However if you make scripts more complicated you can also make them shorter usually (that's pretty much the reason you make them complicated in the first place).

Some of you may know my item tracer script, to find 1 item in a world by it's name I only need like 38 script lines in total now and I can very easily expand the script to search for 10k items instead of 100 items but just changing 1 number. Imagine I had to write out the entire script to search through every item without cookies... Can you imagine it? Good, well now try imagining to upgrade that script to find 10,000 extra items by their name. (I know the item limit is 5119 in WoS, but if it was more it'd require a lot more scripting too.) You'll probably get the idea... about 4 lines per items would make the script at least 40,000 lines long.
Personally I rather go for 36 lines in that case.

You can basicly script most things without cookies, but if you want to make your life easier then cookies can be really useful at times.

Silver

[ 11-29-2003, 12:53 PM: Message edited by: IceFox/ Silver ]

--------------------
Silver
RoT's Homepage - ProxBeta

posted                      

quote:

---

Silver, could you please post that script or email it to me? It would be really useful. Can it be adapted for spells too? Also, can it put a number in a cookie and then give the item of that number?

---

Actually...

The item tracer still needs to get updated to allow more search functions, I did indeed already make a spell tracer script too!
The spell tracer works really well and is pretty cool.
I also want to add a monster tracer script.

All of it will be included in proxbeta v2.1
Right now the latest proxbeta version that's published is proxbeta v1.8

You can download it here: http://members.home.nl/epsilon5/proxbeta_v1.8.zip

Compared to the newest proxbeta version (v2.0) this version is really crappy, but the item and spell tracer work pretty well. The newest versions are a lot more user friendly but I haven't had time yet to update proxbeta and allow even more commands (for example setting scene flags too).

Once I added the monster tracer, updated item tracer and added the other commands I wanted to add several months ago already I'll publish the newest version. I'm glad people are still showing intrest in it, it takes quite some time to update all of it since I'm so low on time always.

Silver

[edit]

quote:

---

BTW, NOT having any cookies in your world does NOT make it bad.

---

I completely agree with that. In my first scripts I never used any cookies and could do almost just as much, it usually just takes more time to get things done though and scripts will become larger. Cookies are more complicated but can make scripts a lot shorter, however you can do just as much without cookies.
When I started world developing I learnt everything except cookies, I saved those for last. When I finally managed to do all scripts pretty well and memorized most of those script commands I started to learn more about cookies and thanks to Corpse Collector and Dazman I eventually understood what cookies truly are about. Since then I love them, but before then I really hated them since they were so confusing first.

That's also one of the reasons for this topic, trying to learn others how to work with cookies, what to do and what not to do.

[ 01-08-2004, 02:21 AM: Message edited by: IceFox/ Silver ]

--------------------
Silver
RoT's Homepage - ProxBeta

posted                       

code:

---

  
SCENE  100  stuff, "The Inn", 0, 0
ACTOR   1, "John the Innkeeper", Johnny, 1, 71, 17
SET  innprice, 30
MUL  innprice, num.peopleinscene
1: Greetings, %1, the price for your party of #<num.peopleInScene> to stay one night is #<innprice>. 
1: Will you stay the night?
ASK   32000
  

---

posted                       

code:

---

 MUL  innprice, #<num.peopleinscene> 

---

code:

---

 MUL  innprice, num.peopleinscene 

---

but that's just what i think...

--------------------
Viva La Resistance!

posted                       

code:

---

SCENE 100 Bedroom,SCENE,"The Adventurer's Inn"
	ACTOR	1, "Ralph the Innkeeper", joshTownsfolk, 9, 17, 71
	SET  innprice, 30
	SET  people, #<num.PeopleInScene>
	MUL  people, #<innprice>
	IF DEAD, @Dead
	@alive
	1: Hello, your party of #<num.PeopleInScene> can stay the night for #<People> Septi. 
1: Would you like to stay?
	ASK 32000
	IF YES, @Yes
	1: Please come again.
	END
@Yes
	IF	G#<People>, @canAfford
	1: I'm sorry, but you don't seem to have enough money.
	@CanAfford
	1: Thank you. Rest well.
	WAIT	3
	HOST_TAKE	G#<People>
	GIVE    H1
        GIVE	H32000
	GIVE	M32000
	END
@Dead
	1: Hmm.. You seem to have been seriously wounded in battle.
	1: Let me take care of that for you...
	WAIT	2
	GIVE	H1
	1: All better!
	GOTO	@Alive
	END

---