posted                       

code:

---

 @eventPlayerEnter
	COMPARE #<num.peopleInScene>, "#<camppopulationlimit>"
	IF= @lock
	IF> @lock
	END
@lock
	LOCK 1
	END
@eventPlayerExit
	COMPARE #<num.peopleInScene>, "#<camppopulationlimit>"
	IF< @unlock
	END
@unlock
	LOCK 0
END 

---

posted                       

quote:

---

Levels.txt

In addition to the START_ELEMENT_PP, MAX_ELEMENT_PP, START_HAND_PP, and MAX_HAND_PP commands, we need a new command to allow the max level that pp can be spent on an element or hand. I.E. after say level 5, you can no longer increase the level by pp, and it must be by using a spell/hand in battle. You can still reach level 9 like this, you just have to put work into it.

The idea behind this is so people can't use auto-clickers/hacks to boost pp and them spend the pp maxing out elements and hands.

---

We also need a MAX_LEVEL <##>

That would help so that if you want the max level to be 80, not 100 in ur world, u can set that. And it will also no longer let your pets go over that level.

works good for class changes, so you can force players to class change in order to continue leveling.

or in short: I need this alot for my world. plz <-- dont let this face down.

posted                       

quote:

---

[ I always like it when someone documents something like this so neatly... makes me want to actually do it... So I started thinking about 'is this the time I finally add support for world-developer-defined-skills? and again I keep coming back to 'what difference would it make to actually be good in a skill'

I mean, in the simplest case (above), the only thing the skill did was let a script test the host's current skill level. Then the script itself would do something based on that.

But I think most people would quickly want a skill level to do something else... like.. defense against certain atatcks, enabling certain spells, etc. I mean things which actually require skill-specific game engine support.

Also, I can't help but see a parallel with the extra elements (elements 9-255)... that they are, when looked at with squinty-enough eyes, actually skills. There we have the advantage that all the weapons armor and spells already have element affinities (hence could be skill affinities).

It all pretty much comes down to what the player believes is happening, since in the end it's really just some spell attack with a name like 'pick pocket' or something. If the engine doesn't support some core function (like 'transfer GP from target to caster') then it won't really make sense to the player.

SO... I think it would have to get developed something like this:

1.) I have to add 'cool special effects' (like diseases) each with some sort of code ID.

* e.g. transfer GP, HP, MP, PP, XP between attacker and attackee (and others)

2.) Ability to bind combinations of 'specials' to individual spells.

3.) Ability to bind spells to element/skills (done!)

4.) Ability to attractively display existing skills and levels. (probably this would merge with/imitate the spell panel in some way... forcing you to pick spell or skill mode, with skill 'selectors' like the element 'selectors' Internally it would all be spells and elements, but we give illusion to player that skills are something else. World developer defines skill-spells as meets their needs.

5.) distribution of enough per player skill info for satisfying experience, obsessive/compulsive competition.

6.) Increased total # of spells

7.) Ability to modify/query skill levels by script.

Perhaps re-factoring the higher elements into 'skills' in the user interface is not an awful first step, even if skills are not particularly useful outside of scripting initially.

-s]

---

posted                       

code:

---

SCENE 100
; Some useful subroutines

@AddThreeNumbers
; assumes three values passed.  values on
; CALL command line are loaded into cookies:
; arg0, arg1, arg2, ... (and cookie 'numArgs' tells how many)
  PUSH sum  ; save this cookie on stack
  SET sum #<arg0>
  ADD sum #<arg1>
  ADD sum #<arg3>

  SET arg0, #<sum>
  POP sum   ; restore original cookie value
  
  RETURN  #<arg0>  
END


SCENE 1000
; a real scene which calls subroutines

  1: Let's say cookie 'arg0' is used to return single values

  CALL  100:AddThreeNumbers  1, 2, 3

  1: The sum of those three numbers is #<arg0>

END

---

code:

---

SCENE 480

@AddThreeNumbers
   SET temp0, #<arg0>
   ADD temp0, #<arg1>
   ADD temp0, #<arg2>
   RETURN #<temp0>

END


SCENE 498

  CALL 480:AddThreeNumbers 1, 2, 3
  1: The sum is #<arg0>

  CALL 480:AddThreeNumbers #<num.hostX>, #<num.hostY>, 47
  1: Look ma, it works with cookies.. #<arg0>

END

---

posted                   

code:

---

WRITE MyHTML, "This is a new line of text"  

---

code:

---

 WRITE "This is a line of text" 

---

code:

---

@QuestStart
SET RandomQuest1, "Kill 4 Black Wraths"
WRITE  "NNN = #<RandomQuest1>"
END
; At this point, our player's MyHTML.html
; file should look like the following when open
; -------------------------------------------
; | NNN = Kill 4 Black Wraths               |
; |                                         |
; -------------------------------------------
; The ugly box above represents the HTML page
; as it would be seen by the player.

@QuestReject
SET RandomResult1, "You refused the task like a coward."
WRITE "NNN = #<RandomResult1>
; Our MyPage.html now has 2 lines as follows:
; ----------------------------------------------
; | NNN = Kill 4 Black Wraths                  |
; | NNN = You refused the task like a coward!  |
; ----------------------------------------------

@QuestEnd
SET randomresult1, "You obliterated the Black Wraths"
WRITE "NNN = #<randomresult1>"
END
; Now we have a page that reads
; ----------------------------------------------
; | NNN = Kill 4 Black Wraths                  |
; | NNN = You obliterated the Black Wraths!    |
; ----------------------------------------------

