Knight's & Magic

[KrayZ33]

How about not attacking the other eye when it clearly worked the first time? (Turns off brain, enjoys.)

"Why did the boxer not use his knockout punch from the very first second!"

Making it sound like he can do whatever at any time whatsoever - noice use of dem brainz.
Obviously, the big ass monster was just standing there and not breathing fire that would melt about pretty much everything in a huge radius.

How about the protagonist who has never ridden a robot before suddenly showing up all known pilots, killing a giant monster that pawns platoons of knights, and impressing the friggin' king? Because he is a "genius programmer?" That very premise is a joke. Even Kraco, who likes this show, admits as much. (Turns off brain, enjoys.)

MC has the ability to control magic, magic is basically script writing, MC is very good at that - robot is controlled with magic, rewrites code and scripts to make it work without certain physical inputs

maybe you should actually turn your brain on instead of turning it off all the time when you watch it.
It's not dumb just because you say it is or because you'd have, in your ignorance, done something different

I don't know, I'm not liking the 2nd ep as much either (basically because he made the mecha look like it's not a 100t mecha anymore), but this amount of wanna-be clever is ridicilous.

Of course it's very convenient that magic is just like programming - otherwise MC would be useless and this show could've gotten a "this boy is just really good in controlling robots, just like in Code Geass" guy.
The biggest issue with this show will *probably* be, that no one will ever explain as to why he is in this world and why he regained his old memories.

And what's the point of a mecha series when there is absolutely no weight (as in actual force) in combat scenes.
I'll never understand that.

Yay - it swings a sword just like a normal person - but it looks more stupid. Oh and then there is that Space combat scene in the OP...ugh.

[shinta|hikari]

maybe you should actually turn your brain on instead of turning it off all the time when you watch it.

How about you speak with some respect? Ad hominem attacks won't get you anywhere and will only detract from your points.

You do know he was running around, on top, and under the behemoth, right? Why didn't he run up the neck, over the head, and then poke the eye out from there? What can the beast even do to hurt him when he is in that area? Why not take advantage of the enemy's blind spot because of its damaged eye and attack from there?

All of these seem perfectly reasonable plans of attack to me, compared to, for example, forcing a crying, distraught knight to pilot a mech, using a large-scale spell to attack the beast (which has a flame breath attack, as you said, but didn't think to use it then) head on, and then jumping in front of its face to manually electrocute it? See why I can't accept "it is difficult" as a reason to not stab the other eye?

I find it strange that there is a need to defend this part anyway. It was clearly done to prolong the fight and to show flashier attacks. Why? Because that is what this kind of story is all about. It's not about efficiency or making logical moves. It's about what entertains the target audience (clearly not nitpickers like me). Blinding both eyes may have been the most effective method to win, but that also means it is boring and predictable.

So you see, I do understand why it unfolded that way. And like I said, I am actually just nitpicking, and that this isn't a dealbreaker of any sort. Why defend this? Just chalk it up to action fanservice, much like how the Avengers always choose illogical and inefficient ways to defeat random grunts when just hitting them with straight punches and front kicks would be faster.

The premise is ridiculous. Coding doesn't work like that, even if you are a genius. You can't just touch code you've never seen before, instantly understand it, and then rework it in the span of seconds (Yes, seconds. See how the mech became faster and faster? He clearly said he was reworking his code to do that. For that to happen, he had to be optimizing code he just wrote a moment ago, which makes you wonder why he didn't write the more efficient version in the first place. WTF.) Even a highly skilled developer will have trouble fixing a defect from code he didn't write, much more reworking a foreign OS. What this guy did is beyond ridiculous and was clearly thought up by an author with no IT experience whatsoever.

Imagine it this way. What if, instead of him stealing and reprogramming a robot on the fly, he had been working on his own unit before this incident, making him familiar with how they work? What if, he already had experience editing the code from a different mech because he was given a (convenient) chance to? What if he merely rewrote his already tried and tested code for the stolen mech this episode? How much more convincing and realistic would that have been?

But you see, this kind of show isn't about realism or making perfect sense. The way it played out reeked of lazy writing, sure, but it also had the most "WOW factor" and flashiness. It is almost expected for stories of this ilk and might even be intentional. At the very least, it is acceptable.

It's not dumb just because you say it is or because you'd have, in your ignorance, done something different

It's not dumb because I say it is. It is dumb for actual reasons, which I stated above. And please ease up on personal attacks (the one in bold). Also, just because it has dumb parts does not make it not entertaining or a bad watch. A lot of stories have aspects like this.

[KrayZ33]

https://en.wikipedia.org/wiki/Ignorance

You do know he was running around, on top, and under the behemoth, right? Why didn't he run up the neck, over the head, and then poke the eye out from there? What can the beast even do to hurt him when he is in that area? Why not take advantage of the enemy's blind spot because of its damaged eye and attack from there?

Yes, he was running around because he didn't want to get eaten, crushed or die.
He even tried to get to his head once more but then the turtle spit fire in his general direction.

Also, what can he do? Maybe spit some fucking fire? Did you even watch the episode? How did the first Knight die again? Oh right - he died when he was stabbing that monster's eye.

The premise is ridiculous. Coding doesn't work like that, even if you are a genius. You can't just touch code you've never seen before, instantly understand it, and then rework it in the span of seconds (Yes, seconds. See how the mech became faster and faster? He clearly said he was reworking his code to do that. For that to happen, he had to be optimizing code he just wrote a moment ago, which makes you wonder why he didn't write the more efficient version in the first place. WTF.) Even a highly skilled developer will have trouble fixing a defect from code he didn't write, much more reworking a foreign OS. What this guy did is beyond ridiculous and was clearly thought up by an author with no IT experience whatsoever.

