Add new comment

I'm much in the same boat. Things will get moving again but I'm just not sure of exactly when.

Flick is a very useful addition to the way DS2 as it makes more things possible and mostly in an easier fashion than what was possible in DS1 but I agree that sometimes the game won't process parts or all of the flick. It's doubly frustrating when 90% of the time it will but then 10% of the time the flick fails. It's even worse when you invest many hours in incorporating said flick into a mod, like I did with the mini-boss battle themes in the Legendary Mod, only to have to abandon the whole thing because of the fickle nature of flick.

I've come to the conclusion it has to be because of some world event priority thing that causes the game code to ignore the flick command because something else is being prioritized. If there's an error in the flick then it won't run at all and often the editor will provide an error message when parsing the flick on startup. However when the flick is used elsewhere in a map with 100% success rate but in certain positions may or may not work randomly, then its hair pulling out time and I haven't much hair left to pull out.

I've also noticed that when placing triggers and such, the game sometimes won't process a trigger if it overlays another trigger. Moving triggers to avoid overlapping other triggers if possible will often solve such glitches. Other times it just won't work and so often I've had to abandon mapping work because of such errant behaviour.

As KillerGremal remarked it's really not amusing at all.