That's pretty neat!

EDIT: Quick look at scripts and I noticed APPatrolScriptInitialize does not nullify the array variables.

You really know how to mak good videos and graphics, Lev! I really liked that about your other mods - and this is no coming short either

Congrats on this release - I see that you decided to make this separate from DLL and I am glad you did too!

@Kyoma
Thanks! 8)

As for the array variables issue, I didn't think it was necessary. Take this quote from the OBSE manual:
"OBSE keeps track of the number of references to each array and destroys the array when no references to it remain. This makes it unnecessary for scripts to worry about destroying arrays explicitly. "

@Anithinks
Automatic Patrols is also packed into Dynamic Leveled Lists, as DLL allows the script to be easily applied to everything in the world. Automatic Patrols is just a detachment for people that want AP for certain creatures, without requiring the entire DLL package.

How does this work? Does it affect all creatures/spawns? Are you able to pick which spawns/creatures/npcs get patrol routes?

True, you don't have to destroy array vars but you do need to inform OBSE that a script no longer needs/uses that array variable. Otherwise the array var will always keep 1 reference and thus continue to exist. Even though no script uses it anymore. And each time the user function is called a new array var is created.

I believe you're correct for things like quest scripts.

However, the scripts you're referring to are User Defined OBSE scripts that are called by the initializing quest, run, and then are closed. All the array variables you stated are local to those user functions, and so their references are destroyed, and consequently, the arrays. Similar to calling a function in C++, you never have to destruct your local int variables and whatnot, and any custom structure has a destructor that cleans up. OBSE has its own array destructor that cleans up the array when the user function closes and there are no more references anymore.

If the array variables were part of a quest script that never went out of scope, then I would have to make the array variables null for them to be destroyed. But I think everything I've done in AP are definitely safe.

Yes and no, Automatic Patrols lets you pick which creatures will go on patrol. Just attach the "APattachmentScript" to the creature/NPC in CS or Tes4edit, and when it spawns it will have a percent chance to go on patrol. And of course, you can set the percent chance in the ini.

If you want this script attachment to be done automatically, you'll have to install Dynamic Leveled Lists instead (linked below).

AP is the "modder's resource" version that doesn't require DLL.

Doh! Yea you're right, I mixed up array vars with string vars there for a moment. Please forget my disturbance. :blush:

8) No worries!
I always appreciate people double checking my work. I'd rather have it right then never be disturbed.. XD

I see... thanks. I just watched the video (was at work earlier), dude - it looks amazing. Your mods have been really impressive! I especially like the loading screens ones.

Back to this though - it is also quite remarkable to think about how much Oblivion needed something like this. I am going to go ahead and give this a go. Thanks for your hard work.

Great idea! This with DLL should make those tedious dungeon crawls much more exciting.

Thanks!

Neat idea! Keep up the bad work :thumbsup: