The Economics of Prophecy

There are swordsmen and wizards here attacking monsters.... It's real in this world in a way, but now all I can think of is a game story.

First of all, it's simply a swordsman. Swordsman deals damage to the monster by combining his Arm and Weapon's Attack. Let's say the attack power of a weapon (long sword) that you have with a legible arm strength of 10 is 10. The monster's HP shall be 100. I don't think of defense.

This is what happens when you honestly program this.

10 + 10 = 20: Calculate Damage

100-20 = 80: Monster's remaining HP

This is hard to understand for a person who writes a program. Because I don't intuitively understand the meaning of each number or expression. Besides, I have to write the same formula for every fight.

It would be a tragedy if a swordsman were to change gear to a Great Sword of Attack 15, or incorporate [Skill Attack +10 percent], etc. There is unlimited room for mistakes to enter.

Functionalize here. Define a function called weapon attack.

Function: Weapon Attack (Weapon Name) (Arm Power)

Damage = Weapon Attack + Arm

Monster HP Damage

Swordsman's attack will call this function.

Whoa, whoa.

Weapon Attack (Longsword) (Arm Power) = 80: Monster's Remaining HP

Whoa, whoa.

Separate the process called damage calculation as a function. Take it to the person you program and be clear about what is being done. No matter how many attacks you make, you don't have to calculate. And even if you add a skill, if you modify the function, it will be reflected in everything.

Next is the wizard. Define a function called magic attack in the same way.

Function: Weapon Attack (Magic Name) (Intelligence)

Damage = Magic Attack + Intelligence

Deal Damage

This is how battles are programmed.

Whoa, whoa.

Monster's HP Weapon Attack (Longsword) (Arm Strength)

Monster's HP Magic Attack (Fireball) (Intelligence)

Whoa, whoa.

Until now, it's what we do with our magic guidance. But there are limits to this. Risk of mistyping data, weapons or spells called arm strength or intelligence. Plus, mistakes get in like a warrior trying to use it with magic or a wizard trying to hit him with a cane.

To avoid that, it is the object-oriented idea to package the function and the parameters needed for it, as if it were the character itself. It would treat abstract calculations as if they were objects with entities.

"Simply put, the function…. Treat not only the magic character, but also the parameters entered in the magic character and the fundamentals of the call as one unit."

I went. Maityle puts her neck up.

Object: Warrior

Name: Female Knight

HP: 100

Arm strength: 10

Equipment Weapon: Longsword

Function: Weapon attack

Function: Dialogue "Curl it"

Object: Monster

Name: Oak

HP: 150

Arm strength: 15

Equipment Weapon: Sticks

Function: Weapon attack

Function: Capture

Whoa, whoa.

Female Knight Attack

Orc Attack

……

……

Female Knight "Come on, roll"

Whoa, whoa.

Ultimately, these two objects fight on their own. Orc wins, and I can combine commonality and personality until the female knight says "come on, roll".

Whether a character is leveled up and gains Attack, the weapon used is automatically reflected in an attempt to gain Power.

"I'm getting a little bit of it. Instead of making blueprints, it's like giving instructions to human tissue."

"Oh, that's exactly what I'm talking about. If the previous design of the magic guide was a single craftsman working with a combination of several tools, this would be like building a team of woodworkers, blacksmiths, and cloth makers to build a carriage."

"… for example, purchasing each ingredient at will when you need someone who needs it."

"Yes. You delegate authority to the craftsmen. Within the limits of his authority, his boss doesn't speak poorly. You understand boulders fast."

"... you have a little earache at the end. Well, I've noticed a lot since I got here..."

Mathier somehow became illuminated.

Anyway, Mathilde, who was at the top of the organization, understands quickly. The larger the organization, the more exponentially it has to decide. Naturally, one top can't make all the decisions. Ultimately, it would be ideal for the top to decide what the purpose is and who to leave the necessary work to.

Whether there are ten businesses or not, it is a ten-time decision to decide on each department manager. If there's a problem, you can just talk to one of the directors there. Of course, if you simply think about it. In fact, in the previous world it was also applied to visualization of management and so on when it came to business process modeling.

The difficulty of difficult things is not difficult. Many of them simply exceed the capacity of the human brain.

