Re: PathsMaker
Posted: Mon Oct 03, 2022 2:34 pm
I keep prior version.
- Fix place duplicate nodes in some cases.
- Add more options.
Updated in first post: viewtopic.php?f=5&t=15041
UT99.org | Unreal Tournament Community
PathsMaker
Page 3 of 3
Re: PathsMaker
Posted: Wed Oct 05, 2022 12:22 pm
Re: PathsMaker
Posted: Wed Oct 05, 2022 3:54 pm
I guess this wont work, but it will be super to have it as a mutator that checks the map before it starts and add if its missing.
Re: PathsMaker
Posted: Wed Oct 05, 2022 4:14 pm
Ah. You mean add paths in runtime. It is not possible. Editor engine not loaded/not exists on server.
Without it even if you able spawn PathNodes in runtime (and you don't since they static actors) they just bunch of actors, without connection between them.
Maybe in future build it can be possible, but i doubt about it. It can take very long time for real usage, for do it each time on map load.
Also there must be turn off runaway limit, which lead to server hangs if something going wrong.
Re: PathsMaker
Posted: Wed Oct 05, 2022 4:15 pm
@Hitman
#1 I'm not sure how much can you spawn PathNodes in run-time - perhaps newer patches can do that.
#2 Next: Does newer patches include run-time support for generating ReachSpecs out of Editor ? Without ReachSpecs (aka Paths) they are useless except for newer patches when it comes to Relics support....
#3 If you can deploy PathNodes before to see engine creating NavigationChain (469 add-on...) - if Engine does this before InitGame then... you will need extra hackish stuff for this task. As far as I recall Relics are working based on navigation chain and embedded PathNodes in said chain - not outside it...
@Buggie
Now we have indeed options. Except two junks, DM-MaleVolence went pretty interesting - it looks like Builder is giving some ideas toward placement.
The rest of my questions are maybe less relevant - I see that 469b cannot compile the code with those constants saying that array is too long or such, 436 does other error and then I adapted what I wanted in a more simple format generating builder in a 60.6 kb package, compiled by 440 without warnings or errors and out of BotPack.
Greetings for these recent versions.
#1 I'm not sure how much can you spawn PathNodes in run-time - perhaps newer patches can do that.
#2 Next: Does newer patches include run-time support for generating ReachSpecs out of Editor ? Without ReachSpecs (aka Paths) they are useless except for newer patches when it comes to Relics support....
#3 If you can deploy PathNodes before to see engine creating NavigationChain (469 add-on...) - if Engine does this before InitGame then... you will need extra hackish stuff for this task. As far as I recall Relics are working based on navigation chain and embedded PathNodes in said chain - not outside it...
Code: Select all
function PostBeginPlay()
{
local NavigationPoint NP;
if (Initialized)
return;
Initialized = True;
// Calculate number of navigation points.
for (NP = Level.NavigationPointList; NP != None; NP = NP.NextNavigationPoint)
{
if (NP.IsA('PathNode'))
NumPoints++;
}
SpawnRelic(0);
SetTimer(5.0, True);
}
Now we have indeed options. Except two junks, DM-MaleVolence went pretty interesting - it looks like Builder is giving some ideas toward placement.
The rest of my questions are maybe less relevant - I see that 469b cannot compile the code with those constants saying that array is too long or such, 436 does other error and then I adapted what I wanted in a more simple format generating builder in a 60.6 kb package, compiled by 440 without warnings or errors and out of BotPack.
Greetings for these recent versions.
Re: PathsMaker
Posted: Wed Oct 05, 2022 8:34 pm
ok thx for the reply 
Re: PathsMaker
Posted: Fri Oct 07, 2022 6:47 am
hows this work for CTF Games? does it insert alternate paths or not that complex?
Re: PathsMaker
Posted: Fri Oct 07, 2022 9:47 am
Same as for any type of game. Nothing specific to CTF. Place only PathNodes.
For CTF can take in account drection between flags for make traveling adjusted to it.
AlternatePaths not placed. This work impossible without human brain and understanding how map work, which ways possible, which not. Which goos for return only, which good for both ways and so on.
Wrong place Alternate path can make bots dizzy, make not necessary travels or been trapped somewhere.
For example if bot goes with your flag to dead end and return back you need only setup ambush on return patch.
For CTF can take in account drection between flags for make traveling adjusted to it.
AlternatePaths not placed. This work impossible without human brain and understanding how map work, which ways possible, which not. Which goos for return only, which good for both ways and so on.
Wrong place Alternate path can make bots dizzy, make not necessary travels or been trapped somewhere.
For example if bot goes with your flag to dead end and return back you need only setup ambush on return patch.
Re: PathsMaker
Posted: Sat Apr 06, 2024 12:11 am