next »

[atsiitech]

Hello ,

As I'm prototyping a 2D RPG game I'm also writing what I discover - in tutorial form. I'd appreciate any feedback. My approach with the tutorials is Keep It Simple. Start simple, add fluff later, etc.

Part 1: Grid movement

Part 2: Camera control

Part 3: Lighting the map

Part 4: Enemy/NPC AI (moving)

I'll update this post when I add more.

[eyeliner]

Good jog, dude. Keep'em coming!

[tsamf]

Great tutorials, they cleared up more than one aspect of unity that I was unsure about .

[atsiitech]

Hey, thanks a lot for checking them out!

Next up is some very simple AI and how to call it from other scripts. Also some adjustments to the player movement code. Soonish.

[atsiitech]

Part 4 has now been added. Let me know if it looks too mush and not understandable.

[tsamf]

Not a bad tutorial at all~ but there are a few things I noticed

An interface isn't what allows your other scripts to call methods in your enemy class. You have a public access modifier on the ExecuteAI() method which allows other scripts to access it. The intended purpose of an interface is to define attributes that a class must have to inherit said interface.

For example: if all of your enemies were going to have health you could define a health property in your interface for inheriting classes to define, ensuring that all enemies have a health bar.

The second thing is that you are putting your enemy controller in the player controller. This causes a dependency between the two when they should be modular and separate objects. For example, maybe you have a level with no enemies but you have a player. When you drag your player object into the scene with your player controller script attached, it's going to have all of that unused enemy controller code attached too. The way you've coded this may cause an issue. This design choice also makes your code less clean and will be harder for others to look at and debug through.

I hope this helps!

[analaura]

so gggood jogos de cozinhar

[atsiitech]

@tsamf

Thanks for the tips. The use of the interface was a bit of a brain fart, I fear. I will revise the code and make it better and by your suggestions.

@analaura
Thanks!