shadowedvaca / meandering-muck-2.0

More to come

meandering-muck-2.0's Issues

Allow user to configure screen resolutions and screen mode

Tried to do this for MVP and it was not working as I expected. I documented links and such here.
#5

Break generate maze section into multiple functions?

One thought, break it out by maze element (walls, doors, start/end)

Last time this came back to shared pieces of info, but I have a better idea how to manage variables now, so it might be cleaner...

This is not a must have, but I'd like to have this worked out before I call MVP done.

Maze not populating correctly

Player Can Leave Maze

# The boundary doesn't work
	# It doesn't work on the second level for sure
		# Not sure if it works in the first level
	# Need a plan for stopping the player
		# Can the world boundary be made to work?
		# Can the player position clamping be made to work?
			# A lot of bugs stopped when I pulled this out, I'd rather keep it out

Sound Effects for game

Title Screen

Options Menu

# Make options screen able to configure screen mode and size
	# Maybe allow user to enter a seed for the rng and select wall and door modes?

Background Music for game

Way to show controls

Need some way to communicate controls to the user

Need to be able to go back to main menu and start over

Normal Door Enhancement

Just like on start/end doors, need 3 options

Random - This is how the doors work today (compass and placement is random)
Middle-ish - This one would be Middle w/ a random placement rather than a forced one (compass is determined, placement is random)
Middle - This is that sticky note I have. This would determine where each of it's children's doors go (both compass directions and placement at one end or the other.

Main Menu not displaying correctly

Maze Code Improvements

# Then improve maze code (see notes there)

Middle-ish mode doesn't work

New Level Player Issues

# I think I need to figure out turning off player input and colission between levels
	# If you keep pressing after hiting the exit, you can accidently leave the map...
	# Also, you can sometimes slide out of the start into walls
	# Also, you can trigger the exit multiple times

End Tile Hit Box Not Working

Slime can enter hit box and maze does not end when he does

Improve inner game communication

# Learn to use signals to push info around better
	# see notes on Maze for what I was working on
	# https://kidscancode.org/godot_recipes/4.x/basics/node_communication/#signal-example

Slime Trail (Optional?)

Timer per level

start / end logic is broken

Look at log files in folder: 2024-02-21T220202

Overhaul Graphics

M3 is working on this potentially.

setters / getters in maze data

Reading about setters and getters online, there was an example around have a variable that calculated upon retrival. It sounds like I could refactor bits of the maze data code and use this. For example, corridors and open are not their own variables holding onto data, they are calculations of the outer wall only. This issue is to play around with this to see if it reduces code in the maze data structure (and reduce processing maybe cause I am no longer storing un-needed values... I think this would apply to all the calcs down from this. If I overdo this however, it might mean calculating one value means calculating several values and using this one value many times would not be process efficient.

https://www.reddit.com/r/godot/comments/164z4at/setters_and_getters/

Need a level counter

Show a level counter on the screen to communicate to the user what level they are on.

Start / End Door Spawn Options

Need to be Random, Middle-ish, and Middle like the wall types

Need a list of the options, and the one picked will apply to all things (walls, doors, start/end)

Random = The start/end can spawn anywhere on the wall that was skipped during door choice (like today, only not random)
Middle-ish = The start/end can spawn -/+50% (respectively) from the wall they surround
Middle = Today's logic, right on the wall they surround

Maze Generation Time

I think when mazes get more than 200x200 in size, they might take too long to generate. Do some testing to figure out if this is actually a problem.

Static / Middle Maze Type generating impossible maze

Look in log folder C:\Users\mike\AppData\Roaming\Godot\app_userdata\Meandering Muck 2.0\sessions\2024-02-23T221041

Troubleshooting: Drop a json object that describes the maze creation process

This would be a useful object to write up with each maze generated. Store them in a temp folder and somehow keep that folder clean (save mazes from the previous 24 hours maybe...)

Need to read more on how temp log files work in godot.

Camera setup not working