Qbasicnews.com

me again. i need to move a npc on tile. i figure just array out some (x,y)'s the flag if user is close to npc....um.....your code is very welcom....

That's "welcome"...

npc.x(n) = npc.x(n)-1
npc.y(n) = npc.y(n)+1

war is peace, 1984

Define a Type for all your npc's like this one:


Then define your npc like:
And you're ready to use your npc type.

And by messing and comparing with the x and y values of both the user and the npc you can find out if the user if close to the npc.

could you explain the type thing. i get what it does. is just for Convenience? this is what i'm using to move the guy around. it's nnot good but it's all i can think of

it's to make the code readable.

In qb, TYPEs serve no real purpose. TYPEs are like the XP-type search mechanism: search for images, documents, music files? What was the color of that file? Did it have a cupcake in it...?

TYPEs try to enforce some sort of order on your variables. If you don't have that order in your head in the first place though, types won't help. But they WILL hurt, as type variable arrays are invoked differently than real arrays, and they have limitations when real arrays with the same name are used.

can you just use ! # $ %
what's the difference?

Agamemnus is always wrong when he talks about types, 'cause he hates'em LOL j/k

Types are useful to pass a bunch of related variables to a function just with 1 parameter, for example.

does it run faster?