He could just be a pretty good robot pilot guy
Or Frodo, or Harry Potter.
Same effort, same story, same thing.

Also half of what you wrote is once again, ignorance. (funny enough that you even think they run like computers)

"why didn't he write the more efficient version in the first place" -> yet nagging about how unrealistic it is to code something so good and fast.

Even a highly skilled developer will have trouble fixing a defect from code he didn't write, much more reworking a foreign OS. What this guy did is beyond ridiculous and was clearly thought up by an author with no IT experience whatsoever.

Why do you even think this has anything to do with an OS or even unclean code? Building a Spell works like Code, but that doesn't even remotely mean it's as messy and complicated to either change or even look into it.

For now, all it means is that MC has the right mindset to get behind the idea of Magic more easily

[shinta|hikari]

What I meant by running around was, he had the ability to navigate the battle area with ease. If so, he could've just as easily gone for the other eye instead of pointlessly bashing his sword, which broke, against armor/magical force field.

The thing is, he already stabbed the right eye, proving he is capable of it. If difficulty really is the reason he didn't take out the remaining eye, then why did he choose a much more unreliable and difficult three phase plan in the end? Now that, is hard and dangerous. If the crying knight didn't get his shit together at the very last second, they'd both be dead.

About the other stories you mentioned, while I'm not that familiar with LOTR or Harry Potter, I'm pretty sure they didn't have coding as a part of their skill set. Moreover, if they also had such a stupid central conceit, I would also call them out on it. Unfortunately, I don't know these stories very well. I didn't watch Harry Potter, and I don't even remember the main plot for LOTR.

Quote:
"why didn't he write the more efficient version in the first place" -> yet nagging about how unrealistic it is to code something so good and fast.

That was a subpoint. If he really could do something that amazing, then he should be also able to do the latter thing. It wasn't important to my original point that the coding premise is bullshit and can be ignored.

Why do you even think this has anything to do with an OS or even unclean code? Building a Spell works like Code, but that doesn't even remotely mean it's as messy and complicated to either change or even look into it.

Because that is the entire premise for his skill. He is a genius programmer, and therefore a genius magician. Why? Because code works similarly to magic. This was mentioned in the show.

If his only edge is only having "the right mindset to get behind the idea of Magic more easily," he would not be inventing new weapons or becoming an ace pilot in the blink of an eye.

