Shooter Demo

by Forum_account
A sample top-down shooter. [More]
To download this demo for your Linux/Mac installation, enter this on your command line:

DreamDownload byond://Forum_account.ShooterDemo##version=2

Emulator users, in the BYOND pager go to File | Open Location and enter this URL:

byond://Forum_account.ShooterDemo##version=2

724 downloads
Version 2
Date added: Oct 15 2011
Last updated: Feb 25 2012
5 fans
A basic top-down shooter that uses the Dynamic Lighting, Mouse Position, and Pixel Movement libraries.

Look through the code to see how things work, or expand on it to make your own game. You can make simple modifications - new maps and graphics. Or more complex changes - new enemies and attacks.

Comments

Forum_account: (Jun 1 2012, 3:57 am)
That makes sense. The slow_down proc used to only be called for mobs with clients, now its called for all mobs.
Forum_account: (May 31 2012, 3:30 pm)
I think it was the change to can_bump. Previously dense mobs could pass through each other, now they can't. This demo could probably use a lot of fixing up.
FIREking: (May 28 2012, 12:15 pm)
Bullets only go like an inch in front of mobs.
Kiohstuff: (Mar 2 2012, 2:11 pm)
thank you, changing control,params to anything,anything,anything,params fixed it, although why the original code worked just fine in a program that did not contain your mouse movement or pixel movement libraries still escapes me.
Forum_account: (Mar 2 2012, 4:27 am)
Kiohstuff wrote:
For some reason when using these libraries I am unable to enable the right mouse button properly. When I enable it, right-clicking still registers as a left click. Here is a snippet of code in case it helps.
MouseDown(control,params)
params = params2list(params)
if("right" in params)
world<<"right-clicked"
else if("left in params")
world<<"left-clicked"

I always get the output "left-clicked".
This code works when it is separated from these libraries.
Thanks in advance.

Add "world << params" as the first line of the MouseDown() proc to make sure that the params are what you think they should be.

The atom's MouseDown() proc takes three parameters, the client's takes four. So what you're calling "params" there is actually the control parameter. I don't think this has anything to do with what libraries are included.