Coding general AI.

As promised I've spent most of my time this week
on coding basic gameplay.

[text above each agent displays debug info]

I started out having separate state machines for AI decision making and actions/animation.

Sometimes AI control calls for very rapid switches of states which would also disrupt the animations. Causing them to stutter or jump.

But by setting up Animations to only switch after a short delay I eliminated the problem you get with having AI and actions in the same state.

If a call to switch animation occurs, but rapidly switches back (like stopping for an instant when walking) the switch is ignored.

So I refactored them in to a single finite state system with inheritance helping to structure things like animation and path finding.

[Blocked in!]

AI is pretty basic. They just try to get towards you avoiding squares they've already visited. But it works surprisingly well.

It's easy to get blocked in by the enemy, but you can use the nature of the grid to avoid fighting too many enemies at once.

I don't know how well this system will work once I introduce the other party members. That's going to take some serious testing to see if it's fun or not.

[Big and small agents interact seamlessly]

I added the ability to rotate the camera 90 degrees, this keeps the WASD movement system working well, but allows you to see behind things or get a better view.

Controls are going to be all keyboard based, with a radial menu handling things like item use, switching control of party members, resting, using special abilities etc...

There will probably be a shortcut bar too, so you can map some short cuts to the number keys.

[Water shader]

I did spend some time this week mucking about with shaders again, but there seems to be some kind of bug when rotating the camera. Sigh.

You know, it's funny that shader isn't in the spellchecker dictionary...

You can check out the video that goes with this entry HERE.

Comments

Advice needed on tilesets...

I need some advice on which is the best way to handle building the dungeon. Right now I'm using prefabs for my dungeon, they have a north south east and west section for each "room": The basic tileset. This has several advantages, and also several disadvantages. Firstly I can have curved rooms, I can have tunnels and other interesting shapes. The tilesets can look quite nice with a little work. On the other hand I can't easily get the navigation data before building the map and once the map has been built I can't make changes to the layout, like having active pit traps or believable secret doors. Although the rooms are interesting, they are quite repetitive, and it takes a lot of effort to make even a few different variations. Also rooms are constrained to one size. A newer version of the tileset with a lot of variant parts for making more interesting rooms. To create a tile set is a real headache too. Planning how to lay out the UVs, trying to cra...

Upstairs / Downstairs.

I've decided to make my prefabs multilevel. Later this should allow me to add pit traps and other great stuff. It also makes it easier to line up stairs so that you can exit them on the same co-ordinates where you entered them. The prefab editor is pretty much finished, it just needs some code for loading up prefabs from a saved dictionary, so that they can be checked or edited. The entries will need to be forwards compatible, so I'll be loading each tile and then translating the indexes to a new array, that way if I add extra indexes or extra info (like traps or puzzles) I'll be able to update existing prefabs to work with the new standard. Click for a video.

Video Diary 8

Things are moving along well, there's been a lot of progress on the action manager side of things. Actions have finally moved to the UI, so you can initiate actions by clicking the appropriate button. I've set up some dummy actions to show what happens visually when actions are taken, but the actual dice rolls and such are yet to be integrated. The UI objects are also being added, though some are non functional or empty at the moment. Click on the image to see this week's development video. Every time I add something big I also add about a dozen small things. Like the selection box visualization. Previously this was using render.drawline, and old fashioned Blender function which can be impossible to see at certain resolutions, or at certain frequencies. I replaced it with a function that adds planes of the right size and scale in the right location. I also made all characters a little bigger. I still need to do some work with vectors and final target locations t...

Pickledtezcat Game Devblog

Search This Blog