EDIT: As a clarification, I'd like to say that I'm not against the concept of coding skill = magic skill. I'm criticizing how they handled it in this story, when there were clearly better, more grounded, ways of doing it. The protagonist is waaay too OP for a really weak reason, and that's coming from a guy who likes Tatsuya.

EDIT2:

Quote from Krayz:
Also, what can he do? Maybe spit some fucking fire?

Wait, how can the behemoth spit fire towards the top of his own head? The attack I was describing involved jumping on the beast, running up its neck to the top of its head, and then launching an attack on the eye from there. Then he can just kick off the behemoth's face sideways. His acrobatics during the episode should allow him to do this level of movement.

[Kraco]

The biggest issue with this show will *probably* be, that no one will ever explain as to why he is in this world and why he regained his old memories.

This is an isekai genre series. Usually the setting is the MC retaining their memories, more rarely they don't but at least the audience knows the character is originally from our world (or at least a world more like ours than the whatever world they ended up in). Some series go to some lengths to give the transfer a reason, some don't do any such thing. It's just a reincarnation after getting lethally hit by a truck. There's no particular reason to explain it since it's the basic setting. You don't explain how there can be magic or pointy eared elves in a fantasy world either. There just are.

In short, it's no issue.

And what's the point of a mecha series when there is absolutely no weight (as in actual force) in combat scenes.
I'll never understand that.

There was some weight since the mecha couldn't take his jumping around, which was clearly out of specs for the mecha's design, and thus the joints started to break down.

[shinta|hikari]

Surprisingly, some isekais do explain why, not that it makes them inherently better or anything.

[KrayZ33]

The thing is, he already stabbed the right eye, proving he is capable of it. If difficulty really is the reason he didn't take out the remaining eye, then why did he choose a much more unreliable and difficult three phase plan in the end? Now that, is hard and dangerous. If the crying knight didn't get his shit together at the very last second, they'd both be dead.

now... This show is somewhat forgetable, I'll give you that... but you should at least have remembered that he couldn't and why.

[shinta|hikari]

Couldn't what?

The moment he stabbed the right eye, I was already saying out loud to grab another sword and stab the other one as soon as he can. Did I miss a defensive mechanism the behemoth has?

[KrayZ33]

Yes, haha

Well, it seems like you missed a lot of things.

The Turtle threw him off, the defence is a 360° lava breath that burns everything, and he couldn't finish him on his terms because the machine broke down - which is why he made use of that whiny traitor in the first place.

Wait, how can the behemoth spit fire towards the top of his own head? The attack I was describing involved jumping on the beast, running up its neck to the top of its head, and then launching an attack on the eye from there. Then he can just kick off the behemoth's face sideways. His acrobatics during the episode should allow him to do this level of movement.

And how will he remain on the top of it's head without holding onto something?
Try balancing an apple on your head, and then let your chin touch your chest.
And make pictures of it too!

Gn8 btw. Maybe we continue this tomorrow.

[shinta|hikari]

Just rewatched it. What I actually missed was the tail that could hit him from the back of the behemoth. However, instead of seeing your point, the rewatch only reinforced my belief that he could've attacked the eye if he actually wanted to. He had multiple chances of facing off with the beast and he even jumped over the flame in one of them, but he never aimed for the eye. In fact, he even said that he had to take out a leg or something, which was clearly armored. Why not the fricking eye?

And it's fairly easy to remain on top of its head because the head is wide enough. Did you even see how the mech moved? He was flipping all over the place and landing on his feet the whole time. Its balance can surely keep him 1-2 seconds on top of the head before jumping off, stabbing the eye, and jumping away/getting tossed off because the creature is in pain.

I guess the core of my complaint is WHY didn't he express intention to blind the behemoth completely? I'd get it if he just said, hey, it might be a good idea to blind it, but I can't! Instead, he mentioned taking out an armored leg that is as wide as a house...

[MFauli]

How about you speak with some respect?

It´s hard to respect your opinion when it´s that easily refutable, yet you continue to press that you´re right and everybody else is wrong. It´s especially frustrating to read when you make those crazy long postings, trying to shit on an anime that only had its second episode and thus lots of chances to explain away most current shortcomings.

But that´s even necessary, because, again, pretty much all of your points can be countered if you actually "turn off your brain", like Kray mentioned.

