It is Vista but I downloaded the zip, copied it to an empty folder, unpacked it there, cd-ed to the newly created Traipse directory, ran setup.py and then ran Traipse.pyw

At any rate I am testing out the new system with my D&D 3.5 group. I am specifically interested in getting the bonuses and effects working, of which there are quite a lot of complex interactions for D&D 3.5

I am coming to think that it might be best to introduce a new node which is designed to do nothing more than hold a reference-able value that can be a target of bonuses. Mostly the system I have seem to work OK but there are some issues.

(1) it would be nice when creating a bonus to have a list of what can have bonuses added to it.

(2) sometimes the rules for a value say it should have a minimum or maximal value. For the moment I am handling this with the min(,) and max(,) functions when the value is added in to another node.

(3) in the future I'd like a system that lists all the special effects that contributed to the adds on a die roll

I am working on sheets that do that with other testers david. If you are testing the Beta make sure you load the 4e sheet that is there and look at some of the combat grids. If you look there you will see a Total cell that allows the users to add new cell references and it will return the total of them all.

I don't have alpha or beta working for Traipse.

whatever.

The Beta has been highly tested and a lot of little kinks have been worked out of it. It is going stable soon.

Yeah, that's real helpful.

Well I did ask you how to update to beta or alpha through the UI but since it doesn't seem to work I guess I'll just try updating it through a mercurial call to "hg update beta".

Hmm. Well I guess your suggestion of "hg update <branch name>" just doesn't work which was my reading of the mercurial documentation on "update", but it leaves open how you are actually supposed to switch branches with mercurial. Do I have to initially clone it as the branch in question? I am, as ever, open to suggestions on this. How did you manage to get a copy of beta to anyone else?

Perhaps you just update to a revision which happens to be on a given branch?

no. I use hg update <branch name>

It's part of the Update Manager code.

Well I am talking about a command line command. It doesn't work. And there's no option to change to any "alpha" or "beta" branch through the updater when you run the program.

Actually the problem seems more serious: when I do a "hg branches" command it says there is no such branch as alpha or beta. Does that mean the zip file you directed me to is for an assembla project that doesn't have an alpha or beta branch?

Do I need to get something like a traipse_dev or something instead of whatever the zip file had?

You are making this a lot harder than I have ever seen any beta testers problems.

In the Update Manager you need to add the repo url

http://hg.assembla.com/traipse_dev

Refresh that repo, then choose a package.