Possible?
 

I was just wondering if it was possible to have an npc that coulds the time that youa re standng still and everytime you move the time resets

umm correct me if im wrong Kai but maybe a timevar and a position checker that checks to see if the position has moved like

NPC Code:

---

if (!playerx==playeroldx || !playery==playeroldy) {

this.idletime=0;

}

---

or somethin like that for the set back part??

Thanx but Kai its not who ever you talking about lol but thanx

sorry Kai posts here the most and usually fixes people mistakes=p, hmm.. is it just me or have been less people postin here lately:(

yeah not as much ppl used to post here alot but not as much anymroe

its probably laggy and not very good but try this sucka:

NPC Code:

---

NPC Code:


if (created) {

  timeout=1;

}

if (timeout) {

  this.oldx=this.newx;

  this.oldy=this.newy;

  this.newx=playerx;

  this.newy=playery;

  if ((this.newx==this.oldx)&&(this.newy==this.old)) {

    message Player Did Not Move!;

  }

  timeout=1;

}

---

thats just a little bit, but toy with it ...

*starts to tally reasons*

1. They dont script anymore
2. They dont play graal anymore
3. They are so good they dont need help
4. They figure it out themselves:D
5. They just dont care
6. They just dont care about this forum and would rather let it rot:mad:

umm that wouldnt work I dont think because it set the oldx and y before it messages anything or does anything, so it would always stay player did no move if im not mistaken, heres how i would do this

NPC Code:

---

if (playereneters) {

timeout=1;

}

if (timeout) {

if ((playerx==this.playeroldx)&&(playery==this.player  oldy)) {

this.idletime++;

message Idle for #v(this.idletime);

}

if ((!playerx==this.playeroldx)||(!playery==this.play  eroldy)) {

this.idletime=0;

message;

}

this.oldx=playerx;

this.oldy=playery;

timeout=1;

}

---

would this work?

remember...

when you do an arguement such as:

NPC Code:

---

you use parenthesis around each 2 arguements:



if ((arguement1==arguement2)&&(arguement3==arguement4  )) {

}

---

yes, thats the "proper" way, but on my graal it work either way, i really should use tht way more

Ummmmm...Actually thats wrong, well nothing is wrong with coding unless its syntax, but you are not suppose, its just personal style, either works, and either are the right way. The having ((this==this)&&(that==that)) is for multiple statement test as follows:

NPC Code:

---

if (playerenters && (strequals(#a,Saga2001) || strequals(#a,Nick P2P)) {

// do this

}

---

But it doesn't really matter...

I know it doesnt really matter, but it looks cleaner in my opinion

for your script just do this.

NPC Code:

---

if(created) timeout=.05;



if(timeout){

  if(!keydown(0) && !keydown(1) && !keydown(2) && !keydown(3)){

    this.NotMoving++;

  }else{

    this.NotMoving=0;

  }

  timeout=.05;

}

---

even better:

NPC Code:

---

if (created) {

  timeout=0.05;

}

if (timeout) {

  for(i=0;i<3;i++) {

    if (keydown(i)) {

      this.move++;

    } else {

      this.move=0;

    }

  }

}

---

i cant get either one of em ta werk on the second one all it does it stay at 3 and i cantfigrue out what im doing wrong!

Presumably he means clocking the time that you are idle?

No your script does not work as you have to check all vars at once or you will get a value other then 0 while your moving.

just put what you want to happen while the player is at idle in the commented area.

NPC Code:

---

if(created) timeout=.05;

if(timeout){

  if(!keydown(0) && !keydown(1) && !keydown(2) && !keydown(3)){

    this.NotMoving++;

  }else{

    this.NotMoving=0;

  }

  if(this.NotMoving>0){

    // Do stuff when not moving

  }

  

  timeout=.05;

}

---

This might work a little better
 

NPC Code:

---

if(created || playerenters) {

//intalize vars

this.maxidletime = 30; //time (in seconds) that a player can idle for



}

if(timeout) {

  if(this.pos[0] != playerx || this.pos[1] != playery) 

    this.move=0;

  else 

    this.move+=.05;

  this.pos = {playerx,playery};

  if(this.move > this.maxidletime) {

    //whatever you want to do

  }

  timeout = 0.05;

}

---

This would check if you acually MOVED from a spot.

now that works & much better then mine i may add lol

It would be more efficient to check if the player is acually moving than pressing buttons. I also would like to add that

if(condition1 || alikecondition2 || alikecondition3 || alikecondition4 || alikecondition5 || etc etc)

isnt a good programming habbit.

True but in this case a for loop would not work as it would return a var unexpected some times because you need to check all keys at once.

I don't quite understand...
If you are experiecned enough, nothing could really go wrong @.o