Newtfeet

I don't think this can be done in a general sense; there is no call to determine if a beam is on a specific space.

BASE 1.0a2 is now available. There's a download link in my first post. I need input, people! (Sorry about the double post.)

Quote: Originally written by Frobozz: I don't have anything against Mac users (I even had one once). However, I like to see code written to be as portable as possible. Why? Because it is annoying to have to change to another computer whenever you want to run a particular program. This code is portable. The only problem is I need the professional version of REALbasic in order to build a Windows version. And that costs around $400, last I checked. Quote: Originally written by Frobozz: It would be far more useful than you would believe. I've programmed three of the languages you mentioned ( VB, C++, Java ) and others you have not mentioned. I doubt it would take long to port. It might not, but it didn't take long to write either (10 days, more or less). If you want to make a VB version, tell me once I get a finial version. Quote: Originally written by Frobozz: Oh and StuffIt is useless because the vast majority of people cannot use it. And "the vast majority of people" aren't going to be using this anyway. In fact, almost every Mac out there has StuffIt Expander. Quote: Originally written by Frobozz: And I don't think you should pay for the program to make them. You don't have to. DropStuff is shareware; I haven't registered it and it hasn't expired yet. I don't think it will.

From the editor docs: Quote: te_beam_hit_type (Defaults to 0) - How the terrain reacts when struck with a beam. If left at 0, ordinary behavior: if the terrain can be seen and walked through, the beam passes through. Otherwise, it is blocked. If set to 1, the beam always passes through. If 3, the terrain can be crumbled by a beam (though it won’t be unless te_crumble_type is set to something other than 0). This leads me to assume that a value of 2 will cause the beam to always be blocked. Is that correct? I'm too lazy to test it out.

Quote: Originally written by wizardr6: Or haven't downloaded it. Of course. I always forget that option! Quote: Originally written by wizardr6: I use REALbasic as well. I'm planning to write a dialogue script editor, in fact, but it might be too ambitious for me. I know exactly what you mean. I get all these cool ideas, but they all hit the dust pretty quickly. I've never finished a program. In fact, I was hoping to add a dialogue editor in BASE 1.5 or 2.0. We'll see...

Quote: Originally written by wizardr6: What is it written in? I'll assume you have Windows or haven't looked at the about window. BASE is written in REALbasic. I've been working on the custom terrain editor. I have some of the most general stuff implemented, and as soon as I get the General tab finished I'll release 1.0a2. I just have the crumble/beam and the special property areas left. I've also added a little note in the comments when you save a floor or terrain that tells how to use the floor/terrain in a scenario. Hopefully that will help the target audience (newbies).

In the event that I would write a scenario, I'd use TextEdit to keep track of states, dialog nodes and SDFs.

Quote: Originally written by Frobozz: Is it just me or has everything on this forum slowly becoming more Macintosh than Windows. I, for one, am glad that somewhere there is a place where Macs get higher priority. It wouldn't be impossible for me to make a Windows version; just expensive. Quote: Originally written by Frobozz: I downloaded it hoping the source was included. No such luck. Well at least this time the file wasn't big and wasn't in that useless StuffIt format. Yeah; this isn't open source. It might be when I get bored and give up . Anyway, the source might not be useful; this isn't written in VB, C++, Java or Python. And what do you mean, "useless StuffIt format"? Quote: Originally written by Snuff ling kin: I don't need some special editor to be able to code. Not many people do. Quote: Originally written by Snuff ling kin: It could be good for Script Newbies to get to learn the system, though. That's the entire point. Anyway, what I plan on isn't even a text editor; you would see a list of functions, choose one and drag it into the code. Then you can set the properties. No code involved. Unless, of course, you want to. Thinking on Tentacle Monster's idea: I can see adding multiple options to the special property menu and adding a node to the output file, but there are a couple of design points that prevent me: It would be massively harder to get this to open files if I have to parse a script. I can easily imagine someone wanting to do more than one thing; it could get annoying for a newbie. I don't like doing things halfway. Putting this in when I plan to make a better version later seems like wasted time to me. Several other reasons I can't think of now. Anyway, has anyone tested these files with BoA yet?

