Earlier I asked an important question: why have so few fan-made M.A.G.U.S. systems been created? At the time, it concerned a small detail: people do not like making something like this merely to leave it in a drawer, if only because of the amount of work. Writing articles, we have the freedom to choose from the easiest 1% of topics, with few landmines and an easy path to finishing. Except the occasional case where we do not; there are bumps everywhere. Developing a system, however, means a complete whole. Support. The service behind it. Making sure questionnaires, articles, supplements and related pieces arrive on time whenever possible. The questionnaire was late this time. But Delta Vision's fourth questionnaire is here. It is certainly worth looking at. Questionnaires, and rebuilding trust through them, are currently part of the road towards a marketable system's release. But this is not a wide, straight road: it is a minefield. A minefield because of M.A.G.U.S.'s current situation. Because of fans' expectations. Still because of the legal background cursed a thousand times. And because designing the system includes that hardest 1% too. Then come the bumps.

Not only for Delta Vision, but for me. For us. I wrote an article examining whether a d100-based system was technically and commercially feasible if we wanted to avoid smartphone dice rollers during play. Many celebrated: wonderful, I was voting for d100. No luck. The next article came: d6, d100, distributions and the feel of the game. Fix d100's many flaws and a d100-based system can follow. Some took that as certain. I think at least five steps remain:

  • Reach a point where the resulting system is usable.
  • Ensure the finished system fulfils its intended purpose.
  • Explain how it improves on previous systems.
  • Explain how it improves on the other alternatives.
  • During testing, incorporate things the market expects. 

Until those five steps are taken, there is no reason to treat what we are developing here as a real alternative. That requires getting through not the easiest 1% but the hardest, plus the other 99%, without running out of momentum. Once finished, it helps to have time for supplements too. This lies behind three deliberate decisions.

When I asked whether we wanted substantial revision of the old system or a genuinely new one, the question meant something different to me: revision can happen step by step. Even with the system unfinished, a twenty-fifth-anniversary edition correcting many small errors could include little changes as optional rules, reflecting "what we have learned in twenty-five years". Carefully editing minimal optional rules into the original text is an alternative available from the very first optional rule. But a handful of changes would not bring people currently using other editions back to the original. A differently rolled skill check, skills rewritten as percentages, improved attribute checks, fixes for d100's flaws: a few sentences of optional rules. Let us admit, though, that this would not convert someone attached to the ÚTK's Favour Points. It is not plan B but plan Z. And I cannot promise its flaws are smaller than those of the d6 solution. 

My second decision was that, although some still swear by complicated systems, we need a modern, simple one. Fewer pages mean fewer belonging to the difficult 1%. The problem is that content, setting descriptions and so on are still needed, and much of that belongs to the difficult 1%. Anyone can immediately point out that, if I think logically, have good ideas and get them into the system, someone then becomes an official creator. Questions about the setting will surely follow. Something must be said about the world too: content matters as well as mechanics. There will be many, many "difficult 1%" issues. Such as what I do with the worldbuilding in a few unreadable books.

My third decision was to make the principal setting a kind of "minimal Ynev", with novels connected as alternatives on the basis that "with small changes, this too fits Ynev", something you can build along similar lines. But on neutral foundations, and offering opportunities to do many things in play that heroes can do in the novels. Two, or rather two and a half, approaches can help. One is a very simple rule: Stealth remains Stealth whether you use a physical method, ancient magic or a racial ability. We have often used the principle that the mechanics remain while the description changes. 

Even with AD&D 2nd edition and the Player's Option books, we often used rules creatively. For instance, I said the increased Strength received as a priest should have a racial basis for my character. Mechanically, a permanent magical effect bought with points raised an attribute; in the world, the explanation was the character's backstory and bloodline. It can work in reverse too: any ability or skill can receive a religious explanation. Even "almost superhuman Dexterity" can be something a chosen character owes to Arel. 

Regarding Favour Points introduced by Új Törvénykönyv, someone asked what happens if a favoured character changes religion, knowing the rules do not allow it. Many answers appeared. Mine stood out somewhat. The gods can probably tell where you belong. If that is with Arel, she may well support you even while you still think you will follow her rival Ellana. What you learned and what you tried to cast is beside the point, because the goddesses knew your path all along. You see a change where no real change exists. Someone who was one kind of priest both mechanically and in their portrayal was another kind in the world's reality. Applying the principle that mechanics remain while description changes makes this a good character concept too: more interesting, multidimensional.

