@immy Nice, this will be really helpful when it comes to debugging. I will check it out.

That's odd. Do you have a coin.png file in your assets folder? Sometimes restarting VSCode tends to fix these sorts of random issues.

Hey @Immy I've just seen you've uploaded a .zip of your code to github which is helpful
https://github.com/ImmyShack/TurnBasedRPG

l but not as helpful as uploading the code itself.

Here's an example of a game I have on github
https://github.com/RichardBray/Kevin-and-Maisey

All the time a change is made to my game I update the code on GitHub as well. It's also easy to read the code on Github like this:
https://github1s.com/RichardBray/Kevin-and-Maisey/blob/master/source/levels/Intro.hx

@immy said in game crashes after pressing "play" button:

I have a github account.
https://github.com/ImmyShack

Ah sweet. It would be great if you could upload the HaxeFlixel game you're working on. If you need help doing so I'll be happy to advise.

Going forward it would be ideal if you were able to upload your code to Github as it'll be easier for me to download and test your updated code.

Anyways, for your first error do you have this among your list of imports at the top of the MenuState.hx* file?

import flixel.group.FlxGroup.FlxTypedGroup;

For your second error. When I was debugging your code I found out the error message wasn't necessarily related to the file that the error is being flagged on.

You'll have to look through your code and make sure you don't have a nested function in a method that you are calling outside of the parent method. Like this:

class Test {
  function methodOne() {
    function functionOne() {
      ...
    }
  }

  function methodTwo() {
    functionOne(); // <-- This won't work
  }

  functionOne(); // <-- This won't work either
}

Actually, I was looking at your "assets/data/room-001.json" and it looks like your numbers don't add up to what the demo has. Take a look at this section

And compare that with the data from the actual demo room-001.json file:
https://github.com/HaxeFlixel/flixel-demos/blob/master/Tutorials/TurnBasedRPG/assets/data/room-001.json

Lol, that's interesting. I'm not an Ogmo expert but I'll take a look at it when I get some time.
Btw two things you should consider:

1 - Getting a Github profile and uploading your project there. It would be easier for people to view the code and make comments on it.

2 - Signing up to Discord and joining the HaxeFLixel channel https://discord.gg/MsEBFF4D it's way more active than the forums and the creators of Ogmo are frequently on there.

Maybe we might need to pair on this, might be easier to debug this over a call, DM me if you're interested.

Anyway, the Player.hx file shouldn't have any collision data in it since the walls variable doesn't exist in the player. IMO you should delete lines 88 to 92.

TBH I'm not sure what the tutorial says but if you think you'll need the update method in player maybe try commenting it out for now.

Thanks for sharing this with me. I've managed to get it working and there are a few things I had to fix. I will lay them out below:

1. in Player.hx

	public function new(x:Float = 0, y:Float = 0)
	{
		super(x, y); <--- move super method call up here
		loadGraphic(AssetPaths.player__png, true, 16, 16);
		setFacingFlip(FlxObject.LEFT, false, false);
		setFacingFlip(FlxObject.RIGHT, true, false);
		setSize(8, 8);
...

	override function update(elapsed:Float) <-- remove the whole update method
	{
		FlxG.collide(this, walls);
		super.update(elapsed);
	}

Usually, the super method is one of the first things to get called in a class constructor (new) or create() method

2. in PlayState.hx

class PlayState extends FlxState
{
	var player:Player;
	var map:FlxOgmo3Loader;
	var walls:FlxTilemap;
	var map:PlaceEntities; <-- remove this line

	override public function create()
	{
		...
	}

	function placeEntities(entity:EntityData) <--- move outside of the create method
	{
          ...
	}

	override public function update(elapsed:Float)
	{
		super.update(elapsed);
		FlxG.collide(player, walls); <--- add this line here
	}

Aaaaand I think that's everything 🤞
Let me know if you're still having issues.

For future reference. If you right-click on your game running in Chrome, choose "Inspect Element" and look at the console tab, it usually gives more information about an error you may be having.

As you can see from the image above I spotted the issue was one line 15 of Player.hx

Good question. If you're familiar with GitHub (or similar sites) you could upload you r code there. If not you could give me a link to the .zip file from something like Dropbox. I'm not sure if you can upload zips to the forum.