Inserting a token after start of combat without sorting all.

I've been using Group Initiative for Initiative calculating. Is there a way in that Api or even a handy macro to add a token to the turn tracker and sort it in the preferred method without the entire turn order being sorted, e.g. with a descending turn order of 4 tokens with init values of 15, 14, 10, and 9, after combat has started and we are on init count 14, I want to add a new character to the initiative order. and they get initiative 13, Is it possible for that character to then be already sorted into the order thus having the next turn? 

You can manually add a token to the turn tracker(right-click: Add Turn) and then drag them wherever you want in the order.  The manually added token's initiative will show as "0", that will not effect the turn order unless you re-sort.  You can adjust the initiative number as well if needed.

This is a feature I've been thinking about, actually.  It is definitely doable but there are some edge cases to solve, the primary one being if your order is: 10, 9, 15, 14 and the new player gets an 11, does it go at the front or the back of the list?

@Vince- Yes, this is my current method of doing so. I currently have the character or effect hidden, and are added to the initiative prior to everyone else and then adjusted afterwards, and I know it's a small thing, but I'm running the AGE system, and it usually involves rolling + modifiers, so sometimes the new character usually comes in at a specific round count but others are introduced on the spot. Thus, something I like rolling in game, and anything that makes calculations in combat that much quicker is always appreciated, so automation with a macro or in the api for that bit would be a nice feature.  @Aaron- My thoughts, and obviously I'm sure there are possibly strong preferences to sorting, but I would suggest the front of the list in your example. Considering that if this character or effect is in essence entering mid initiative and order is calculated consecutively, the turn order is just counting down from highest initiative, and checking for the lower number immediately after the last number is recognized. So, after the 14 init player goes, it's like it's checking for 13,12, and 11 but skipping them because they aren't there. I feel as if that way its easier for the GM to resolve their own preference whether the GM wants the the new player to actually act before or after the 10 init player, it would arguably be easier for the GM to advance past the new players turn for the latter preference, than for the GM to reverse the turn, or advance the entire round to give the new player a chance to act in the former preference. 

Hello Timothy T., I have moved your post to the API forum.