Jump to content


Global Moderator
  • Content Count

  • Joined

  • Last visited

Everything posted by Kelandon

  1. I'm still a little unclear on what you're trying to do, but it sounds like you may need to use change_outdoor_location(). It's likely easy to make the teleportation effect work, too, if you want, but I'm very unsure about what you were trying to do and why it didn't work.
  2. What happened? I might be able to help if you give more details. Did you get an error message or something? Incidentally, you said that you created a disk image with the APFS format, but, per the above posts, APFS is the problem. It needs to be in the older format.
  3. Yeah, I've stayed on 10.14 specifically to finish Homeland.
  4. If you've made a dmg file, open it and that should mount it as if it were another hard disk. Then you can put your scenario's bas file (and the rest of the scripts, if need be) in there, and the editor should be able to edit and save the bas file.
  5. At the beginning of the script, you need to declare variables. Right after your begintownscript, there should be: variables; short choice;
  6. I really hope so. I think that creating the main plot sequence (which I've already done) and filling in absolutely everything in Chapters 1 and 2 will clarify quite a lot for Chapters 3 and 4. There are some special areas — such as the end of Chapter 2 in the capital, and basically all of Chapter 5 — that don't work the same way, but most of Chapter 3 is really the same type of thing as Chapters 1 and 2. So the same notes, the same design process, etc., will work there.
  7. To give you some idea why this all takes forever, my plan for the rest of today was exactly what I said: fix the special spells/abilities, and keep alpha testing. But as I was fixing the special spells/abilities, I realized that some of my early choices about when you learn the special spells/abilities were irrational. They were rewards for very minor quests when there were much more major quests with altogether too modest rewards. So I sat down to document all the side quest rewards and all the places where you learn special spells/abilities (plus all the magic items that are found/earned). This doesn't sound so bad until you realize that, right now, there are 29 side quests that you can complete within Chapters 1 and 2, 16 special spells/abilities that you can learn in Chapters 1 and 2, and 24 magic items that you can obtain in Chapters 1 and 2. Then, once I'd documented the relevant info in spreadsheets, I realized how haphazard choices I'd made so far about these things had been, and I decided to make them more logical and systematic. First, I had to figure out what I want to do (changing the spreadsheets), and then I had to go back into the scenario and implement it. So what seemed like a fairly simple, basic task ended up being a lengthy documenting process that took all day, and I didn't get to any additional alpha testing. But in the end the scenario will benefit because things will be a lot more planned and balanced, and I can go back to alpha testing when I next sit down to work on this. (It looks like the changes to the special spells/abilities worked, thank goodness.) Anyway, with regard to giving the player some indication of how much they've missed before the end of Chapter 2, there will be extensive help/walkthrough information available, so anyone who wants to know can know. Given the way the scenario is structured, it would be sort of intrusive to give the same kind of update before the end of Chapter 2 that you get at the end of Chapter 1. But it is fairly obvious at the end of Chapter 2 that you will not be able to backtrack. There is at least one "finish your other business before proceeding" warnings.
  8. I'm going through my third alpha test of Chapter 1, and it's generally in a good place, but it's making me realize that I really need to sit down and restructure the special skills/abilities that I designed way back at the beginning of the scenario creation process. Now that I know the structure of the main plot in much more detail — all the core quests have been designed at least in principle (and almost all implemented in a basic way), and all the side quests in Chapters 1 and 2 have been fully designed and implemented, save at the very end of Chapter 2 — my initial ideas for how the special spells/abilities would work don't really pan out. In particular, the skill requirements (e.g., you have to have a minimum Mage Spells of [x] before you can cast this spell) are all set wrong. A few spells were made Mage Spells that should have been Priest Spells and vice-versa. And, much more importantly, the skills/spells are being listed in the wrong order. The other two issues are just matter of tweaking my notes and two states in the scenario script, but that last issue requires moving a whole bunch of things around. It will be a mess to fix. But hopefully I can get it done today, finish the last alpha test of Chapter 1, and finally get into the first real alpha test of Chapter 2. (I tried to alpha test Chapter 2 a few weeks ago, but there were so many bugs/missing pieces I uncovered from both Chapter 1 and Chapter 2 that I didn't get very far.) A while back, I worried that I was creating a Nethergate scenario: there's a main quest line, but a lot of the cool stuff is outside the main quests. Now, much farther in, I'm pretty sure of it. There is a ton of content outside the main quest sequence, and if you're not looking for it, you can easily miss it. At the end of each chapter, you get an update on how many of the side quests you've started and completed, and Chapter 2 is structured such that you can backtrack into Chapter 1, so at least people should be aware of whether they're missing a lot of stuff or not. After Chapter 2, though, each chapter is self-contained: in Chapter 3, you can't backtrack into Chapter 2, etc.
  9. This is controversial, but I definitely agree.
  10. Per my investigations this morning, I have determined that I don't like the standard magically locked door mechanic and am going to change it for Homeland. I don't particularly like that the magical door script and the regular door script are two separate scripts, so I'm going to unify them. And, per my usual approach, I'm going to set good defaults but allow customization through memory cells, such that you can set magical lock strength, mechanism difficulty (for picking), and physical strength (for bashing) separately. Some doors will be only physically locked, so you need picking/bashing/a strong Unlock spell. Some doors will be only magically locked, so an Unlock spell is all you need. Some will be both, so you need an Unlock spell plus picking/bashing/a second Unlock spell. And some will be much easier to bash than to pick, or vice-versa. Obviously, in-game dialog boxes will need to give clues about the nature of each door.
  11. I was messing around with magically locked doors this morning, and I discovered that the key call — get_unlock_spell_strength() — is totally undocumented. I don't know if anybody has bothered to work out how it works before, but here's what appears to happen. The strength of an unlock spell appears to be calculated by (Unlock spell level * 2) + (Mage Spells skill / 2) + 5. Weirdly, the Mage Spells value is rounded up, even though BoA normally rounds down. I didn't check whether Magery affects it, but I assume that (as usual) Magery would be calculated as extra levels of Mage Spells. So, for example, a mage with Unlock level 2, Mage Spells 10, has an unlock strength of (2 * 2) + (10 / 5) + 5 = 14. The default magic door script has a double unlocking mechanic, where first you have to cast an Unlock spell that releases the magic and then you have to pick the lock. The lock difficulty is the same for both, which seems sort of unreasonable because the default party starts with a Tool Use of 4, while the minimum unlocking strength for a spell is 10 (and can be attained by increasing Mage Spells once from the default party). Similarly, at high levels, with an Unlock spell of, say, 3, and a Mage Spells of, say, 17, the unlock spell strength would be about 20, which probably far exceeds Tool Use at high levels. The default door script unlocks if the unlock strength is twice the lock difficulty, which means that Unlock 3 + Mage Spells 17 is equivalent to Tool Use 10. Thus, you might be able to get away with replacing a tool user with a mage in some circumstances. Except that, weirdly, the default magic door doesn't unlock this way, so if there are magically locked doors, you still need the tool user.
  12. You can change the starting location just for testing purposes or test with a god party. Or put in calls that you’ll later delete that move the party past the combat.
  13. If you want to be able to see an area in a cut scene, you either need to put a character close enough that the party can see the area, or you need to use set_total_visibility(1). Remember to set it back to 0 when the cut scene is over. As for the south end of your outdoor section, I don't know why you're seeing a blue area, but maybe put in a wall?
  14. If you want help, you really need to copy and paste the actual section of the script, not just something from memory. Also, the command reward_give() takes one short. Anything in the form reward_give(x,5) will generate an error because it has a second number. I don't know why the first version wouldn't work (assuming that the extra spaces are not the problem). You'd need to post more of the script (at a minimum, the entire node).
  15. The way you give an item to the party in dialogue is exactly how you're describing. Post the code if you want it debugged.
  16. I'm not sure what you're trying to do, but yes, you'll have to include some sort of code about SDFs. I also don't understand the "unfortunate thing" at all. If you need help, could you explain further?
  17. Ess-Eschas just helped me with a bug that I was realistically never going to track down by myself, and I figure I might as well let everyone know about it. Evidently, using the set_terrain() call in the outdoors prompts weird behavior when used on the eastern end of the outdoor section, if the party is currently located in the (north-?)western end of the section. The problem manifests for x-coordinates greater than or equal to 37. There are some safe regions with x = 40 and y = an odd number greater than 26, x = 41 or 42 and y = and odd number, and x = 43 and y = and odd number less than 38, among other potential safe areas. But otherwise, using set_terrain() in the outdoors can mess up the first PC. The bug initially manifested when I had a supply cache at (41,46) and was setting it to be a found supply cache if the player had already opened it and was re-entering the outdoor section. While wandering in the northwest corner of the section, I ended up with 141 copies of whatever was in the first PC's fifth inventory slot. Moving the cache to (41,44) changed it to adding pears (item 397) to the first PC's fifth inventory slot. Moving the cache to (41,45) fixed the bug as far as I can tell. Ess-Eschas can explain why this is happening better than I can, but it's one of the weirdest bugs I've ever seen in BoA. It seems to involve memory errors not unlike the old staining technique.
  18. You don't have enough numbers in parentheses. Here's the relevant part of the docs: You need to specify how much of the status and whether to give an update in the text field.
  19. Personality has an extremely limited effect, and not related to this. If you talk to someone with a given personality and encounter a node with the INTRO characteristic, you get text1 through text4. If you then encounter a node with the INTRO characteristic from the same personality (whether the same node/character or, I think, a different one), you get text5 through text 8. That's it.
  20. You need to set the third memory cell to the first node of the character's dialogue. For the second character, Allen, you need to set the third memory cell to 4.
  21. One unexpected thing about alpha testing is that I have to relearn how to play BoA. I don't really remember how to allot skill points and that kind of thing. It's fun, but it's a bit weird, like speaking a foreign language for the first time in many years. As of this test, the party ends up around level 14 at the end of Chapter 1 if you do all the side quests. That's probably not going to change much between now and the beta version. I have a list of about two dozen things that I need to fix in Chapter 1 based on this round of alpha testing. I'm now ready to go into Chapter 2 for the first time. I'm not exactly looking forward to it. Initial alpha testing is usually pretty rough. But the capital awaits.
  • Create New...