I started with a simple pixel movement demo a few months ago and it grew in all directions. As a result many hub entries were created to show the different demos: top-down pixel movement, isometric pixel movement, isometric platformer, sidescrolling platformer. Recently I started turning these demos into libraries, resulting in even more hub entries.
The end result is two libraries. Each pixel movement demo I had created has been removed from the hub and is represented as a demo contained in a library. The two libraries are:
This library provides a pixel movement system for top-down and isometric maps. It supports elevation and jumping so you can use it to create action/platform type games or just use its basic pixel movement to create smoother movement in action games. This library takes the place of Forum_account.Isometric.
This library provides a pixel movement system for sidescrolling action/platform games. It has no support for isometric maps.
The libraries are very similar. They both have global loops that call the movement proc for each mob every tick. They have many other vars/procs in common, such as: px, py, can_bump, move, movement, can_jump, pixel_move, set_pos, set_camera. There are some crucial differences so I don't expect to ever combine the two libraries, but they're similar enough that if you're familiar with one you should be able to pick up the other easily.
I was getting fed up with having a messy hub, so hopefully this hub cleanup helps you as much as it helped me.
Copyright © 2023 BYOND Software. All rights reserved.