Modular Spellmaking

Guy picked the first component shape on the list and tried to cast it in isolation. With circle-based magic, this was possible as long as the spell could be standalone. Some components had dependencies. For those spells, Guy would have to work backwards and cast the dependencies in tandem with it.

While the RoK greatly amplified his rate of progress, it was technically considered an isolated space. His body was not physically present in here, only his consciousness was. Therefore, Guy had to alternate between the RoK and the real world when testing the spells. And so, Guy optimised the process by grouping up spells together and testing them in bulk to reduce the number of transitions.

As Guy went through the process, he gradually started to understand the perspectives of the people indigenous to this world. For them, magic was an arcane process in which the end justified the means. With things that didn't make any sense to them, they simply chose to overlook it since all they cared about was the outcome.

"This spell creates fire…Why? Who cares! It makes fire, that's all that matters," was the common thought process.

While there were groups that specialised in spell research and development, the way they went about it lacked generalisability and repeatability. Essentially, their methodology was unique to the school of magic they were trained in, and an outsider would not be privy to the process. This inevitably led to a regression in the rate at which new spells were developed.

Unlike back in Guy's original world, where knowledge was accessible at everyone's fingertips, this world, which was still stuck in the middle ages, kept knowledge on a need-to-know basis.

Ultimately, this problem was circular. Without dispersion of knowledge, there was a lack of varied perspectives, resulting in technological stagnation. And the advancements that did occur, happened at a snail's pace.

Thanks to Guy's out-of-this-world experiences, and with the help of the RoK and the technology within it, Guy was able to approach the problem with a unique perspective.

As a modern man who was initiated in the scientific process, Guy was able to systematically go through the decomposed component shapes and take pertinent notes on their purpose and effects.

After a primary run through the components that worked in isolation, Guy realised that in each fire-based spell, there was a component that infused inflammable properties to mana. This produced what the locals called fire-infused mana or mana attuned to the fire element. There were additional properties to the mana such as conductivity to heat, which were implicit.

What Guy realised was that the magic in this world went for a one-size-fits-all solution.

"Want to make a fire? Well, first let's change a part of your mana to become inflammable. And while we're at it let's make it conductive. Oh, and why not make it volatile. And I almost forgot, the fire needs to burn continuously, lets add an oxidising agent as well!"

Guy felt that the whole idea was redundant. There were already inflammable compounds in the air, there was also oxygen to sustain it. Why bother changing mana if a resource is already available with all the required properties?

The dependent components that followed added to this base infusion step and performed actions such as compression, dispersion, concentration, diffusion, repulsion, attraction, energising, de-energising, and so on. Those were the names Guy gave to those spells since their purpose was implicit in their effect.

Guy decided to categorise these components as "Action Components". They performed specific actions and were dependents. In order to gauge their effects, Guy used a basic spell called |Inspect|. It was considered a cantrip, but it was moddable to perform different tasks. Guy modified |Inspect| to observe the molecules of the substances in the area affected by the spells.

He then documented those Action Components for later use.

After that, Guy moved on to the less frequent component shapes captured by the decomposing algorithm.

Most of them were duds and didn't have any purpose in the grand scheme of things. But the ones that stood out, were dubbed "Source Components" by Guy.

These Source Components were different from Action Components because they were independent. By design, they appeared similar to the fire-infusion component. But instead of sourcing mana, they sourced naturally occurring substances.

For instance, one Source Component appeared to draw in a large quantity of air from the environment to increase the size of a |Fireball| spell.

And so, Guy scoured through the folders and managed to gather a list of Source Components.

This entire time, Guy had a particular goal in mind. When he worked as a teacher, he primarily taught kids who were in elementary school or middle school. While he did teach a few high-school courses, he preferred interacting with little kids over those hormone-fueled monsters. Furthermore, his charity efforts were geared towards increasing the base educational level and inevitably forced him into that speciality.

As a teacher, Guy aimed to increase the approachability of knowledge to those that didn't explicitly show any interest in learning. For little kids, going to school and sitting in classes was simply a chore. It was something they had to slog through.

It was his job as a teacher to make them interested and capture their curiosity. To accomplish this, Guy would regularly scour various teacher forums and discussion boards to find novel ways to engage his students.