The second approach is a skill representing an "iconic ability". An iconic combat ability inflicts X damage during a scene with probability Y whether it is an arrow machine gun, a firearm, a necromancer's greenish death ray or an assassin's words of power. Something making the character completely unique. You distribute the damage as you wish. I could write fixed numbers now. That would be great. Even explain how to gain modifiers. But testing can tune this precisely, and it should fit the eventual finished system. In any case, if you use it rarely, the skill can gain +10 per scene. Since skill checks add d100 to the skill value to reach a target number, success might begin at 70, with each additional point providing one point of damage to distribute. This could more or less work in the current system too. Honestly, though, I would handle damage differently.

That is already a serious bump, because changing how damage works would require simultaneous changes to combat, character creation and spellcasting. Doing all that in one article is very difficult.

Imagine another small detail. Where Új Törvénykönyv uses Favour Points, we could introduce a score I find more interesting: how strong the character's "Essence" is. A better-played character has stronger Essence; a poorly played one, weaker. The game master uses this mechanic as a reward. A priest's Essence lies in their relationship with their deity. A wizard's often lies in a depth of focus and concentration far beyond other magic users'. Essence signifies something else too. As long as you have Essence, your story in the monastery is simply written onward with you having survived. Thus it, rather than Health, can be the guarantee of survival. A simpler approach can replace the existing ÉP/FP concept: 

When your combat reserves run out, you are defeated; after that, your pain tolerance can continue to decline. When pain tolerance also runs out, you are broken, and your Essence can be damaged. A continuing campaign character has greater Essence through many rewards and divine favours, so is not only stronger in certain situations, at the cost of reducing Essence, but also far more likely to survive than a newly created tournament character of the "same level". The latter can face greater mortality and risk, making play more exciting. This supports different play styles. Spending Essence may produce a stronger effect than an iconic ability. If the result temporarily or permanently reduces Essence because the ability is so powerful? Stronger still. Instead of tactics based on combat positioning and many other details, using iconic abilities and Essence can provide tactical choices while making combat more cinematic.

In most cases, "combat reserves" can be shared. Each side's checks, whose difficulty depends on the opponents' values, reduce enemy combat reserves in proportion to their success when attacking. A defending side can reduce the damage inflicted by its enemy. Healing and spending a character's Essence can even increase combat reserves. The result? You can describe how your character fights more freely and with more roleplaying, without seeking "the mechanically optimal tactic". Another advantage? Once character and party creation establish how combat reserves are calculated, we have turned combat into a sequence of simple checks, a group contest. Far fewer values are needed. It is faster and more lively. Since combat is not chess, I find it more realistic too. 

Moreover, taking a serious wound no longer merely means cursing a bad roll. In a fight going too well for the enemy, looking too evenly matched, it can result from a heroic manoeuvre through which you knowingly accept the wound. A dramatically important moment in which your character matters right then. Such moments make both good and bad rolls memorable. 

Delta Vision's fourth questionnaire asks an interesting question: Which kind of character with religious faith do you most enjoy playing? The problem is that ordination is not restricted to characters mechanically belonging to the priest class. Most village clergy have no priestly powers either. Some religions' churches consist almost entirely of religious witch orders, and similar orders probably exist in other churches too. There are also devout knights in religious orders without Favour or Mana Points. I could say the questionnaire classifies them as followers, since they have no mechanical modifiers. Invoking the principle that mechanics remain while description changes, one could say that is roughly true: they have no mechanical modifiers. Until the game master intervenes a little, because a GM can readily grant one.

Witch sects associated with Arel have appeared several times in our ongoing campaigns. It is easy to imagine the GM proposing a new method instead of the Potion of Power, which manipulates life energy and is harmful in many respects. Perhaps some good practice pleasing to Arel, reducing Endurance at least as much as Magical Embrace and taking some time too. Banning the Potion of Power is a restriction, rather than extra points or power, but already a mechanical modifier. In return, Arel pays attention to the ordained individual. Flexible handling of Essence and iconic abilities would remove this problem. But the current questionnaire gives me no way to say, "Some ordained people outside the priest class mainly receive restrictions through this." 

The concepts of Essence, pain tolerance and combat reserves overturn the system. Much of combat and magic may therefore cease to exist as separate subsystems. With purely skill-based character creation, this is simple; converting existing characters also takes only a few modifiers when combat values become skills and FP and ÉP become combat reserves. Clearly, changing the values of Essence and iconic abilities makes it easy to shift between a more traditional worldview, where many not especially famous adventurers have defeated aquirs, and a darker, somewhat horror-oriented world, where the aquirs win. But we must switch to skill-based magic, so the skills corresponding to spells need to be produced as content. The fiddly work most agonising to a creative mind arrives. 