Quote: Originally written by Tentacle Monster: A bit bare-bones right now (obviously), but I like the set-up. It does, however, assume that the player knows some things about the terrains they're dealing with before even opening it- why not make smaller captions or a "help" pop-up? Most of the controls have tooltips; just move the mouse over an option and wait. I also want to add a visual picker for graphics; is that what you meant? Quote: Originally written by Tentacle Monster: Perhaps you could make a state-compiler where you have a selected group of "options" (ie. Display Message, Display Small Message, Set Flag, etc.), the designer chooses which he/she(/it?) wishes to add to the list of actions performed in the state, at which point it would be compiled into one handy state to be used in the editor. You've hit upon something I would really like to do. It probably will have to wait a while, however; it requires another whole generated script. I'll also have to think about the design...

Quote: Originally written by Kelandon: I really like this idea. I haven't played with it at all; I have little in the way of custom floors I want to deal with right now, but once you add a few more features, this will be a great program. I liked the idea too, and it was a good way to get some programming experience. I plan to add the rest of the custom data types sometime. Quote: Originally written by Kelandon: Obviously it will not replace writing scripts directly, but it will make it easier to do basic things and serve as a good intro for new designers. In the subsequent major release I want to add actual script generation (not just custom objects). I also want to re-write everything; the code right now is rather sloppy. Edit: I've had another look at the custom terrain section in the docs. It's about twice as complicated as floors; expect it to take a while! At least I have some of the framework in place...

BASE 1.0a2 is now available. This new version adds part of the custom terrain editor, fixes several bugs and adds a small note to the comments of a generated file explaining how to put the floor/terrain in a scenario. Download here. I've been working on a program christened Blades of Avernum Script Editor (BASE, for short). Anyway, I'd like to inflict it on you people. BASE isn't very polished. At the moment, it will only save floors and not open them. Also, I haven't actually tested the floors in the game, so I'll need your help on that. BASE runs on Mac OS X 10.1 and above. Please tell me about any bugs you notice. Ideas are also welcome. Thanks in advance! Features: Creates custom floors in a highly intuitive way. Part of the custom terrain editor has been implemented. Saved files are ready to insert into a scenario custom data script; all you need to do is change the identification number. Saved files now have a note in the comments explaining how to insert it into your scenario. Planned Features: Some way to see/list graphics already in the game without having to consult the appendices. Creating custom units and items. Grouping floors, terrain, units and items into a self-contained scenario data file. Editing objects that already exist in the game, so that extraneous data is removed from the script and the scripts will reflect future updates to BoA. A dialogue and script editor. Known Bugs: The checkmark in popup menus disappears if you de-highlight the active item in the menu. New window placement is messed up if the about window is visible.

Actually, I believe you can. Just insert the icon into the PICT resources of the .cmg file. If that doesn't make any sense, sorry.

I'd guess that you could use species_in_party() with a value of 1 to see if there are any humans in the party. If that doesn't work, find what the call for getting a player's species returns for a human.

Unless you aren't using the basicnpc script.

Oh yes! (wacks himself on the head)

Nope. Custom items vanish whenever you leave a scenario. I'm not sure about altered items, though... They probably are just reset to the standard.

It appears you'll need to initialize quests, special items, etc. in the loading state, while horses, boats, and other stuff that's saved goes in the scen start state.

One already exists. http://www.spiderwebsoftware.com/avernum/blades/workshop/scripts.html

You can control where the monster moves to but not what path it uses, and you also can't make it teleport.

But supposing a resistance of 0%, how would it translate?

Ok, I think it get it.

Cool. However, I still have a question. How do levels of posion/disease translate into HP damage?

Try just using this link: ftp://ftp.spiderwebsoftware.com/mac/BoAeditor.sit.bin

Ohhh... So a strength of 11 would be a 5% chance of 11 layers of posion?

Unfortunatly, that still doesn't help. What happens if I change the floor type?