My experience so far is that, apart from a few almost unusable programs, most make it easy to reach the point of producing something beautiful. There is no problem with that here either, and for the price, it is good that we can create several months' worth of maps before reaching the problem almost every similar program encounters. The process leading there is surprisingly similar, and there are points along the way when an ordinary user feels they have hit a serious wall. Get past it and another wall appears, then another.
When we try a new program, we find a few objects that inspire us, beautiful enough that we gladly use them in a map or adventure, and we get that first taste of success despite barely knowing how to use the program. After trying a few new possibilities, our first reaction to the result is amazement at how beautiful it is. And the next program may have another object we have been missing; we jump on it, and the result is beautiful, good and wonderful thanks to the consistent visual style, the new possibility and our initial enthusiasm. As a hard-hearted reviewer, however, this is precisely the feeling I must be able to put aside.
We put together all sorts of things and happily accept our players' praise: we have improved, learned, made something better than last time. We have managed many kinds of location, our adventures are varied, and the program helped us achieve that. It is a familiar feeling, and Arkenforge delivers it too. After a while, of course, we notice that we already know the objects available in the program, but the particular one we have in mind is not there. At first we turn to plan B, hoping it will be added soon. Perhaps it will.
Arkenforge has not only few developers but also few enough users for them to pay attention to reasonable requests. So for a while, the missing thing will probably appear soon, allowing the next map to be made, only for a few more things it struggles with to come up afterwards. This is not a problem, just a slight limitation. We have grown used to the tools; we work and plan the adventure. If we need something other than fantasy and the tool does not suit it, we look for another one. Not everything will suit every task.
Then comes the criticism we may never have thought of because we are working inside the program: the map was good for the adventure, considering the program's limitations. The same tables, in the same sizes, and the same chests, in the same sizes, turn up too often. The objects in the program are no longer novelties; they have become a force making the adventure uniform.
If we look around the VTT market rather than dedicated mapmaking software, I immediately have to defend the Arkenforge team. They are a small team currently listening closely to feature requests, so you have a particularly good chance of getting a few extra things made that you happen to need, and other VTT applications offer no substantially better possibilities in this respect. So at first glance, this is good.
And it is particularly good for a beginner learning to design a few kinds of location. But this situation will arise, just as it arises in many other contexts. When beautiful graphics look too similar in too many places, feel sterile and so on, more and more people say that what they imagined was better. If imagination gets more room and beautiful graphics less, then a simpler and in many respects abstract visual style is better. Here, however, we get yet more effects, lovely colours and animation, and the system is not really equipped for simpler floor plans.
We appreciate beautifully drawn content. I praise it too. But when I discover that there are not many different tables and I need more variety, I either ask them to help find a solution or experiment. I experiment because they have shown how to build a bar counter out of walls and flooring, so perhaps a table will not be hard either. Benches, booths and many other things come to mind. Lots of things are a little harder to make this way. Either the developer helps, or we are stuck.
Because these symbols would not take stretching or distortion very well, and it would be hard to combine them effectively with other symbols. With beautifully and carefully drawn assets, a pretty table edge sometimes takes far greater priority than functionality like this. And we know the limits. If you need different goddess statues for many cultures and religions, say ten goddesses and ten gods, and then mortals in all sorts of roles, not every warrior statue will be the same, so you need ten or so warriors, ten wizards, and the list goes on until it becomes clear that we would need hundreds of statue symbols alone.
It is easy to feel that this is impossible. And we find that the map which initially brought variety and visual inspiration to game master and player alike is now making everything uniform. A simple floor plan is a perfect handout for many investigative adventures, because it really looks like those in books from the 1920s and even contributes to the atmosphere, but it is woefully inadequate as a D&D battlemat. When I often say that prewritten, published adventures are not really for me, and that the pressure to stick to the supplied maps and levels reminds me of CRPGs in many ways, I quite reasonably hear the answer: the battlemat, the map and the situation visualised on it matter, and the issues above make a good one hard to create.
Because even in the first few adventures, it becomes noticeable that every inn has the same chairs and the same roasts when we make our own maps, even if the culture is entirely different and they are made from different things in different ways. When a professional publisher has an artist design everything individually, we cross that boundary. We have little chance of doing that ourselves, although we can try assembling many things. But after the wonder of "Wow, there is a proper bar counter on their map," we realise that it is not only made of walls, but that the walls do not even join perfectly—and the development team's professional artist put it together. What chance will I have here?