"Ideas for designers, not for magic guidance...... But isn't that a lot of waste? Negative in the sense of efficient use of magic."

Mathier notices the problem. There's a lot of overhead in the sense of magic efficiency.

"Oh, that's what I said. There will be no waste. However, considering that, if we go beyond a certain amount that has a magnitude of demonic guidance, efficiency will be better here. This way we can standardize parts, or more importantly, abstract."

The idea of a basic object.

It can be designed in the form of a base and its derivation, as in the classification of animals. If you think, for example, that female knights, orgasms and characters all have HP,

Basic Object: Organism

Name: X

HP: X

You can also set basic objects in a way like this. Individual objects inherit this and add the function Skills to derive it. Can be used for occupational systems, monster types, etc. Also, if you make objects like weapons or magic, you can do the same.

If an object can have an object as an element, it can also have a structure on the nest. A warrior can have a specific weapon object as a weapon. The special effects of a weapon can only be handled by the weapon itself. The user simply orders the weapon to "be effective" and the Flaming Sword burns the opponent and the Ice Sword freezes.

The management of the types and quantities of objects that can be held may be carried out within Warrior objects. That way warriors can also design naturally if they can't use magic. Of course, you can make certain skills stay special. For example, [Status Open]?

"On the scale of spirulitis... Yeah, that's not the perfect way to think about parallelism that Meer was saying earlier. The ease of parallelism increases if we bind not only the magic guiding characters, but also the numbers against them. Yeah, the way I think about it now, I can also think of abstracting the very concept of parallelism and incorporating it into the process of demonization"

"Oh, I can actually design an abstract process as well. It's like, for example, commonalizing the supply, operation, and activation of magic with just the basic parts of each, so that the individual contents are derived according to their own demonic guidance."

"I see all the magic guides go hand in hand."

"What's more, this can separate designs one by one, so it works great in designs with multiple levels of human involvement"

"It's seemingly far-fetched, but if you think about it, you can design magic on an unprecedented scale. Together with the micronization of the magic conductor circuit, the overhead can also be absorbed. It makes sense just to streamline the design on paper. Specifically!!

Mathier looks at me with her eyes shining.

"... no, that's why I have absolutely no control over it"

"Wait a minute. How do we achieve the separation of functions now?"

Gather knowledge desperately to Mathier's demands.

"... it's more about organizing each liaison than about consolidating it nearby in design. Specifically, set access permissions, only inside the object. Make a sort of distinction from the whole thing. Now, in human tissue, the harm of" boss's mouth "doesn't happen physically"

"Ricardo is already blessed with some of his men... Well, fine. Meer, Noel. Think about how you can apply yours now. Access is a line connection in the circuit after all..."

"It's a multilayering of the circuit's wiring. Hierarchize the circuits on the design diagram so that processing in and between objects uses a different hierarchy."

Meer said.

"Layering of circuits...... That's still at the possibility stage..."

Noel screamed.

The feverish argument quickly transcends my understanding. Well, in order for magic to flow, we need space around it, not closed circuits.

"I'll add a new circuit the way Ricardo said. I can't change the original circuit as it stands, though. For example, since aiming is the last step, it is suitable for attaching and adding to the cartridge as well. Full application is next."

Mathier said.

"That's huge. Somehow the knight hasn't been able to use his spirits yet."

"Yeah, that's why I'll concentrate on it and improve it"

"I see, and I'm going to save my life. As far as I'm concerned, I appreciate that."

"Beh, it's nothing like that. I only consider feasibility as a magic guide...... Well, if Ricardo exits in a strange place, my research will be delayed, too. Yes, I have one suggestion. I want you to tell Prince Craig. With me..."

Mayteer said a hell of a thing.

"No, no, that's on the boulder..."

"Oh, speed is our top priority."

◇ ◇

"You're going to figure it out."

I told Meer on the carriage back to Grand Duke's residence.

"Yes.... I hope so"

"What's up? If you're parallelizing earlier, you're already at a point where I can't help you. Maybe I don't know if Meer explained it to me..."

"No, not a magic guide..."

"Is there something wrong with Vinder?"

"No......"

Rarely did Meer mumble.

"Have you spoken properly to Master Alfina about this one?

…………

I was silent on the question of Meer, who lives with me and Alfina.