onwall and such
 

can someone thuroghly explain onwall,onwall2, onwater, and things of the such. Please. The wiki doesnt help much for me.

onwall(2) detects if a tile is blocking. onwater(2) detects if a tile is water. onwall and onwater check a single tile, while onwall2 and onwater2 check an area of tiles.

onwater/onwater2 checks for lava and water tiles
onwall/onwall2 checks for anything that should be blocking according to the default system (includes players/npcs).

onwall(x,y) tells you if the specified coordinate is blocked
onwall2(x,y,w,h) tells you if there is anything blocking within the specified area

ok thanks, I got it BUT, with onwall2 is it possible to just detect a blocking tile without specific coordinates? like this.x???

Yes. For movement systems, people use player.x and player.y to detect. The onwall2 function will put in the value of this.x for the x-coordinate to be checked.

so it would be like this?

if (onwall2(player.x,player.y-0.5)) {

if so how can I make so it doesnt need to read one the variables and just one of them.

Not quite...

onwall2(x,y,width,height) returns a boolean value (true or false value).

So if you wanted to see if the left side of a player was blocking, for example, it would look something like this:

if (onwall2(player.x,player.y+1,1/16,2)==true) {
player.blockleft = true;
}
else {
player.blockleft = false;
}

oh I see. Thank you much. ^.^

EDIT: Okay, it work on all walls but down and right... ?

a little bit of redundancy here.
onwall2(player.x,player.y+1,1/16,2)==true
true == true returns true
false == true returns false
so you can just do: if (onwall2(x,y,w,h))
otherwise it would be doing a double comparison, which should be avoided, although it really won't matter much unless you're doing a long for loop or something.

FIXED.

When you have the benefit to, always listen to Massokre over me in scripting advice. I, for example, was unaware that it automatically interprets (the question) as a boolean (question).

That is pretty much exactly what I said, except you tried to add the 'players/npcs' thing, but left something out. If it is a no playerkilling zone (or the noplayersonwall() function is called, players are not counted as blocking.)

It's not redundancy. You are not doing double comparisons. That is the exact same thing as if you leave it out.

yea, noplayersonwall() will make players not detected by onwall.
while playersonwall() will reverse that.
using a no PK zone will imply noplayersonwall, but I haven't gone as far to see if calling playersonwall() would reverse that, and I don't use onwall anymore, but a function I scripted that detects tiletypes, npcs, and players on different cases.

And yea, it is redundancy.
You already get a return value of true, then you see if it is equal to true.
Otherwise you get a return value of false and you see if it is equal to true, and because false != true, it returns false. It doesn't really matter if you say ==true, but it's still redundant.

ok now for tiles. I know you can detect tiles with tiles[x,y] but how do I use this?

It's just an array that stores values that represent different tiles. Doubt anyone's made a list of all the tile values. I think I've made an equation for it though (back when I made a gs1 tile editor script).

tilex + tiley * 16
reflects the position of the tile on the tileset image.

You don't need to use it unless you have a need to detect the different codes for tiles.

ok thx

Simply put: You are an idiot.

The client/server is going to do the == true check regardless if you put it or not. It does not do it twice if you put it. I will say it one more time: There is no redundancy in that statement.

No, why would you make a statement true==true.

What if, for, and while statements do is interpret boolean values.

By putting (onwall(x,y) == true), you're comparing a boolean value to a boolean value, which isn't necessary. onwall(x,y) already returns true or false, and then you're comparing it to another boolean value. Putting (onwall(x,y) == true) would be the same thing as putting (onwall(x,y) && true), just not necessary. The only reason anyone should put ==true or ==false is if they believe that it would improve readability, and it usually has negative effects on the readability of the code.

Doodeedoo..

if (onwall() == true) is redundant. if (onwall()) is shorter and, in my opinion, easier to read.
However it doesn't really matter, so who cares?

I think I've heard that before in this thread before okiesmokie went psycho on me, and although that seems to be a pattern, I'd rather have him realize I'm right and he's wrong because I enjoy lowering the pride of narcissists. What's the proud boy gonna argue now, eh?

Both are perfectly fine, I guess. Except one of them is like doing:
Matter of preference, in my opinion.

He is trying to say it's redundant to the interpreter, which it isn't. Even if you don't put ==true, THE INTERPRETER WILL STILL READ IT THE EXACT SAME. IF YOU PUT THE ==true, IT WILL NOT TRY TO ADD SOME RANDOM **** TO MAKE IT MORE PROCESSOR INTENSIVE. God. Learn to ****ing read.

well, only if it ignores the syntax. The boolean comparison is still there. I love how you're flipping out about this, it's not a big deal.

Pixel. Not tile.

That is for the board array. The tiles[x,y] syntax is magical and does not require fancy maths, you just separate the coordinates with a comma.

You are wrong. Stop violating the forum rules

Yea, that just breaks every rule ever made for that operator, but stefan can break it because he's stefan.

Wait so can some now explain to me tile[x,y]; is it like a array or somethin?

It is like a function with [ ] instead of ( ) except you can assign to elements as if it was an array.

tiles[x,y] just gives you the tile index at x and y. Tilesets are broken up into 16 x 16 pixel 'tiles', and each tile has a unique index. This is just used to read and write these indecies. Experiment with it,

function OnMouseDown() {
player.chat = tiles[mousex,mousey];
}

to check tile indecies, and you can write them like so

function onMouseDown() {
tiles[mousex,mousey] = #;
}

Hope this helps..

Breathe!

WOOOOOOOOOSAAAAHHH...

Unless the compiler tries to trim it, it does make it more processor intensive, but only by a negligable amount. And the fact that the compiler would have to trim it would just make it more processor intensive at the time of compilation itself. :frown: But yea, I agree. Calm down, it's not like it really matters.

Triple post, you fail. Stop violating the forum rules. Use the ****ing edit button.

Read the forum rules. He is using hybrid mode.

Also, I am not wrong about the == true thing.

Tell me, why would you write
if( (x==2) || (x==3) || (x==5) || (x==7) )

When you could write

if( (1<<x) & ((1<<2)|(1<<3)|(1<<5)|(1<<7) )

I'll tell you what though, I've only been recently learning how to use bitwise operators.

Then why stop there instead of doing if ((foo() == true) == true)?

If you are using the new engine...

NPC Code:

---

if (x in {1, 2, 3, 5, 7})

---

I know
you can also do things like

NPC Code:

---

if ( (x|y) in |22,42| )

---

Actually, couldn't you have done that in the old engine too (the former)?

However, let's say you have

NPC Code:

---

 if ( x in arr ) 

---

I've had a problem in which my array has to contain multiple values. It can't just contain one value. In my movement functions there's generally multiple parameters in the array, but what if you wanted only one value in the array? I've had to use switch (arr.type()) to cope with the language not being very great with array sizes of 1. Of course it's not really an array if it only has one value, but the fact that it's usually an array, it might make it good to have the in operator behave like == when the right operand contains a single value for better dynamic behavior.

Because the compiler would interpret those as bitwise operators. if(function()) is doing an '== true' check, if(function() == true) is NOT doing two checks for true. If you honestly think I am wrong in this, then you would think that if(function() == false) is doing a check for both true and false.

Read my damn text before you reply. I am done with this thread.

if (function() == false)

CASE 1:
function() returns true
true == false
true is not equivalent to false, therefore the statement is false.

CASE 2:
function() returns false
false == false
false is equivalent to false, therefore the statement is true.

Tell me, what's the contrapositive to p->q?

Seriously, take a course in logic or something.