quick question
Displaying 1-3 of 3 total.
1
Please enter a numerical value for the importance of this sticky.
Enter 0 to unsticky.
Fire_Warrior

winv2..

how do i instantaneously change the tile location of the [player] entity?

entity.tx[player] is apparently not writtable...

Just finished my save/load menus today and i'm trying to get the character to the correct position after a game is loaded. I have the tile location of where the chr is supposed to be upon loading.. but how do i set it?

otherwards,
WinV2 kicks @$$. gj vecna
My system ported nicely.
The world clock scripts don't seem to want to work.
Its just a function that increments clock variables that you put in a hooktimer(). It worked fine in V2.5b6 and it doesn't do anything in WinV2.

I had to rip out all the 16-bit vc code out for now, including all the fancy gradient stuff.
haven't had time to look further into that arraycheck prob. I turned it off so i could get some work done for now. Its most likely not a problem at all.

asking here becuase i'm lazy.

-FW



Posted on 2001-12-30 21:58:09

vecna

Tile locations:
entity.x[player] = (tx)*16; etc.

Essentially, the original v2 entity system of essentially using 2 sets of coordinates per entity (tile, pixel) was horrid and I did away with it. So there is only one set of coordinates for entities in winv2, and actually they are internally in 16.16 fixed-point format. When reading from entity.x it's converted to pixels, when reading from entity.tx it's converted to tiles. Writing to entity.x works as you'd expect, but I made entity.tx and .ty unwritable because of the way they were used in the original v2: they controlled the obstruction coordinates, not the onscreen coordinates. So you might write to entity.tx before the entity.x had actually reached that exact value. In short, some people's VC code for original v2 might make entities "jump" around unnecessarily if I set up entity.tx writes to just jump the entity to that offset. But just ignoring .tx and .ty writes works in most cases.

.. It just occured to me that it's entirely possible I broke HookTimer when I replaced MMTIMER with a timing thread in the very latest beta. I'll check it out.

I still haven't looked at arraycheck either. I'm going back home tommorow (broadband again! aww yeah) so I'll get back to business then. ^_^

-vecna



Posted on 2001-12-31 13:59:08

Fire_Warrior

may be a bit late, but hooktimer
doesn't work with any function...



Posted on 2002-01-02 17:07:06


Displaying 1-3 of 3 total.
1
 
Newest messages

Ben McGraw's lovingly crafted this website from scratch for years.
It's a lot prettier this go around because of Jon Wofford.
Verge-rpg.com is a member of the lunarnet irc network, and would like to take this opportunity to remind you that regardless how babies taste, it is wrong to eat them.