Combat Status and Conditions tracker - anyone?

I was planning to recreate some of my scripts from my maptools campaign in roll20 this afternoon. The first of which is my combat condition and status effect tracker I use for my 4th edition games.  I wanted to check if anyone else is working on the same thing. If so, then it might be a good idea to set up a github repo or something so we can have a collaborative effort on a feature that I'm sure many people will use.

I'm working on a bunch of d&d 4e scripts atm, but just working out the limitations of the system atm.

There is already a post in this forum named  Automatic Status Markers

Hey Eric - I saw that post and it's a good start however it's really basic and doesn't do things like 'how many rounds does this last and what are it's effects' so that's the part I'm planning to expand on.

Ah cool, looking forward to see what you come up with :)

So I started working on the basics of this. I found that I'm going to need a reliable way to parse incoming chat commands to allow the players to send in something like  !status --ongoing 5 --end save    or !status --weakened --duration 1 To implement this I'm going to modify Commander.js  to handle argument parsing and pass back help/error messages to the consumer. Unfortunately the api came out during the week so I may not have much time to spend on this. The next issue is going to be determining how to address the target of the condition. Hopefully someone will crack that nut before I get there though.

Targets are hard :( as we can't get selected token or anything, I’m working on some sort of text short cut of some sort but not sure how to do it yet. Maybe some sort of set target macro for the GM. So player says "I would like to attack X with Y", so the GM presses his target X macro then player uses his Y macro.

Yeah. Well I think we can scrape the initiative tracker and then print out a list of targets in the chat box then the player could do !status [name] .... What do you think of that?

Could work it would be best to use a short name or id as names are case sensative.

One might be able to use the 'closest token to this one' script elsewhere in the forums to implement a 'target' for conditions. Simply create a transparent token called 'targeting'. Before launching the status script, place the target marker directly on the token representing the target. Then, the script simply looks for the token nearest the targeting token to obtain an id.

that's a great idea Chaddington! - I already started implementing that for burst encounters but I didn't think about using it for single targets

Ok that is actually exactky what I was just trying to figure out using my admittedly pathetic programming skills - does anyone hsve axworking script for targeting yet? If so, can the code be published here so I know how to stsrt emplimenting it?

I am working on something for this. It will not require tokens or status indicators. 

that is cool. Plus I'm kinda getting used to your code - clean and easy to follow, which good for novices like me. 

My scripts have a basic example of turn order detection (needed for status effects) and targeting including blast and burst, feel free to have a read if you need ideas <a href="https://app.roll20.net/forum/post/149568/scripts-4e-helper#post-151603" rel="nofollow">https://app.roll20.net/forum/post/149568/scripts-4e-helper#post-151603</a>

Thanks Alex, I looked at your code before and it helped a lot with my teleporting scripts.

Done. Posting it as a separate posting for others to use.