PLAYERKILLERS

Members
  • Content count

    9
  • Joined

  • Last visited

  1. wip: PLAYERKILLERS.EXCHANGE

    https://playerkillers.exchange/js/game.js Check again, I changed it this morning after your reply.
  2. wip: PLAYERKILLERS.EXCHANGE

    The audio issues should be fixed now. For some reason I had not updated me.audio.init() after converting the files. Thanks again. Not sure if I would be happier with an 8bit sound scheme. I should also add a disable audio button to the HUD. For the UI, I used a mix of GUI_Objects, Renderables, and a bitmap font. It would still need more work for game pad support. Touch targets seem difficult on some devices.
  3. wip: PLAYERKILLERS.EXCHANGE

    I added entity composition, a basic inventory system, armor values, different attack properties for weapons, health potions, and health bars. The NPCs are now less powerful and spawn differently based upon how many NPCs the player has killed. Next I want to add some non-humanoid enemies and work on map generation. The portals I have been using need to be changed. Staircases should give the user a better indication as to when he is moving deeper into the caverns or surfacing. Other (north, east, south, west) portals should just be corridors. I may attempt some urban areas.
  4. wip: PLAYERKILLERS.EXCHANGE

    I did use nipple.js! There are some issues with the nipple not disappearing in some corner cases. I heard something about keyboard input issues with safari in fullscreen. Hopefully multitouch input will be enough for those cases. A message about the distance to the nearest player should appear when you stop in front of a portal. Players are currently spawned in a random map if no players are online and in the map with the least players if someone is online. If you manage to run away, you should be able to leave your attacker surrounded by the NPCs pursuing you. Once alone, the player will heal 5hp for every 3 seconds of idle time. So there is a little room for strategy. Right now these player distance messages are displayed on the HUD and removed by a callback. Not the best design. I am thinking that portals and portal messages should be made into game objects. The client should detect the collision and then ask the server for validation. Next, I want to add multilayer sprite composition. A long time ago I had it working by replacing the renderable with a container of sprites. One of the updates broke this. Not sure about how this is handled currently. Some of the weapon animations from the lpc-universal sprite sheet are over sized as well. These will be the next issues. Also, the players deserve health bars above their heads. I've seen examples of this, so it should be easy to implement. Work continues, the project is no where near complete. Going further off topic, I notice that some of the more popular games which have been picked up by hacker news and reddit still have relatively poor alexa rankings and 'time on site' How are people pushing their content & monetizing? I've some incentive ads which will pop once the player bases increases, but this kind of performance remains to be seen. You guys are the pro developers and naturally I am wondering about the $$$... I am still looking for the right approach for the gaming niche. Again thanks for the feedback and thanks for melon.js!
  5. wip: PLAYERKILLERS.EXCHANGE

    I've added NPCs, touch controls, and fixed the safari issues (ogg was not supported by safari). Description: The playerkillers.exchange is a free to play multiplayer deathmatch game. Players can obtain virtual currency by killing other players and NPCs. The game world contains over 200 different interconnected areas.
  6. wip: PLAYERKILLERS.EXCHANGE

    Thanks for the feedback. I think it is probably better to fix some of these issues before I post it too extensively. All kinds of feedback is helpful for me. Thanks again. TODO: mobile controls description player instructions fix Safari issues multivariate testing for content enhanced hud bots gameplay
  7. Run without rendering (for online game)

    The server's logic will differ from the client's. There's no escaping developing them separately. Just think about what you want for your server side game loop and go from there.
  8. wip: PLAYERKILLERS.EXCHANGE

    Here's a multiplayer pk/deathmatch game I've had on the back burner for awhile. There is still more that needs to be done. The project will probably continue to evolve. Thanks for checking it out. PLAYERKILLERS.EXCHANGE