El Briano's page

4 posts. No reviews. No lists. No wishlists.


RSS


New Request - Share encounters between my iPad and iPhone.
* A way to share my encounters across my iPhone and iPad. I use my iPad to run the game with PF Battle and set up my encounters there. I don't always have my iPad with me when an idea strikes, I would like to be able to create or update an encounter on my iPhone and have it show up on the iPad.


bffjuuso wrote:

Thank you for making this wonderful app!

Which monster would you suggest I use in place of a city guard or a band of highway robbers?
Thanks!

It would depend on the level of the party. I have used goblins, hobgolins, and ogrillon to represent generic guards or bandits NPCs as the party has leveled. They have a general melee and ranged weapon that is simple to manage.

I also create a few PCs of specific levels to represent other boss type NPCs and add them as appropriate. If I need multiples of that PC as NPC, I add a number after their name to indicate the quantity of them that they represent.


Thanks for the quick response. I love the new features. Can't wait to try the conditions next week. Must have accepted the update without realizing it as I already had the update but didn't notice at last Sunday's session.

Keep up the great work!


Love this app!!! Have been using it every week to DM since it came out. Makes planning encounters so much easier that I can't imaging running without it now. I love the app as is and find it extremely useful. All of my ideas below are just suggestions that I personally would like to see.

+1 to the addition of a turn counter. Glad to see that is coming.
+1 to adding a tag name for the monster. Would like to share a view of the list, but don't want players to know what they are fighting. Be nice to say "Large Oozing Dogs" rather than "troll hounds" to maintain the mystery. Alternately, create a screen view that I can show to the players, as needed.

Apologies in advance if this has already been covered
Things I would like to see/ nice to have:
* XP total for a "battle"
* Ability to collapse multiple of the same monster in the turn list. I like to use large groups of the same monster. 20 hobgoblins makes a long list. Right now I enter just one of a monster, but will hit melee attack rolls 20 times and just manage hit points separately. But if XP count is added, this would be extra helpful as I would then enter the correct number of monsters without cluttering up the list. I am happy to have them all go on the same initiative.
* Would like a better highlighting scheme of the current player. I would like to replace the red dot with a highlight of the row. This would make it easier to see. Or, alternately, just have the player whose turn it is at the top of the list and just have the list scroll around from the bottom.
* Ability to auto re-roll monster initiatives. Players or monsters will frequently disengage causing a new initiative to take place when they re-engage. Currently, I either manually update the monsters or just leave them with the same initiative as before.
* Ability to force player initiatives to be recorded at the start of a battle, by cycling through the PCs without have to do the swipe and enter. All of my players prefer to roll their own initiative. Always have, always will. This would be a good default to specify, by player, when editing/creating a party.
* For monster customizations, allow the adding of an NPC.
* Ability to scroll back on rolls, such as damage. Players are forever asking after the following attack, "How much was that damage again?" I'm old and have enough else to juggle in-game that I don't remember. :-) A back and forward for this would be a "nice-to-have".
* Ability to account for "held" actions. Players can hold their action to go at any point before their next turn, regardless of their dex. Drag and drop for this would be really cool. Supporting decimals with an initiative roll would certainly be a work around.
* The ability to roll Attacks on the monster page like the saves, stats, and CMB/CMD rolls. I suspect it wasn't done this way because of the amount of data to manage.