1
submitted 1 week ago by to c/haxe@programming.dev
2
submitted 2 months ago by to c/haxe@programming.dev
3
Haxe 4.3.7 released (community.haxe.org)
submitted 1 year ago by to c/haxe@programming.dev
4
submitted 2 years ago by to c/haxe@programming.dev
5
submitted 2 years ago by to c/haxe@programming.dev
6
submitted 2 years ago by to c/haxe@programming.dev
7
submitted 2 years ago by to c/haxe@programming.dev
8
submitted 2 years ago by to c/haxe@programming.dev
9
submitted 2 years ago by to c/haxe@programming.dev
10
submitted 2 years ago by to c/haxe@programming.dev
11
Haxe Roundup 703 (blog.skialbainn.com)
submitted 2 years ago by to c/haxe@programming.dev
12
submitted 2 years ago* by to c/haxe@programming.dev
13
submitted 2 years ago* by to c/haxe@programming.dev
14
submitted 2 years ago by to c/haxe@programming.dev
15
submitted 2 years ago by to c/haxe@programming.dev
16
submitted 2 years ago by to c/haxe@programming.dev
17
submitted 2 years ago by to c/haxe@programming.dev
18
submitted 2 years ago by to c/haxe@programming.dev
19
 
 

Specifically this font, although I've tried a few. Specifically in HashLink.

Anyone have any tips or best practices when it comes to fonts and FlxText in general? The default font looks great, but I'm finding that just about every other font I try looks kind of terrible. Like sort of grainy, I guess? The default one looks very crisp in comparison. Also, any non-default font that I put in a FlxButton seems to be vertically way off-center, raised up too high.

20
submitted 2 years ago by to c/haxe@programming.dev
21
submitted 2 years ago by to c/haxe@programming.dev
22
submitted 2 years ago by to c/haxe@programming.dev
23
submitted 3 years ago by to c/haxe@programming.dev
24
 
 

So, the FlxG collide method knows how to tell which tiles in a tilemap are walls or not walls, but the overlap method does not. If you write a simple custom collision with the overlap method and tell it to .separate(), your sprite will collide with every tile in the map, not just the walls.

This is expected behavior, as there's a note in the FlxG documentation that says:

this takes the entire area of FlxTilemaps into account (including "empty" tiles). Use FlxTilemap#overlaps() if you don't want that.

On the other hand, the documentation for FlxTilemaps.overlaps() says:

Checks to see if some FlxObject overlaps this FlxObject object in world space. If the group has a LOT of things in it, it might be faster to use FlxG.overlaps().

In my scenario I have a lot of tilemaps and just one object to collide with them, the player. The way this is written, I'm thinking I have to call this method for EACH MAP, i.e. map1.overlaps(player), map2.overlaps(player), etc. Whereas with the FlxG method I can pass it the entire FlxGroup of maps as one parameter and the player as another parameter, which seems way better. I guess I could write a function with a loop that iterates through each map doing this one by one, and then call that in update(), but I'm getting the impression that it might be really inefficient.

What's the best approach here? Am I missing something obvious?

25
 
 

https://itch.io/jam/haxejam-2023-summer-jam

view more: next ›