RPTools.net

Thats really nice!

yup, combination of drooling, longing and despair on this end.

Thanks for the praise. But why the despair?

What do you think about the name: Project Tiamat? For the Babylonian goddes from which the world was created.

I am currently working on ordering the projects on my system and git. after that I try to give you a (more or less) working built.

The despair is simply the fact that I won't ever use it, for reasons explained earlier. (Abandonment of the old script).

First test build : Tiamat

Tiamat sounds great! I personally would go for 'Phoenix' (rising from the ashes) but that too might be a bit pretentious
another interesting option is Samsara

wolf42 wrote:another interesting option is Samsara

Love it love it love it!!!

Guess I will choose a more generic term, like RPGTool or something. And then I name each major release. First will be Tiamat.

I worked on reintroducing chat commands. They were broken because macros and the chat were tightly linked in the old maptool. Thus I wrote a new parser and interpreter for the chat.

Halfway through I created a new campaign property editor. I know... That wasn't really an important task, but I enjoy working with tables^^

So here is a simple but easier to use editor:
This would allow me also to make properties a tree instead of a list. Would that be useful? Being able to create properties like this: Would something like this be useful? Or would it be too complicated?

There are many (including me) who build json structures looking exactly like that. So its potentially useful IF both the keys an values pairs can be created and edited through script. In my case (although I as mentioned before, I won't be using your branch) I have a few thousand entries like this in excel. I use excel to create the code to turn them into json objects and copy paste that into maptool and then run the code.
If its possible to create such a structure similarly but embedded in MT and it still allows for automated filling, changing and reading then yes it valuable.

I like your 'checkbox' method, much cleaner then the old system. Now only add script as a value.

This is nifty and all, but I try not to use the token type all that much. The only properties I have in there are displayed on the stat sheet and I'm even moving away from that with my own frame for token stats. I will likely only use it in the future for the mouseover event.

What I really need are some global variables with speedy read/write capability. Saving a json to a token, depending on the complexity can take forever.

I like some of these input/display improvements. I've always thought that there was a lot of room for improvement in these areas. But because they just weren't all that sexy and didn't really add new functionality, none of the community developers really seemed interested in spending much time on them. Where were you 3 years ago?

That said, I'm not sure you're going to get a lot of traction being fairly new to the community and not directly supporting the old macroscript. Too bad there is no way to synergize the two scripts more seamlessly.

Lee's Mote Fork is something that's probably more than a year in the works at this point. I have to wonder if your energy might be better spent producing patches that would be more "fork and release friendly"... that is, mods that might find their way into b90 (which might still come out before Mote) or into Mote itself when its source it opened up.

I get that improving what's here might not be on your radar... but I have to believe that your work would get more use if it could be attached to a more "established" project. Nothing personal... I feel the same way about Lord Ashes' fork. There is certainly some really interesting work there... but it's probably seriously underutilized. Heck, getting people (myself included) to use the b90beta (which is better than b89 in most regards) is an uphill battle.

aliasmask wrote:What I really need are some global variables with speedy read/write capability. Saving a json to a token, depending on the complexity can take forever.

This will be coming when I will create the new alternative to library tokens. Json should be no longer useful in the new system because you can workdirectly with maps/lists. That makes it very fast.

wolph42 wrote:So its potentially useful IF both the keys an values pairs can be created and edited through script.

Of course I will make everything available in the scripting API. If you catch something missing I will add it asap.

wolph42 wrote:Now only add script as a value

I added this and dice expression property types to the todo.

Sorry for not posting that much in the last weeks. I am in the middle of my exams atm. What I am currently doing on the code is also not the intresting. I am finally refactoring and commenting the script API. When this is done there will be some really cool stuff again

I hereby proudly present to you version 0.3 of T³. This is the first release I feel confident in showing it to someone. There are probably still lots of bugs int there^^ But I will start hunting them by switching my personal RPG group to T3.
In this release there was a lot refactoring involved. The key features didn't really change. My next work will mostly aim to improve the user interface und usability. Because these changes do cot concern any compatibility I hope to put them into the future 0.3 releases.
A lot of work also went into the creation of the website and macro API documentation. I hope it will give us a strong base for future work.

Don't stop