In this state, the pathing system will switch to move to the player instead. After two seconds have passed, if the player hasn't taken cover, the enemy will enter the Chase state. When the enemy sees the player (currently just a raycast from the enemy to the camera, ignoring FOV or distance for now), it starts a timer. First, the enemy is in its default state (either standing or patrolling). The enemy attacking mechanic is now fully implemented. Most SOMA levels have more dynamic objects in a given major room than these Wolf3D levels have in the entire map.) (Not to mention there aren't so many wall objects that it would be that much of a concern anyway. However, entities of the type StaticProp aren't much more intensive than static objects, and having collision integrated with the wall objects themselves makes creating future levels easier. (Of course, the alternative solution would be to cover all the walls with block boxes, and that would achieve the same result while involving fewer active objects. There's apparently something interesting going on with the physics regarding static entities that let players walk through them when they wouldn't be able to with entities. The reason for this is because apparently at the high movement speeds required for Wolfenstein 3D, if the player is sprinting, they will walk right through anything that isn't a blocking entity. (Another thing that I had to recreate.) I also upgraded the A* pathfinding to allow for diagonal movement.Īnother thing I had to change that I didn't expect to is all the walls on the map have been converted from static objects to entities. In the Path state, the enemy is also intelligent enough to detect when it's standing in front of a door and will open it before walking through. Path is the idle patrol state, where the enemy follows a predefined patrol path. Stand is what it sounds like - the dude is just standing there, waiting for something to happen. (I wonder how many other things I'm going to have to make from-scratch custom versions of before I'm done.)Īnyway, in this video there are two states: Stand and Path. The way I had to do it meant that I had to create a custom state machine implementation as well. Like I said in the previous update, I had to create a custom pathfinding implementation. Here we have the beginning of enemy states.
0 kommentar(er)