This is where every M.A.G.U.S. reform's problems have begun. With an excellent idea, everything was wonderful at first. Then came the fiddly work, the fixes, the developer exhausted by negative feedback, the dwindling enthusiasm. The final 2–3% of corrections never got done, even if the book appeared. Missing that 2–3% is enough for many players to say, "That's a critical flaw. Of course I can fix it, but..." The critical flaws in Favour Points come to mind. They can be fixed, and not with much difficulty. But many people say, "To hell with explaining this every time; I'll stick to the tried and tested old version." We have not even started the fiddly work. Of course, the system is ready. I can play it whenever I like, understand its logic and set its values. But roughly none of that is written down, and none has been tested so that many values also fit someone else's reasoning.

But to get feedback, you must make promises. Promise to do something. I see that we sometimes fall behind even on our own planned material, distributed among several people. Working officially with deadlines would be terrible. If a few items under our "articles in preparation" option remain unfinished, big deal. We do not charge for them. Someone who likes our writing will enjoy another piece too, and can suggest a topic at any time. Official work, however, has deadlines. People wait on tenterhooks for the material promised for that Friday. Nobody cares that you cannot make a living developing RPGs in Hungary, that you have another job, are dead tired or face family issues. Everyone will care that you did not release the promised product or article on time and disappointed them.

The news arrived that the official M.A.G.U.S. project's developer blog had launched. Should we focus on the fact that three weeks have passed without a post? Those of us reporting it complain because we are embarrassed to have misled our readers too. I explained why writing introductions to the questionnaires is difficult. The understanding was that we would receive the news and merely post it. All that remained was the link. And the sting: we had not agreed to spend Friday afternoon, when we had other things to do such as enjoying ourselves, writing content and introductions. Excuse me, we were misled: we promised to share it widely, but it already takes more time than we allotted. The fourth questionnaire slipped a day without a word. For anyone waiting to post it, that killed every possibility of making evening plans. If we dare mention it with a little humour and a knowing wink, one of the publishing team's friends arrives with personal attacks, demanding to know why we are complaining. 

If we were complaining, we would describe the repeated deception. Ask rhetorically why we should trust this project. Politely withdraw from our promise to link the material. Given how often the fan community has been misled, we could easily call this simply the umpteenth occasion: who expected anything else? Who expects the future to differ? Say that what we see is not quality. That smaller problems are enough for an Early Access game to be torn apart on Steam. Even a traditional RPG would face uproar for missing, say, a Kickstarter deadline. Fine, we are not investing money yet. Perhaps. But certainly work and time. And believe me, when a situation like this requires a new website component, that costs money.

The truth is, though, we know building a workable system is difficult. DV's strength as a publisher in the Hungarian market does not mean enough capital to maintain a proper social-media team. Beginners often do the work, and mistakes will often happen. Developing a system and rebuilding trust is a damn difficult process. We could interpret the issues above as broken trust. But there is another narrative. A team that has so far largely succeeded in restoring trust despite difficulties has improved a great deal, but that improvement is relative. When many saw DV as the industry's most rejected company, partly through the DV–Lunír–Tuan dispute and partly through much unfair dealing, the road upward from "one star only because zero isn't possible" passes slowly through a genuine one star, then "almost two". That mountain must be climbed. It takes enormous work and time. Changing overnight is impossible. 

I tell the publisher's representative with a smile that their polling component has the advantage of at least being cheap. The guaranteed answer is that I know how little money there is. I am a little annoyed they cannot afford SSL either, when Cloudflare offers it free. Where kalandmester.com is hosted, hosting is available for 14,400 forints a year, enough for much more than the developer blog. Naturally, HTTPS and HTTP/2 are available. Given a supplied logo and colour scheme, the foundations of a simple website with a few menu items can be laid in hours. This includes installing components the company is licensed to install on clients' sites, even ones more expensive than the polling component in question. But two years of hosting and the support available in such a package would swallow a few crisp ten-thousand-forint notes. Even below a six-figure sum, this market is accustomed to sales of only a few hundred copies. 

That would add a few hundred forints to each book merely to provide the support shown by a fan website willing to spend a minimal amount. Fan sites have probably made several such investments over the years. The webshop also needs SSL and more hosting capacity. If they spend on the web, we could reasonably say that we have run advertisements on Facebook, for instance: they should advertise too, not leave it to fan sites. Gradually the book's price would rise again. Still less would reach the developer, artists and writers working on the setting. We would not reach minimum wage. 

