Please stop lying about me.
RAM:
I'm actually convinced at this point that you seemingly oppose everything I type on principle. It feels like whenever I post anything in this thread it's only a matter of time before RAM comes to make up more stuff trying to "counter" it.
I said that the aethergems were fundamentally a good idea, but flawed. I made a better design, and argued for it., I frequently pointed out why they were inferior to the alternative. But I do not recall saying that they were bad, just flawed and could be improved upon. Please cite a specific quote where I said that it was a bad design. For contrast on how I define this, I regard the Titan as a bad design. THAT would have been a waste of an action.
More to the point, I often criticise all proposals when I vote. It just so happens that I generally find may many many more problems with yours than I do with anyone else's. Most everyone else's proposals are actually viable. Yours lately have a habit of being fundamentally unworkable and missing a bunch of design elements in the final product. More to the point, these inevitable failures often get lots of votes, and thus it proves necessary to warn people that they are voting for something that will fail, which they generally do, generally for the reasons that I have stated. Such as Falcons not being found, tamed, trained, and mutated with a single action, we got the one thing that made it possible at all, a mind-control spell, a fully functional and usable one, unlike what happened with plant growth, when mind control wasn't even mentioned in the proposal and without it we would have gotten slightly enlarged birds that eat our trainers. We basically got the one thing that wasn't mentions and lost everything that was, and it was the best outcome that we could have hoped for, better even. If the G.M. wasn't constantly going out of their way to reinterpret your designs into something remotely plausible then we would have ploughed into disaster so many times that it isn't funny.
The problem is that I feel almost obligated to show why the stuff you post is blatantly false.
And yet you do not do so. Please cite precisely when you showed "why" a post of mine was blatantly false. On the few occasions that you have done so I have actually been quite receptive. Like when you pointed out that the falcons were actually modified permanently, and not just suppressed temporarily. On that occasion you actually made an argument and actually got a result. Mostly you just make completely baseless accusations. Such as saying that what I post is blatantly false.
But that's at the cost of my time and the general state of the thread.
The whole thread choosing designs, I try to argue for why designs should be chosen. If there were any actual content to any of your arguments then we could maybe resolve something. If a point has been argued I am willing to drop it, but nothing is addressed...
Sure, most people can probably see right through your stuff, but there's always that miniscule chance that someone may have their opinion shifted by your baseless assumptions.
You keep making these empty claims about my flaws, nd yet have no evidence to back it up. Surely if my offences are so abundant you can find at least one that you can go into a respectable amount of detail on?
I'm fine with arguing/discussing this kind of stuff with other people, but really. Other people don't just make up stuff to counter every single sentence of what feels like every post I make. Like for a recent example, I disagree with Fallacy, but at least he makes an effort to actually support his arguments.
Exactly, I have no issue debating with Fallacy for exactly those reasons. I and Fallacy both support our arguments. You do not. Please post a quote of you supporting an argument against me and me being unreasonable about it. The thread is not going anywhere, feel free to grab a quote, any quote. The thread isn't deleting itself in a hurry, you really ought to be able to find one somewhere.
"My design is broken, just spend a revision to fix it" "Spending revisions to fix designs is bad, for vague reasons that I am not going into but are very real so long as they don't apply to me"
When anyone can tell this is, as always, blatantly untrue. Like, if you actually read the supposed "hypocrisy" I said, which is:
And it's always a good idea to not have to use Revisions to fix a Design.
Not if we fix the Protector, which uses canons. And it's going to be exponentially harder for them to increase the effectiveness of the spell.
Note how, unlike what RAM pretends it to be, this statements work together.
Using revisions to fix a design is unavoidable. We generally shouldn't make designs with the intention of also using revisions that turn to fix the design. It's always a good idea to not have to use a revision to fix a design is true - we shouldn't intentionally put ourselves in situations where we have to use a revision to fix something.
But the Protector is buggy only because of a poor bug roll. We had a [3-1] for the bug roll, which is mostly just bad luck.
Okay, that is fair, completely lacking in foundation, the protector was obviously too ambitious and was always going to need revisions to be a tide of armour rolling over the fields. The fact is we got lucky that the G.M. decided to just ignore parts of the proposal. But still, I am willing to believe that you know little enough about what a design can actually achieve that you thought that you were submitting something that would work as you wanted in its initial form. It is worth pointing out that the average roll of a 6-sided die is 3.5. "3" is as close to average as is possible. "-1" is a consequence of the design. So you are lying or wrong about it being "just bad luck" as that is not, in fact, bad luck. That is a design going exactly as one could reasonably expect. Protector got a ridiculously average roll and came out with features just completely absent and still works about at well as can be expected. And it did not win the turn for us, because it was the wrong design at the wrong time. Which is exactly what I claimed it to be. but you are correct that, assuming that you were mistaken about the protector's ability to be a functional design, thus did not explicitly design it to need a revision, that you asking to revise it is not evidence of you operating under the idea of designing to require the use of revisions.
On the other hand, that is a very specific interpretation that you are using...
And it's always a good idea to not have to use Revisions to fix a Design.
You do not actually specify any intent. You specify a situation. Specifically that of having to use a revision to fix a design. A situation that we now find ourselves in if we need to use a revision to fix Protectors. We obviously don't, protectors are kind of pointless, they get about as much as they can out of their role in the current circumstances so no revision on them would help significantly, but if we did need one then that would be the situation that we find ourselves in as a consequence of their design. It is just really sad that you do not understand the word "blatant". When your entire argument rests upon a very specific interpretations of a very vague sentence then that is not blatant.
But then we come back to whether you actually designed the protector to require a revision.
I honestly don't trust that Evicted would ever be willing to make the Protector Cheap on the first design regardless of what we do. Also, usually Cheap/Expensive don't really make a difference for bigger things.
So you expected it to be expensive, and regard a 3 as a bad roll. 3 is as good as precisely half the possible options, that is a very likely thing to happen. It was, in fact, by your own standards, very likely that your estimations would not be met. Your estimates were "expensive" at best. You even specifically mentioned the "First design" with reference to "Protector" thus implying that there would be future "Protector" designs. And yet apparently this is not an example of designing to require a revision? Even though you plainly regard the next step up from "expensive" to be requiring of a revision:
So here's a list of the flaws I could see at a glance:
- It's Very Expensive!
- No anti-magic resistance?
- Poor propulsion - The engine's great, but the small wheels can easily crack and sink into the ground. The lack of suspension means no cannon fire on the move. The gears make turning a very slow + arduous process and are prone to breakage at high speed. And more. We could probably fix all this with a single revision.
- It's slower than a horse. Related to above (gears/suspension/wheels and the like) and could probably be fixed with a single revision along with the above.
- Magegem battery only allows up to 1 minute of unpowered operation
- AS-HAC-1 emplacement provides no protection to operator, requires an apprentice operating it, and doesn't support armor making the operator very vulnerable. Also only useful for anti-air.
- IDE can't be retrofitted to other designs. We should probably just implement it in future designs; I don't think a retrofitting revision is worth it.
- Small amounts of ammo. Not a huge deal since the HC1-E is a pretty big cannon and can do a lot with small quantities of ammo.
The ones in bold should probably be fixed first. I think we should prioritize the expense, but revisions fixing more than one problem would be great and may be possible. The Protector is (probably) useful as it is, and fixing a non-expense related part would probably not do much at Very Expensive.
Anti-magic resistance is annoying, but not the end of the world. Their anti-magic still needs to be consciously cast by a wizard with the spell and our soldiers can always just wait it out or depart the vehicle when disabled.
The wheels/gears/suspension/mechanical propulsion stuff is all annoying, but we can live with it. On the bright side, a single revision could potentially fix all of this and radically progress our knowledge of engineering in this area. Seriously. It's a huge opportunity - suspensions, gear turning, better wheels.
Maybe we could implement treads.
So you do not believe that cheap is possible. You believe that very expensive requires a revision, and you do not think it is appropriate to make designs that require revisions... So you do not believe that expense rolls exist? I am really having trouble figuring out if you are deliberately lying or really don't understand something about this situation, by your own statements the only possible outcome was a single specific expense level, as though expense levels are certain. Do you perhaps think that The G.M. was unjustified in giving the design anything less than a +2 on the expense roll?
Not to mention the 6 other things that need revising on a PERFECTLY average roll with no comment about the G.M. misjudging the design... You are absolutely certain and sure that this design was not intended to need a revision?
And for another example, let's take another look at your post:
Personally, I feel that recharging a magem in an hour would be optimistic, a day would be pessimistic, a week would be something that we ought to be prepared for, five minutes would be a thousand birthdays at once, and "enough to maintain a third of our current rate of fire" would be something that we can potentially hope for, but really shouldn't.
Note how RAM is using this as evidence, yet it's literally just baseless assumptions. And I mean "baseless". There is no base to this statement. You're just saying "Well, I bet this is going to be bad, so therefore I'm right at saying it's bad!" like in nearly every argument you've made recently.
I clearly stated that it was my personal opinion. It is very very clear. How vague can "Personally, I feel that" be on this issue? I made a very clearly personal judgement on what was plausible and used it as an example to explain my own thought on the matter. And it is not baseless, it is based upon my personal assessment of the situation, and I made that very clear. I don't even regard that as "bad" as you are accusing me of. I regard those rates as being pretty good. Well, the optimistic one, and the pessimistic one is generally bad, but that is what pessimistic is. Really, you are citing the exactly how clear, concise, and descriptive I can be at my best and saying that I refuse to provide tangible arguments. These are the figures that I think are likely and why I think they are not good enough., And, as it turns out, wer, by some miracle, got even better results, they can barely be considered batteries anymore and still haven't lost any storage capacity. I blame the G.M. for being too soft. That said, they still do not generate charge quickly enough to keep pace with our firearms. So it turns out that even a success well beyond my expectations was insufficient for our purposes.
So yes, I freely admit that my very clearly labelled expectations were inaccurate. However, that is not actually any sort of problem. Somehow you managed to be completely wrong here. I did not use it as "evidence", I used it as a hypothetical example, very clearly so. It was not "baseless assumptions", it was estimates based upon my experience with the thread and the magics involved. Accumulating magic seems to be something that takes a while and now we have more than we know what to do with. I did not think that it would go "badly". I thought that it would result in a large increase in our magic generation, I just didn't think that it would be sufficient to replace magem replacement, so the proposed implementation could be improved upon and would not meet the very specific requirements that I was responding to, that of its function as a power-source for fully-functional and self-sufficient armaments. In the respect that it is completely accurate to the extent that it is advertise then yes, it is exactly like the majority of my recent arguments, however it, and my recent arguments, are completely unlike your description. So you are, in this instance, completely wrong.
Also in response to the "A mist cloud would likely be blown away":
Nope.
See our "channeling mist" spell which explicitly works against wind by being continuously generated, which is the same thing a Tower of Mist would be doing. Actually, I just know you'll say "NUH-UH" then make up another thing saying that technically it doesn't work. But let me pre-emptively prove you wrong:
Obscuring Mist: Cloaks a squad in a fog cloud, hiding their numbers and equipment, and making them harder to hit at range.
Variant (Channeled Fog): A denser form of Obscuring mist, continuously generated.
Revision: Channeled Fog [5]
Well I do so love making things up, lets make pretend that the G.M. said something like this:
@EvictedSaint: How effective is our channeled fog against their wind spell? Is it still getting blown away or are we capable of maintaining constant cover on our troops?
It's about even. The fog is continuously generated from the casting mage, so as long as the troops trying to hide are downwind it will more-or-less cover them.
And then let's all share a delusion that channelled fog is, in fact, affected by wind. Or, you know, maybe it just likes being downwind, because our apprentices smell nice... How many times do you have to outright lie about me making things up without ever doing anything to support your claims before your slanderous tastes are satisfied?
Rather than just casting a cloud of mist and moving it about at will, our Mages have learned how to continuously conjure the fog. This means the cloud will grow larger and larger the longer they stand still, and moving will leave a trail of fog. This leaves more ambiguity as to how many men are hidden in the mist, and natural wind can't dispell the fog quickly enough to leave the men uncovered. Only time will tell if the Moskurg's control of the weather will be enough to dispell our cover.
And I don't believe they've ever actually countered this. It's just not particularly useful. But even if I missed something and it's not viable because of wind (if you do want to say this, please bring evidence for once), do you know how we can fix that? More mist. Do you know what makes a lot more mist? Towers of Mist.
I have already stated that a tower of fog would result in a giant "shoot here" arrow stretching up into the sky above the conjurer. Wind, surprisingly enough, does blow fog. True, channelled fog does, indeed, persist, due to its continuous generation, but it is still blown and it thus still completely fails to obscure the location of the person creating it.
Now, are you quite done lying about me?