• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Scalable Mage Knight

  • Thread starter Thread starter emperor799 at earthlink.n
  • Start date Start date
E

emperor799 at earthlink.n

Guest
I'd like to start by apologizing, I assumed you had a familiarity with Mage Knight, and didn't explain myself thoroughly

Well, its more than that. Most of the Titans are scalable: the Titan Artillery (as I said before), the Dragons, Tanks, (possibly) Chariots, the Iron Rain Hill Giant, and Gilgarsh. Along with the Doom Blade Orc Cyclops that comes out next month. I included the lvl 1-4 figs in with these because they cover the same issue, which I will try to better explain at the end:

My point was that of the Artillery & Dragons (the only scalable figs in the datafiles so far),

They are listed in deckbuilding as such:

Living Ballista
Living Ballista (Light)
Mortar
Mortar (Light)
etc.

Firstly, the Artillery versions that aren't (Light) should be (Heavy)

i.e.

Living Ballista (Heavy)
Living Ballista (Light)
Mortar (Heavy)
Mortar (Light)
etc.

Meanwhile, the Dragons are scalable to: (Ancient), (Mature), and (Young); the tanks to: (Heavy) and (Light); and the Hill Giant and Gilarsh are scalable to: (Ancient), (Mature), and (Kitling)

Secondly, my purpose in bringing this up originally is that I was wondering if there isn't a better way to list these. However, the more I talk about it, the more it seems a reasonable thing to do. If there IS a better way to handle these scalable figs, then by all means, let me know. Also, it occurs to me that when the Titans are fixed such that all their [for lack of a better word] "levels" are included, there won't be a way to sort them such that their individual versions are together and in order of point cost/strength.

i.e. it will end up

Gilgarsh (Ancient)
Gilgarsh (Kitling)
Gilgarsh (Mature)

Instead of

Gilgarsh (Ancient)
Gilgarsh (Mature)
Gilgarsh (Kitling)



--Kyle Turner
emperor799@earthlink.net


"You might say Reality is a result
of complex negotiations between
the observer and the observed.
But that is merely a point of view." -- Andromeda

----- Original Message -----
From: Rob Bowes
To: cardvault@yahoogroups.com
Sent: Thursday, February 20, 2003 2:52 AM
Subject: Re: [CardVault] Mage Knight


Ah! So the "scalable" issue is really the problem with the level 1-4 heroes
at the moment. Now I understand. Thanks for clarifying that for me. I think
what may be needed is an option to merge "identical" cards/models (using CV
authoring jargon), just like there's an option to merge duplicate
cards/models already. I'm going to think about this one a bit more, but it
might be something that should be added to V1.1 still (it's not a big risk
item, so it may be something I can still add).

Thanks, Rob

At 01:58 AM 2/20/2003 -0500, you wrote:
>Oh, sorry. "Scalable" was a term I first heard used with the HC oversized
>figs, but whether officially adopted or not, scaleable figs are those
>which can be given clicks of damage prior to play to lower their point
>value (i.e. cost)
>
>Some examples are the titan artillery and the Castle pieces which are not
>currently in the datafiles. I included the lvl 1-4 Heroes in this in my
>head, though they are not exactly" scalable."


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (559) 658-6995
Lone Wolf Development www.wolflair.com


Yahoo! Groups Sponsor
ADVERTISEMENT




To unsubscribe from this group, send an email to:
cardvault-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]
 
There's a difference between familiarity and detailed knowledge. :-) I've
played MK many times, but I have NOT used any of the "special" figs, which
is where the confusion is arising.

Thanks for explaining this in more detail, since I now understand what the
real issues are with the special figs. There's a conflict between showing
all the separate models that the user can select into his/her force vs.
eliminating the duplication. There's no "right" answer, so the data files
opt on showing everything. From your post, it sounds like you're beginning
to see this tradeoff and how there's no truly optimal solution for all
situations. :-)

I think there may be a way to have the duplication be readily eliminated
via a setting. I'll see if it works in the next few days.

As for the sorting, that can be readily handled. All that's needed is an
extra space before the opening '(' on the Kitling and Mature versions,
resulting in the increasing order Kitling/Mature/Ancient.

If I run into issues when working on the data files, I'll post them here
for comments and suggestions.

Thanks, Rob

At 12:55 PM 2/20/2003 -0500, you wrote:
>I'd like to start by apologizing, I assumed you had a familiarity with
>Mage Knight, and didn't explain myself thoroughly
>
>Well, its more than that. Most of the Titans are scalable: the Titan
>Artillery (as I said before), the Dragons, Tanks, (possibly) Chariots, the
>Iron Rain Hill Giant, and Gilgarsh. Along with the Doom Blade Orc Cyclops
>that comes out next month. I included the lvl 1-4 figs in with these
>because they cover the same issue, which I will try to better explain at
>the end:
>
>My point was that of the Artillery & Dragons (the only scalable figs in
>the datafiles so far),
>
>They are listed in deckbuilding as such:
>
>Living Ballista
>Living Ballista (Light)
>Mortar
>Mortar (Light)
>etc.
>
>Firstly, the Artillery versions that aren't (Light) should be (Heavy)
>
>i.e.
>
>Living Ballista (Heavy)
>Living Ballista (Light)
>Mortar (Heavy)
>Mortar (Light)
>etc.
>
>Meanwhile, the Dragons are scalable to: (Ancient), (Mature), and (Young);
>the tanks to: (Heavy) and (Light); and the Hill Giant and Gilarsh are
>scalable to: (Ancient), (Mature), and (Kitling)
>
>Secondly, my purpose in bringing this up originally is that I was
>wondering if there isn't a better way to list these. However, the more I
>talk about it, the more it seems a reasonable thing to do. If there IS a
>better way to handle these scalable figs, then by all means, let me know.
>Also, it occurs to me that when the Titans are fixed such that all their
>[for lack of a better word] "levels" are included, there won't be a way to
>sort them such that their individual versions are together and in order of
>point cost/strength.
>
>i.e. it will end up
>
>Gilgarsh (Ancient)
>Gilgarsh (Kitling)
>Gilgarsh (Mature)
>
>Instead of
>
>Gilgarsh (Ancient)
>Gilgarsh (Mature)
>Gilgarsh (Kitling)


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (559) 658-6995
Lone Wolf Development www.wolflair.com
 
>If I run into issues when working on the data files, I'll post them here
>for comments and suggestions.

By all means, I'd be glad to help.



--Kyle Turner
emperor799@earthlink.net


"You might say Reality is a result
of complex negotiations between
the observer and the observed.
But that is merely a point of view." -- Andromeda



[Non-text portions of this message have been removed]
 
You must log in or register to reply here.
Back
Top