The Dink Network

I'm called magicman here, but my real name is Joeri van Eekelen and I'm from The Netherlands.

I'm 37 years old and currently being a programmer who's involved in social housing software.

My interest in Dink goes off and on. It is currently off. Check back later. I kinda like sourcediving into the Dink engine, which is an awesome way at figuring out why some unexpected behaviour occurs.

Scripting techniques rant
Some Notepad++ Python scripts
Error in map_tile(); documentation.
Why void touch( void ) freezes, void die( void ) fails to complete, and you need wait(1) in loops.
About external(), spawn(), procedure calls, run_script_by_number.

For those interested, you can read my Dinkerview from early 2014.

j.v.eekelen@gmail.com
Private Message

The screen is 640*480, but the playing area is only 600*400. The last 80 pixels of the height are taken by the statusbar, and the 40 pixels of width are split into the two screenlock-bars of 20 pixels each. So if you want something to move to the leftmost pixel, you'll want to move_stop(&sprite, 4, 21, 1); The dink engine will think that if Dink (just dink) is on a x-coord < 21 he must move to the next screen.

Also, if you try to move to the east (dir 6) but to an x-coordinate that lies to the west, Dink (or whoever you want to move) won't move at all. Similar cases with moving north to a pixel south of the sprite, or moving west to a pixel on the east, etc...