One of the topics he found most difficult to teach kids was coding and programming. In the age of information, working with technology and automation had become commonplace. It was almost impossible for someone to survive in a competitive STEM industry without having some knowledge of how to code. So it was inevitable for the topic to enter the school's syllabus.

At first, it was only a high-school requirement. But over time, the topic began to breach into middle schools, and finally into some elementary schools.

One can only imagine how hard it was for a teacher to get a child interested in printing "Hello World" on their monochrome consoles windows.

To them, the conveniences provided by knowing a programming language were irrelevant. It just wasn't exciting enough to learn. Guy blamed the media for glamorising the idea of programming for the layman. Typical coding sessions seldom involved flickering screens, lines of scrolling text, and intense techno music.

In Guy's experience, a typical coding session usually meant hours of cursing at his screen, downing cans of caffeine-filled energy drinks, sleepless nights, and frantic searches on StackOverflow.

So the question at hand was: How to get kids interested in coding?

Guy found that kids preferred it when their work displayed tangible results. Most of the time with coding, the results were abstract. Things happened on the screen, and lines of text were spewed out. They weren't interesting at all.

From various forum threads, Guy managed to find a coding framework perfect for kids called "Scratch". It was a programming language that was completely visual.

It contained specialised blocks that performed specific tasks and could be chained to form a script or a function. The best part was that the result of running a script was automatically evident in a graphical user interface. It was also possible to program peripherals using this language.

Introducing that kid-friendly programming language showed immediate results in his classroom. His students started to take initiative and came up with novel projects. The best part was that when those students reached a higher level and learned of the inherent limitations in the language, they were able to assimilate advanced languages more easily.

Guy's end goal in his current endeavour was to develop a method to create spells similar to the way Scratch worked. He already had "blocks" that performed actions, and blocks that were sources. He wanted to figure out a way to efficiently put these together and still have a functioning spell.

Based on his observations, the spells had to have a circular construction to work. He didn't know if it was a strict requirement, but it was a plausible conclusion given the lack of spells that suggested otherwise.

So in his experiments, he started with a large circle. Next, he began to fill in the circle with the components for a simple spell that compressed air and rotated it into a ball in the palm of his hands.

He first placed the components in a symmetric pattern inside the circle. He then tried to activate the spell, but it failed to even initiate. It was a complete dud.

After pondering on it for a bit, Guy hypothesised that a specific ordering was required. Just placing the components didn't provide a proper sequence for the components to activate. It didn't make sense for air to compress before actually sourcing it.

And so, he connected the components using straight lines and achieved some success. Although a ball formed in his hand. It was unstable. It would frequently flicker and would disperse intermittently.

After activating the spell a few more times, Guy found out that the result was because of a sudden interruption in the influx of mana. Compared to published spells, this construct would often sputter. If the spell construct was equated to a long and winding length of tubing, it was as if there were sudden knots in between causing the water pressure to build up and disperse irregularly.

Guy wasn't knowledgeable enough to figure out the nitty-gritty details of the whole spell casting process. His current methodology was purely led by his preconceived logic and concepts. So after getting stuck at such a critical juncture, he began to push his mind to come up with a suitable solution.

"The components work. The spell circle works. Then what is causing the mana flow to choke? It most likely has to do with the interconnects between the components…"

As he spoke out loud, Guy was struck by a sudden thought! "Is it because the connections aren't closed?"

This idea sprouted from his understanding of modern electrical circuits. Guy equated the spell components as electrical components in a circuit, mana as current, and mage as the energy source. With that analogy, it made sense to him that the lines which connected the components must form a closed-circuit. The existing set-up left everything open; there wasn't a line joining the last component with the first component.

With that in mind, Guy redrew the spell circle. Before placing the components, Guy drew a star with the same number of corners as the number of components being placed. When drawing it, he never lifted his writing utensil; it was drawing in a single line. He then placed the components on the heads of the star and activated the spell.

Eureka! It worked!

Guy congratulated himself and performed an impromptu dance solo in the confines of his RoK.

After a quick 5-minute dance break, Guy calmed himself and started to create a |Fireball| spell using his newly developed method.

But Guy faced a roadblock. In nearly all the Source Components, there were fragments of Ancient Tongue that provided targeting. If Guy wanted to source oxygen from the air, he would need to include it in the Source Component. But the problem was he didn't know what oxygen was called in Ancient Tongue as it was a dead language.

"What to do now?" Guy muttered solemnly.