I feel dumb repeating myself the n-th time by now, but you really should wait for 1-2 more episodes before making these negative, critical assumptions, going into such perceived detail and ranting and ranting. If in 1-2 episodes no proper explanations are given, I will be the first to complain about it. But that´s then and we cannot see into the future. What we have no is a perfectly fine, enjoyable anime that didn´t do anything crassly wrong. Definitely not to the degree of "I have to turn off my brain to enjoy it".

[shinta|hikari]

It's not about my opinion. You can disagree with that all you want. It's about having respect for other people. I argued without attacking him or you, but you both have made direct negative comments about me. Attack the argument, not the person.

The funny thing is, Kraco agreed with me on some of the points I made, so no, it's not "I am right and all of you are wrong," but "This is what I think. Tell me what you think. Apparently someone agrees too."

Why are you guys getting angry (clearly so if you attack me) from having a discussion? If you don't want to respond then don't. If you do, then respond. There is no point telling me not to do so because I still want to.

The funny thing is, you say all my points can be countered, yet none of you have managed to actually refute my first 4 points even now. If you did, I cannot keep on posting in detail of why I think my position is right. Being refuted means being stopped from doing that. You are still welcome to try, of course. I have responded to every single defense you have made and will continue to do so.

One last thing to add, I don't think this is a shit show. But even if it is and I call it out, that is no reason to feel offended for liking it. People can like bad things, and that's okay. No one has the right to judge you based on your preferences. Heck, I like certain shows I'd consider shit.

EDIT: To provide some clarity, I believe I need to elaborate on what I mean by "turning off my brain." It doesn't mean the show is for idiots and that only idiots enjoy it. I have repeatedly said that this isn't a bad show, and I still maintain that. Not "turning off my brain" means approaching something not for enjoyment only but also with a layer of critique. This means questioning and pointing out parts that could've been done better, or are a little too unrealistic. Some call that nitpicking, including myself in my previous posts.

So tell me this, why are you two being so defensive when I myself am saying my criticisms are no big deal (except maybe the dumb premise, but a lot of premises are dumb) and don't make this a bad show for what it is?

[MFauli]

When someone writes huges postings about how bad something is, I kinda interpret that as "a huge deal". Sorry if I misinterpreted you, then. I took it the way I would post, and if something is not a big deal for me, you won´t get much more than a one-liner from me.

And yes, I also took "turn off my brain" as "a show for idiots".

Anyway, I can only repeat that I believe episode 3 and 4 will tell us all we know and if we should turn our brains off OR on. ;>

[shinta|hikari]

What can I say? I like to write.

[MasterOfMoogles]

All I could think about this episode was Kira Yamato.

Ernesti isn't anywhere near as good as him. Kira reprogrammed his mecha while fighting.

[shinta|hikari]

Was that Kira's first time riding a gundam then? I don't remember.

[MasterOfMoogles]

Yes, he was just a student I think?

[Kraco]

The funny thing is, you say all my points can be countered, yet none of you have managed to actually refute my first 4 points even now. If you did, I cannot keep on posting in detail of why I think my position is right. Being refuted means being stopped from doing that. You are still welcome to try, of course. I have responded to every single defense you have made and will continue to do so.

I actually addressed your not attacking the other eye point in an earlier post of mine, but I think you totally missed my post because KrayZ33 posted right after it and you concentrated on his post. So, I sort of feel like I tried to counter your point (that single one), but since you missed my hypothesis, I can't do anything about it.

[shinta|hikari]

I read it and I believe it was addressed by my succeeding posts about the relative difficulty of his final gambit over actually just attempting to poke the other eye out. I also specified that I was mostly criticizing how the protagonist made no evident attempt to destroy the other eye, or even said a one liner excuse saying it was too risky (He was doing a monologue the entire time, so this would not be out of place at all, not to mention an exposition-bot narrator explaining everything happening.).

[Munsu]

I think you're all wrong about the battle.

It was very evident to me that the only reason he didn't go to finish the fight quickly was because he was having a shit-ton of fun and wanted to test a lot of his theories.