Then there is risk. Of the new-system projects, Új Tekercsek and the d20 attempt appeared. The Szürkecsuklyások system and Lunír's attempt did not. Új Törvénykönyv could not appear officially either: it lacked the rights holder's consent. Supposedly it still needed corrections, which cost money. Two projects out of five were released. The legal situation changed during this period, of course, but the ratio is bad regardless. If we previously said effective costs would add only, say, 400 forints per copy on average, business risk makes the difference a thousand immediately. Before the retail margin; afterwards, probably much more. That would further reduce sales. The extra spending would still not reach committed rejecters, while some committed fans would drop out because of the price. It might or might not reach buyers whose purchase depends on certain conditions.

Projects sometimes slip. Overwork and lack of sleep sometimes knock us out. That is fine, and although we could point to a promise, we do not want to turn it into a question of honour. But I think it is reasonable to expect the responsible person to tell us next time a questionnaire is delayed. Deciding and notifying us by four in the afternoon costs nothing. Honestly, though, that is not the real problem. Not at all. Ideally we would notice none of this. The questionnaire would appear another time, perhaps as extra content, and a few articles prepared well in advance could go live instead. 

The current situation is probably that everyone, starting with the editor, works beyond office hours. Sometimes they collapse and rest, because they need that too. What we see from Magnus does not suggest quality. He needs criticism, including harsh criticism. He learns from it and improves through it. His work needs picking apart, with even the smallest issue pointed out. But he also deserves patience, because he is doing this despite my explaining what follows the first few per cent of easy work. I also described the financial obstacles, uncertainty of publication and the rights holder's attitude. Most of us would never have accepted these conditions. The editor available late at night after work, the project's public face who asks favours and bears the embarrassment of delays, also deserves respect and trust.

If the rights holder begins the "this is no good after all" game, the publisher's head and the editor representing the project will again face embarrassment. And forgive me, but the rights holder may also notice obvious flaws flagged by the community, only by then corrections will be much harder and could cause the project's complete failure. The publisher takes risks too. Admittedly, if it loses on the project and cooperation breaks down, it gains sympathy as the victim and profits on other projects. Success likewise reflects its work, and we buy more than M.A.G.U.S. from it. Many small profits may cover the M.A.G.U.S. project's cost too. Still, we can see effort and risk-taking on this side as well. The finished system they hope to receive reduces costs, but both sides can be satisfied with that. 

There is a man named András Gáspár. He owns the rights. He did during the ÚTK project too. Those rights will be worth a great deal to him, his family and so on if this project succeeds. Incidentally, he is a writer. There are a few other important writers too. They have often made promises. We have been disappointed even more often. A few small pieces of writing are needed so that a slight delay builds their legally owned brand instead of causing disappointment. Even an article on how the new, consistent Ynev affects their creative freedom. Or how unfinished business from the present day of already published works is affected by spoilers arising from the setting in books taking place later. There could be many interesting pieces to keep the blog from being empty. We would see that avoiding our disappointment matters to them too, that they also go beyond their limits. Somehow that has been missing. He and a few colleagues are the big men at DV through the M.A.G.U.S. brand: they brought M.A.G.U.S., the goose that lays golden eggs. But when numerous promised novels are late, yet another system project fails to reach legal publication, rubbish has repeatedly received the rights holder's blessing, and precisely the rights holder's effort remains invisible while we repeatedly feel deceived, that brand eventually looks less like a golden-egg-laying goose and more like an aged, lame nag laying horseshit.

The others are nevertheless trying to climb the mountain between zero and five stars. This particular mountaineering is an interesting sport. We slag off the system, but see effort. The claim that DV would also be open to another system has credibility. If they reach a point where alternatives exist, the present system proves less appealing and a new direction emerges, some steps taken now need not be repeated. Whoever undertakes it could prepare much of the weekly content far earlier and schedule publication on the appropriate site. A number can be mistyped there too, of course. But another admin could watch and solve such problems. 

Creating a system is difficult in itself. Creating a carefully considered system is harder. Creating a good one is much harder. M.A.G.U.S.'s many expectations increase the developer's difficulty by orders of magnitude. Then comes the audience's severe, justified resistance after previous projects, which must be overcome by slowly rebuilding trust. Meanwhile, there are certain to be people concerned chiefly that their collection of "new classes" published one after another for the old system retains its "value", guaranteeing opposition.

Genuine criticism can easily disappear in the sea of negative comments, yet it is what needs answering.