Lilith

I think that's one of those things that just doesn't exist in BoA.

You don't technically have to kill any of the dragons to loot their treasure; you can just haste and run away.

I just might have a little something in the works as well.

With 5 luck, attacks that would otherwise kill you will fail more than half the time; probably close to 70%, I'd guess, and maybe even more. Get 10 luck and the chance starts looking more like 90%.

I've always felt that there were two main obstacles to collaborative efforts in BoE:

 

1) If one person gives up on the scenario, the whole thing tends to grind to a halt.

 

2) BoE wasn't modular enough. Towns could be imported between different copies of a scenario, sure, but outdoor sections, items, monsters and terrains couldn't.

 

Now, BoA goes some way toward solving problem 2, since all of those things except outdoor sections are now just scripts and so can easily be transferred from one person's working copy of the scenario to another's. The ease of one person handing most of his work over to the others upon giving up may also help with problem 1, but it still means that each member of the team has to potentially be ready to complete the scenario on their own if the others pull out. And if they're prepared to do that, then what's the point of collaborating?

I never spend skill points on health. If dying is a problem for you, spend the skill points you save on HP on Luck instead; you won't regret it. In fact, starting all your characters with 5 points or so of Luck isn't such a bad idea; your party may feel underpowered at first, but it hardly matters when they're virtually invincible.

Have you checked the clipboard before pasting to make sure it actually contains the graphic? Sometimes opening a program in Classic mode (like ResEdit) can erase the clipboard contents.

If you run, you have to cast Armageddon at the exit of the cave to prevent the dragons from chasing you down. If you refuse to be sacrificed, you have to flee the castle and then find your way out of a cave you get dumped into. Either way, the scenario continues in pretty much the same way afterwards.

The preferences file you want is the Avernum Prefs file, the one you probably had to delete the last 2 times your editor was disabled, thus causing you to unregister your copy. Delete your prefs again, get a new code, reregister, set your preferences as you like them and then back up the preferences. Next time your sister messes with Avernum 3, replace the preferences file with the backup you made. If she destroys the backup, you can probably make a case for justifiable homicide.

Sounds like someone's been messing with your saved game in the editor.

Back up your preferences file, preferably to a CD.

Actually, I think I needed to use the stone at all 4 gates. You only need one stone, though, so you can sell any others you find to the priest in Marralis.

 

And to appease the herbalist, all you need to do is search the place thoroughly, then go back and tell her you found nothing there. You'll still get a reward for your trouble.

He wasn't talking about your post, he was actually describing the program itself as "bloated". It's a fairly common term among programmers to refer to a program with more features than anyone will ever want, and it's a fair bit more constructive than "that program has no use".

This has happened before in BoE scenarios. End the scenario normally and call it a win.

I believe that Kel was pointing out that you invited opinions, and that UA (Shining Lightbulb) gave you his, and that you went snarky at him for it.

Think of scenarios as having the same canonicity as fanfiction; that is to say, none at all if you don't want them to have, and you can even ignore established canon if you don't mind annoying some people.

Sounds like you forgot to define choice as a variable.

If you edit corescendata, the changes you make will only show up on your copy of BoA, not anyone else's -- which means that if other people play your scenario it won't work properly. This is bad. Don't do it.

It sounds as if that's what Jeff was planning to do when he first heard about the problem, and now people are trying to harangue him into finding increasingly perfect solutions. Honestly, I'm starting to see why he was reluctant to fix BoE. Even if we have good reasons for it, we can ask for a lot. The Blades community must be worse than Cordelia sometimes.

Note: a portal that takes them to a TOWN far away.

 

Basically, it's used so the party ends up in the correct place when they step *out* of town. Remember, although an outdoor location can be associated with a town, the town isn't specifically associated with that outdoor location (if that makes sense). To put it another way, BoA doesn't intrinsically know where a town is supposed to be located, and you have to tell it.

The "*2 -1" bug (as in the example discussed in this thread) makes it sound a lot like BoA is counting a carriage return immediately followed by a line feed (the standard format on Windows) as two line breaks when it should count as one.

As Alec once pointed out, if the number of times the average player reloads is anything to go by, Exile is littered with the bodies of would-be heroes.

The consensus is that it doesn't work in the current version.

The time you take to make a scenario will obviously depend on how large it is; it could be anything from a couple of weeks to a year or more. For a medium to large-sized scenario, expect to be working on it at least an hour a day for a few months.

 

The numbers you put in for the outdoor dimensions are the number of outdoor SECTIONS, not spaces. An outdoor section is pretty big; err on the side of a smaller outdoors rather than a larger one. A 2x2 outdoors is probably more than enough for a small to medium-sized scenario, as long as you make it compact. Even a largish scenario shouldn't need much more than 5x5, and you probably won't end up using all of that. You can always make a large outdoors and wall the bits you don't use off with mountains, of course.

Scripts on items won't carry over between scenarios even if there's an identical item with an identical script in another scenario.