A little eye candy for you while I work on pulling EpicTable 2.0 together. The new maps in EpicTable 2 support some new features. I’ve spoken to many of you about separating terrain and dungeon dressing from the map background and the token layer. While looking at the issue of map layers more generally, it struck me that there were some interesting effects possible. One such is this battle map of a volcanic cavern with flowing lava and smoke and steam. As cool as this is, I’ve no doubt it will drive some people crazy, so rest assured, I’ll give you a way to turn off animated elements of the map.
About this map
This map started life as one of the maps from the 2013 EpicTable Box Set, a beautiful cavern map created by one of my all-time favorite fantasy cartographers, Christopher West. You can find more of his work at Maps of Mastery. (Watch out, though–a lot of his stuff is for printing, so it’s super-high-resolution. I had to scale it down to some tiny percentage to make it virtual tabletop ready–and it still looks amazing.)
I made some areas of the map transparent, added some flowing lava under it, somewhat slower than the original, and added a layer of dark clouds, rendered mostly transparent and very slow, on top of it for the smoke and steam. Both those videos were from iStockphoto, and um…I’m chalking their cost up to my Marketing department (which is me).
Any of you think you might be able to make use of animated token bases? Check this out:
These are, for the moment, rather non-trivial to create yourself, so I’d probably start with a gallery of them for different conditions that you could apply to a character…like…um…”on fire”? 😉 I don’t know, honestly, that fire is the ideal example. I think maybe flying and confused and entangled might be better examples of indicating character status in this way. But you’ve got to admit the fire looks cool. 😉
How would you guys see using this? Or do you? Right now, I think of it as a proof of concept that may or may not have a concrete use. Before you suggest it–because I know you are about to–the related feature that this enables, which I’m more sure will be useful, is animated spell effects. I’ve been looking at things like (to go all D&D on you for a second) Obscuring Mist and Entangle and a Pleasantly Roiling Darkness. As with all things EpicTable, I’m trying to give you a set of game-system-neutral components that you can use in any game you want, but where I know certain things are going to be useful because they appear commonly in certain games, I’m not above providing some pre-builds for them.
A Little Gratuitous and Unnecessary Background for the Insatiably Curious
EpicTable 2 represents a fairly major technological uplift relative to EpicTable 1. I created the first version of EpicTable when some tech that’s available now just wasn’t around or wasn’t ready. As new devices have entered the market, it’s pushed me to upgrade the technology underlying EpicTable. In some cases, the benefit is just that it handles new scenarios like large screens and high resolution displays better. That’s why I started with chat, by the way–at the time that was written, one had to do horrifying things to render dice and text together, and not only was the code complicated, but it just doesn’t work perfectly with some of your new displays. The additional benefit, though, is that the new tech opens up all kinds of possibilities, and it’s looking like the EpicTable 2 codebase is going to be significantly smaller and simpler. The core is the same–the way a dice roll or a character or a map is modeled is the same underneath–but the way it hits the screen and allows interaction is way, way, simpler.
Here’s your first look at one of the things currently under development: the “Character Mini-Sheet”. This is a little card that you can pop up next to your character/monster token on the map. It’s meant to give you quick access to the values and actions that you need most often during play. Here’s a quick example.
On this card, configured for a D&D or Pathfinder game, you’ve got icons for armor class and hit points, followed by icons for a couple melee attack rolls and a ranged attack roll. These are all interactive. That is, you can type a numeric value or use the arrow keys in the AC and hit point icons, and you can click on the dice roll icons to make the corresponding roll. The second row has a rather unlikely set of conditions–wounded, hasted, and dead. You’ll be able to configure a set of conditions for your game, so that you can easily add them to a character during play. Notice the little grey plus signs? Those indicate unfilled slots where you can add additional icons.
As always, EpicTable is game system neutral, so you’ll be able to configure the mini-sheet to suit your game. As the mini-sheet concept develops, I’ll show you alternative configurations of the mini-sheet and some of the surprises lurking under each of these icon types.
EpicTable 1.2 is right around the corner. The features are done, and I’m testing a release candidate. The major feature of EpicTable 1.2 is fog of war, something I know many of you have been waiting for. I’ve been testing with it awhile now, and it’s fantastically helpful. I wish I’d had it in my last Pathfinder game. If you’re not familiar with the term, or because fog of war sometimes means different things to different people, let me explain what it means in EpicTable. Fog of war allows you, the GM, to control which parts of a map the users can see.
To whet your appetite, here’s a video demonstrating the new fog of war feature. While this video doesn’t show it, the fog of war feature is not limited to maps. You can also use it on tabletops. So, if you have a more abstract playing surface, you can hide certain areas. Or if you use tabletops to share pictures, you could choose to hide some of them. It’s very fast and flexible, and it’s built for winging it. Enjoy.
EpicTable 1.1 is nearing the point where I’ll start letting people get their hands on it. I’ve been very reluctant to break anyone’s game night, so I’ve held on to this release, probably longer than I should have—certainly longer than I did with the beta releases. At this point, there are a few things that need to be put back together—changing technology on the tabletop/map area meant changing lots of little things, like how I handle right-clicks, how rich text is edited, etc.
With Gen Con right around the corner (mid-August), my goal is to get EpicTable 1.1 out there as the currently released version, and thereafter, start giving you guys some 1.2 and 2.0 preview content. If you’re at Gen Con this year, ask about the features we’re not selling yet. (We don’t typically demo features that aren’t in the shipping product, because we don’t want someone feeling like they got a bait-and-switch, but if you’re in-the-know and you want to see what’s still in the lab, let us know.) Once 1.1 is out and I’m back from Gen Con, I’ll do a better job of giving you previews of what’s coming up.
Speaking of what’s coming up:
EpicTable 1.1 is full of goodness. I’ve been working on it so long I sometimes forget how much there is to love about it. There are a few of new features, and a lot of what’s there just works better. EpicTable 1.1 will be a free upgrade.
EpicTable 1.2 will be the beginning of the long-awaited vision features. Several things about the technology shift in 1.1 will make (parts of) vision in 1.2 cleaner. I want to get this one in the hands of some existing EpicTable customers and let you help me make it better before springing it on the world. I know several of you have been waiting. I’ll be sending out more details on this after Gen Con; i.e., probably in September. (EpicTable Box Set customers: here’s where your “VIP pass” will come into play–you’ll be the first to get your hands on some of the 1.1 and 2.0 features.) EpicTable 1.2 will be a free upgrade.
EpicTable 2.0: Lots of things are vying for priority. This is going to be a fun one. I’m going to try beta testing 2.0 features with some of you 1.x folks, and I’m going to try not to let vision consume me, so that there’s some 2.0 work going before too, too long.
I did some EpicTable 1.1 testing last night with part of my Friday night gaming group. It’s looking much better than last week. But what would one of my status updates be without a weird looking bug to show you? This one, I call the “Player Horde”.
I’d like to tell you that I just have lots and lots of friends named “Scot” and “chris”. Sadly, that’s not the case (for who could ever have too many friends named Scot or Chris?). It’s far more likely that there’s a bug in my participant tracking. If I were to guess, I’d say that the New and Improved Participant Tracker and the Old and Somewhat Inattentive Participant Tracker are furiously reacting to each other’s notifications, each engaged in an existential struggle, trying to be the guy in the know:
“Hey, did you hear Scot just joined?”
“Yeah—I was just going to tell you that. Chris joined too.”
“I knew that, oh and I hear Chris—”
“Before for you go on, I need to tell you: Scot and Chris just joined.”
“Sure, but did you know Scot joined too?”
I’ll get in there tonight after the kids go to bed and break that up.
Where does EpicTable 1.1 stand?
At this point, everything that I expect to work does work. There are just a couple things that need to be re-implemented in the new technology, and they’re fairly low risk things:
Context (right-click) menus for objects on the map/tabletop.
Snap and size to grid
A lot of this is already done outside of the view and it’s just a matter of reflecting it appropriately in the new view.
There are some things that I’ve been improving or adding opportunistically while I have certain parts of the code open. I really want to talk about a couple new things, but I don’t want to force myself into releasing them if they end up taking too long. I’ll put together a whole “What’s New in 1.1” to make sure I wring every drop of appreciation I can out of the work I’ve put into this release.
I was working on EpicTable 1.1 tonight, modifying the dice tray and the way dragging is handled. I have this neat little routine that creates a cursor from an object you’re dragging and the existing cursor. I use then when you start dragging an object, and ordinarily, I reset it to normal when you stop dragging. Here’s what happened when I neglected to reset it.
What you’re seeing there in the red circle is a custom cursor. It’s the result of dragging a d12, then a d20, a d4, a d6, and finally, a d8. It should look like a d8 with the little cursor arrow. Instead, it’s a d8 with a little d6, with a little d4, and so on, as long as you keep dragging dice. Not very functional or intuitive, as cursors go, but kind of interesting.
Speaking of version 1.1, expect it soon. I’m trying to get a build ready for a second internal test this weekend.
Long ago, a very wise artist/designer/musician, in between trying to coerce me into implementing playing cards, entered a feature request for drop shadows. I had them for some types of notes, but under the old technology I was using, it was just to difficult/time-consuming to implement drop shadows for everything. Now, though, with the new tech going into EpicTable 1.1 for other reasons, drop shadows are quick enough to implement that I can make good on this long-standing promise to “look into it”.
They do add a little spiffiness…. Notice that they’re not limited to rectangular objects like the 1.0 shadows.
It’s less obvious, but borders are at work here as well. The dark grey border around the image of the girl is EpicTable’s doing. Essentially, as I add the 1.0 objects to the 1.1 tabletop, I’m hooking up the Format tab, which in 1.0 is active only for text fields. This gives you access to borders and shadows and other visual tweaks to the objects on the tabletop.
Don’t worry—I’ll get on to more important stuff, like cards and vision/fog-of-war, but as I’m hooking things back up, it doesn’t take that long to add some consistency and polish that 1.0 was lacking.
EpicTable has had notecards for a long time. But they’ve always been very plain. The text fields in EpicTable 1.0 are all kinds of fancy, but that’s not the case for the other objects in this weird trio made up of notecards, rich text notes, and text fields.
They’re distinct partly because they’re used differently and partly because they were implemented at different times. The downside of their being distinct is that when I made text objects super cool, I couldn’t easily do that for rich text notes and notecards. Now, in the technology overhaul tabletops are getting for 1.1, I have to change these objects anyway. While I’m doing that, I’m taking the opportunity to unify these concepts. From a code perspective, these are all going to be the same thing. That’s good for you, because it means that all these note-like objects will get the same treatment that text fields have in 1.0. As you can see here, notecards get a significant boost in functionality as a result.
There will still be some out-of-the box presets for notecards vs. text fields, for instance, but you’ll have a lot of customizability, and you’ll be able to save your creations. So, if you love mint green notecards, you may applaud now.