Calling All Pixel Movers

Page: 1 2
May 14 2011, 8:12 pm
Works amazingly on my end.
May 14 2011, 8:50 pm
@Forum_account:
//from keyboard.dm, line 89
            var/windows = winget(src, null, "windows")
            var/macros = params2list(winget(src, windows, "macro"))

The skin reference says:
winget(player, null, "macros") will return the IDs of the macros available in the program, separated by semicolons.

So shouldn't it be
var/macros = params2list(winget(src, -->null<--, "macro"))

?
May 14 2011, 8:53 pm
Having taken a look at the Pixel Movement library and cycled through the demos, I'd say it's a pretty outstanding library for smooth and efficient pixel movement. Although I'd have to start a project with an intention to use it from the start to get the most use out of it.
May 15 2011, 2:01 am
Kaiochao, the winget call that I use is ok, but after further inspection the problem was not as I described. The problem was actually that macros is an associative list and I wasn't treating it as such. In the loop, m isn't the name the of the macro set, macros[m] is.

I'll take a look at your suggestion, it'd reduce the number of calls to winget by one.
May 19 2011, 3:07 pm
Ive been thinking about adding Pixel Movement to my anime fan-game but it seems im having problems with mobs walking through each other. And also ive been using it for my other fan game and its works very well but its also having the same problems.

http://www.byond.com/games/Aniste/NarutoWorld
http://www.byond.com/games/Aniste/NarutoBattle
May 19 2011, 3:09 pm
Make sure the can_bump() proc has this in it:
if(ismob(a))
   return a.density
Page: 1 2