3 years ago

Testing different pathfinding options+ Some advice on Plugin use on #Unity

Initially I tried to use Unity's own system, but that didn't work out with a grid-based game.
Eventually I went with something based on A* and Code Monkey's grid system (...)


Initially I tried using h8man's navmeshPlus so I could use Unity's system. Seems good for non-grid based games, but my agent's didnt like it very much:

Not to mention all my entities are controlled like player characters, with actual input, so I need more "indirect" control from the pathfinding.

So I went for the good old A* algorythm using Code Monkey's tutorial as a base

I wrote a new code based on the original and more suited to my own needs. It's not usually a good idea to just jam code made for another game into yours without properly preparing it.

Now I actually want to make this grid system (which I named LogicGrid in mine) to work **WITH** Unity's preexisting grid system so I won't have 2 different systems competing with each other.

On plugins:
be careful with plugins. They're great to get things started, but it's very easy for Unity projects to become bloated masses of plugins that can barely run and become an absolute nightmare to mantain.
If you use a plugin, be very careful to only use it as needed and remove it from the project if it's not required anymore.

Also, and that is really important: AVOID DIRECTLY MODIFYING PLUGIN CLASSES. It's going to absolutely destroy your game if you ever want to update said plugin.
If you **Need** to change the plugin, prefer extending it's classes and working on top of them.

(that is not a rule, though. Nothing is. There will be situations where that is indeed your best option)

But if you reach a point where you're fighting against the plugin that was supposed to help you in the first place, maybe it's time to look for another solution.

Now I need to actually wire this pathfinding into some AI.
I won't need anything super complex so I'm thinking a basic state machine should suffice

Didn't intent to write out another #devlog right now but I guess I started ranting. oops.

1
1
Game Dev Show & Tell
UNITY 3D / 2D Show off 🔥
7


0 comments

Loading...

Next up

A cool thing about having all your entities work the same is that you can easily make anything playable and everything functions nicely. Gonna make a longer post about it later. I might also soon change the art to something original

Starting a devlog: How to keep your Unity project from crumbling upon itself (from some nerd who's been using Unity for over a decade and one really hard burnout) #unity3d #gamedev #fangame

I wanted to make a pallete-swap system to replicate what the #NES does, so I made a simple shader on shaderGraph for that. It samples each color channel and replaces it with the color defined on the material

NES link looks good in blue! #Unity #Gamedev

Happy #WIPWednesday! Are you working on a game? Making some art? Practicing a song? Something else? Tell us in the comments!

So...I'm trying to recreate something of an "Nintendo 64 as seen through CRT" effect in Unity #unity #retro #N64 #indieGame #indieDev

The Knightling launches on August 28! Wishlist it now so you don't miss out: https://bit.ly/KnightlingSteam

To celebrate the game's impending release, we've added The Knightling Pack and The Knightling Community Pack back to the Shop!

Generic component system is done... kinda. Activation is messy. You currently need to specifically setup the projectile separate from the equipment data. If I don't fix it it'll be a trap for myself later. Works fine though. No specific code required

After implementing some of the structure I learned on #UE4 into #unity and some input juggling I've "accidentally" made multiplayer Every character has a "characterController" and these can have a separate input source. Every character should be playable

Happy #WIPWednesday! Are you working on a game? Making some art? Practicing a song? Something else? Tell us in the comments!

art comission.