---

I know my name will be cursed and many pins stuck in Voodoo Mj dolls for this suggestion, and I don't blame you as I just know this would be a right pain to make possible, but, many developers are starting to apply randomness to their worlds and what better way to be non-linear than total randomness right?

[ 10-20-2005, 06:23 AM: Message edited by: Sir Mj ]

--------------------
Come ride with me through the veins of history,
I'll show you how god falls asleep on the job.

posted                   

quote:

---

Still, might be able to do something along the lines of:

SEND_NON_PARTY_MEMBERS_TO_SCENE x

which would pick someone in the scene who was not currently a member of the current host's

party and make them become the host of a new scene, that other non-members would be coerced to join.

BUt if you had recently given a PARTY command to break up the party, you might need to add a WAIT

to let the dust settle before issuing this command, since the host has to know the party affiliations before it could work.

And maybe as well:

MAKE_SOME_NON_PARTY_MEMBER_THE_NEW_HOST_OF_THIS_SCENE

to let the host leave the scene without destroying it.

---

posted                       

code:

---

;[#]			Every mission needs a unique 'Job Number'
;Name= 			Every mission should have a short name
;Qualify= 		this is a conditional string, as used by the script IF command.  
Only qualifying characters can do mission
;Desc=  		This is the longish description of the mission.  
Not TOO long, I hope
;Trophies= 		This is a list of required trophies, like "3x12,4x17" 
(Needs 3 trophy12s and 4 trophy17s)
;RewardGold= 		Gold provided as reward 
(assumed to be 0 if omitted)
;RewardGive= 		Object given,  uses same syntax as GIVE command to give something 
(S12 = spell12, I33 = item33, ...)
;RewardTake= 		Object taken,  uses same syntax as TAKE command
;RewardLevel= 		Give them enough experience points to take them from 0 
to this level, say "3.2"
;RewardPP= 		Participation Points Given
;RewardWP= 		War Points Given
;RewardToken= 		You can give ONE token 
(use negative value to REMOVE the token)
;AcceptGive=		Object given (GIVE syntax) when you accept the mission 
(maybe something you'll need)
;AcceptTake=		Object Taken (TAKE syntax) when you accept the mission
;AcceptMsg= 		A message sent to user when they accept the mission
;AbandonGive=		Object given (GIVE syntax) when you abandon the mission 
(maybe a cursed item or something)
;AbandonTake=		Object taken (TAKE syntax) when you abandon the mission 
(maybe what they gave you, maybe not)
;AbandonMsg= 		A message sent to user when they abandon the mission
;FootNote= 		A footnote added to completed missions

---

A mission reward can,
in theory, be something bad. For example

RewardTake=G1000

But you can't take away XP or PP. You CAN take away a token (which could be good or bad)

---

Also, notice I added things like:

AcceptGive
RewardTake
AbandonTake

so you can reward/punish (or maybe provide some item or spell which will be needed for the mission)

Basically, these are ALL optional, but they let you give/take an arbitrary thing at each transition (accept, abandon, reward), which I hope will let you do things like "you'll need this lockpick" and "you won't need that lockpick anymore" and "here's a cursed soul for running out on us" and "let me remove that token from you, so you can replay quest 5 after completing mission 33" etc.


The funny thing is that at the end of this, I might have a better idea how to finish my arcadia card game "TurnAbout"



Right now, short of a little simple hacking, you cannot repeat a mission once you have completed it. I am pretty sure I want to add something like:

canRepeat=N

to let you do the same mission up to N times.

but I think I will wait on that. might need some sort of "repeatQualify" string or something...

An Example Mission:

code:

---

[1]
Name=Jelly Trouble
Qualify=V1
Desc=We have a lot of trouble with Jellies around here.  If you could get some Jelly 

pigments for us, we might be able to make an anti-jelly spray to keep them away.
Trophies=5x1
RewardGold=300
RewardGive=I25
RewardLevel=2.1
RewardPP=1000
AcceptMsg=Go forth, brave %3, and squish!
AbandonMsg=We understand, it's a royal pain washing that goo off, isn't it?
FootNote=Well, we appreciate your efforts, but unfortunately it turns out they LOVE the stuff! 
 Miserable little cannibals!

---

posted                      

• Punching twice with fists.
• Casting a spell and hitting.
• Applying a status effect and hitting. (eat poison!)
• Casting two spells. (fire and ice?)

1. You could tack on a new argument somewhere, like making argument 6 have more parameters. But I think it's a bit clunky (though probably rather simple).
2. Those args 10, 11 and 12 aren't used on anything but consumables... Why not give them a use?!
   This can be done by setting these arguments to the values of OTHER items (namely, weapons) that have all the stats you wish for part of the attack. Thus for a sword that hits and lowers stamina I could set arg 6 to something like "-1" to indicate this is a multi-weapon, then set arg 10 to "721" the item ID of my weapon that does a small hit, and arg 11 to "722" the item ID of my weapon that casts lower stamina! Of course, for this weapon I'm not using arg 12, so it's "0", but I'm sure some people would love some sort of triple weapon.
   Another benefit here, is that to equip the weapon you could enforce all the requirements of the items used in the combo. So unless you had the skill to equip both items 721 and 722 in the above example, then that multi-weapon could not be used!

1. Don't change a thing. Just apply multiple effects.
2. Simultaneous animation. Matrix-like effect as you both lunge at them to hit and also stand in place casting!
3. Fast animation. If there are two effects then animate them both in sequence at 2x speed. If three then do all at 3x speed.