FirePaladin said:

---

Gonna investigate right now!

Edit: You made a campaign with maps?... (I didn't play too much H4, so I don't really know how that goes and how you made two maps in a campaign etc.)

Edit 2: Weird... I don't see it either... Specifics? Players, towns, etc.?

Edit 3: Now I see it, after adding towns and players to them. It's probably because your map is unplayable if it has no towns or players.

---

FirePaladin said:

---

Nice. There was also a guy who made The Hobbit into a H3 map recently. Anyway, tell me the results after putting a win condition. You can also just make a place to test it first, to see if that's it, the problem.

---

FirePaladin said:

---

Good luck! Well-made story-driven maps and campaigns are awesome! Gonna check on Dragonlace Chronicles, see what it is about.

I'm also creating a story map, for H3, but its story is not extremely serious (even tho the events are serious) and does contain jokes, silly quests and other stuff, since I'm making it especially to play it together with my family in allied hotseat. It should be playable with friends too, since it's not "that" silly to the point it's just too much.

---

FirePaladin said:

---

I do love fantasies!

H3 does lack scripting, that's true (and I sometimes find it annoying, but I manage to do it somehow, like making it possible to destroy rocks blocking passages, etc.). I'll try to make the map as balanced and interesting as possible (including gameplay), by testing it, so I'll release it after a while, even though almost the entire map itself without some quests and events is already finished (80% surface 100% underground done).

There's a script to make the purchase of a Megadragon possible, if you're interested. I can send you a link to it. Here's the link: [url=https://www.mediafire.com/file/9y7gdbk0zd58im7/wb_megadragon_dwelling_wow.h4c/file]Megadragon Dwelling[/url]

Edit: You don't especially love SpAzZ MaTiCuS and his mad quest to rule the world?! That's heresy!

---

iliveinabox05 said:

---

Edit. The clear win/loss condition scripts are just meant to clear any text associated with the win / loss conditions when viewing these in the menu during a game. Some of those scripts may be bugged, but I don't remember which ones have issues.

---

iliveinabox05 said:

---

H4 scripting has variables you can set and use to do what you want.

Once you give the quest, set a numeric variable to be the current day. then you'll have a timed event that checks everyday to see if the current day is equal to your saved numeric variable + 20. If the day is equal to you saved day + 20, and the player hasn't accomplished what they were supposed to, then you can display a message, followed by the "lose" script, which will end the game.

Here is a little psuedo scripting to help you out:

--------------------------------------------

Timed Event for initializing variables, start Day 1 and only run once-
set boolean variable isQuestActivated = false
set boolean variable isQuestComplete = false
set numeric variable startQuestDay = -1
remove script

Timed Event for quest, start Day 1 -
if ( isQuestComplete )
{
   remove script
}

if ( isQuestActivated )
{
   if ( current day = ( startQuestDay + 20 ) AND NOT isQuestComplete)
   {
       Display "You lose"
       lose
   }
}

Placed Event (or other type of event) to start the quest -
set numeric variable startQuestDay to current day
set boolean variable isQuestActivated to true
remove script

Placed event (or other type of event) when quest is completed -
isQuestComplete = true
//These next two aren't necessary, but I like to set all variables to a correct state
set boolean variable isQuestActivated to false
set numeric variable startQuestDay to -1
remove script

--------------------------------------------

I may have missed some things, but that is the gist of what you'll want to do.

Let me know if you have any other questions.

Edit. The clear win/loss condition scripts are just meant to clear any text associated with the win / loss conditions when viewing these in the menu during a game. Some of those scripts may be bugged, but I don't remember which ones have issues.

---

Karmakeld said:

---

iliveinabox05 said:

---

Edit. The clear win/loss condition scripts are just meant to clear any text associated with the win / loss conditions when viewing these in the menu during a game. Some of those scripts may be bugged, but I don't remember which ones have issues.

---

I believe you can use the 'set new loss condition' to change the loss condition. I used multiple win/loss conditions in some of the maps in my campaign so I could go and check to be 100% certain. Also nice to see a fellow Dane in here
As for the Mega Dragon Dwelling you may want to look in my object package, as McIric and I are currently working on making a unique Mega Dragon Dwelling adventure object, which isn't just a preset quest hut but an actual dwelling for this crrature.

---

iliveinabox05 said:

---

Yes, I listed out the different events you should create to do what you want to do.

Why can you not set a boolean variable in a sequence? You just click "new" under scripts for the event and then select "set boolean (true/false) variable", enter the name of the variable (isQuestActivated), and then set the value (true). Since you want the first day to activate your quest, you'll set the "isQuestActivated" variable to true in your initialization timed event.

You'll do the same thing for your "startQuestDay" variable, except you'll want to pick "Set numeric variable" from the list of scripts. When setting the value, you will scroll up to the top where you should see "current day" and use that to set your variable.

That was all for your first timed event.

For the second timed event, you should set it to start on the second day so you don't have to worry about correctly naming your timed events so that they execute in the correct order (they go alphabetically if I remember correctly).

To get the following into a script:

if ( isQuestActivated )

Do the following:

Under the script tab of your event, click "new", then select "conditional action". Next, click "edit" to the right of the "if" block, and then select "variable". If you have already created the initialization timed event, then you will be able to select any boolean variables you have created from the drop down menu here. Select "isQuestActivated". Now you can go into the true branch and add the things I mentioned in my previous post.

You can ignore the other events I wrote about (the ones saying "placed event or other type") since you are starting things on day 1. You should only need the two timed events to do what you want.

You should be able to use these tips to do the rest of the scripting I wrote out in my previous post

---