Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
I'm curious why?
Plus, you'd have to have a custom model for every different brick
1x1f,1x2f,1x3f,1x4f,1x8f etc
Code: [Select]function Armor::onAdd(%this,%obj) {
%data = %obj.getDatablock();
}
As in the player's location (AI's destination) is constantly shifting. Unless the player is stupid and stays in one spot, waiting to die.
why cant people just buy the original consoles and not adhere to the whole "le retro gamer REVOLUTION" thing?
Especially because Zack0Wack0 and I are on the authors list!
Yeah, I am realizing now that I need some sort of dynamic pathfinding system for SCP-096.
might as well just play pyro
go into console and do "mouse1 forward mouse1 fire"
or whatever the code is and go hardcore w+m1
To add a custom train to the mod (must be a bot vehicle) package:Code: [Select]Replace "[DATABLOCKNAME]" with the name of your train's datablock. For the rest of the options:function [DATABLOCKNAME]::onAdd(%this,%obj)
{
parent::onAdd(%this,%obj);
PrimeTrainPhysics(%obj,[ENABLEENGINE],[DRAG],[ENGINEPOWER],[ENGINEMAX],[BRAKES],[STARTSOUND],[RUNSOUND],[STOPSOUND],[IDLESOUND],[HORNSOUND]);
}
- ENABLEENGINE determines whether or not the train has an engine that can be started/stopped via chat commands or keybinds.
- DRAG determines the slowdown force that acts on the train when it is coming to a stop.
- ENGINEPOWER determines how hard the train is being pushed forward, and plays a part in determining how fast it gets to full speed.
- ENGINEMAX determines how fast the engine is capable of going. Note that this is relitive to the max speed defined in your bot vehicle's datablock.
- BRAKES determines whether or not your train has brakes usable via keybind or chat commands.
- STARTSOUND, RUNSOUND and STOPSOUND, IDLESOUND and HORNSOUND are the sound datablocks that the train uses. Put "0" to not have sound.
That would involve object detection - I guess, provided that the bot knew it's end coords, it could do a raycast for objects in front of it, scheduled every second or so. When it does encounter an object, it performs a sweeping raycast finding the nearest possible "exit"; distance greater than the hypotenuse of the triangle it is searching from (i.e. player is looking at something, distance from player to object is leg of triangle; distance from player to object as the angle of the raycast changes is the hypotenuse). It would turn to this direction, pass the other object, and continue moving towards its destination.
This is the most basic of basic pathfinding methods, but it should work for simple structures. I'm sure there's another non-node type that could be implemented with enough time and effort, but not by me. It'd be great if it could map out its route before hand, using the above for unexpected object encounters (i.e. a player).
