Objective Making

[sparhawk]

We wont implement timing, because it doesn't add anything to the gameplay itself. If anybody thinks he wants to add it on his own, no problem, but for now we have more important things to code than features that don't really do much.

[Fingernail]

It's the easiest thing to do in the world with the scripting language anyhow. You could make it enable an automatically failing objective after a certain time...simple solution.

[Ishtvan]

That's true, it is very easy to add this in scripting.

 

There's a scriptfunction like sys.waitTime( time in seconds ), so you just run that with a fail mission afterwards and you're set.

 

Or if you want to get more fancy, you can do periodic checks on whether an AI is within a certain location, if your mission goal is to pickpocket or kidnap someone before they get on a boat and sail off or something like that.

[Domarius]

The ConVict system that we should implement will have this feature so that FM authours can do it if they want. The ConVict system in T2 did, so ours should too.

[obscurus]

While I am not keen on time limited missions, I do like the idea of Day/Night cycles, where, if say you start a mission at midnight, you have 5 - 6 hours before dawn, then things get more difficult as the shadows get brighter and fewer. But not necessarily impossible. Actually, I wouldn't mind a daylight mission, provided you did have a few shadowy sections (say you start outside a cathedral, then you end up in some dank catacombs, or like the cragscleft mine mission in T1, where it is day outside, but dark in the mines...