HOME | DD

Description
DAY 1: [link]
DAY 2: [link]

DAY 3: Think I've worked out all the kinks in the ground/edge/slope detection.

On the priority list now is a sliding behavior for sufficiently steep slopes, and curbing the speed when climbing up. Still doing AI research - trying to work out the best method. Preprogramming routes and nodes would work, but requires editing if you make any major changes, and the goal right now is to make the engine flexible enough that I don' have to worry about a lot of programming when I'm building the game itself... It's looking like I might write a script to pre-calculate the nodes and major routes, to hopefully minimize necessary in-game calculations.

Anyway, in case anyone is interested, almost all of the script right now is handled by an abstract Sprite class, since all Sprites will use the same ground detection methods. How they behave in response to those detections will be determined either by an AI or by player input, and those behaviors will be defined in the concrete subclasses that extend AbstractSprite.

DAY 6: [link]

Description
DAY 1: [link]
DAY 2: [link]

DAY 3: Think I've worked out all the kinks in the ground/edge/slope detection.

On the priority list now is a sliding behavior for sufficiently steep slopes, and curbing the speed when climbing up. Still doing AI research - trying to work out the best method. Preprogramming routes and nodes would work, but requires editing if you make any major changes, and the goal right now is to make the engine flexible enough that I don' have to worry about a lot of programming when I'm building the game itself... It's looking like I might write a script to pre-calculate the nodes and major routes, to hopefully minimize necessary in-game calculations.

Anyway, in case anyone is interested, almost all of the script right now is handled by an abstract Sprite class, since all Sprites will use the same ground detection methods. How they behave in response to those detections will be determined either by an AI or by player input, and those behaviors will be defined in the concrete subclasses that extend AbstractSprite.

DAY 6: [link]