A (very) nice screenshot

wololo

Been followin' the console hacking scene since 2006, I'm an old guy so get off my lawn!

You may also like...

Hey, reader. The ads below are not "inappropriate", they are computer-generated "popular topics on the web". Data doesn't lie. Don't blame me, blame mankind.

10 Responses

  1. gdspsp says:

    take a break willow!!

    you deserve it. the project will keep growing and we will always appreciate you effort.

  2. Elfo says:

    Great, when tokens work right a bunch of new cards could be added…

    I hope more people develop themes, i’m not a big fan of wow myself, so I would like to see more ‘neutral’ cool themes

    Tks for the work =)

  3. NyghtcrawleR says:

    I made a classic theme :)

    Look to make some more themes in the future.

  4. Shishio says:

    Nice work with the tokens, bro!
    token(Wasp,creature artifact insect, 1/1,flying artifact)
    This breaks down to:
    token – signifies that a token will be made
    (Wasp – creates the name of the token or uses this instead of “id=”
    creature artifact insect – all subtypes?
    1/1 – n/m
    flying – ability
    artifact – ?Can’t figure out why it’s noted as artifact again…
    Am I close?

  5. wololo says:

    Overall you’re correct.
    The second occurence of “artifact” is the color. In Wagic, Artifact is unfortunately both a subtype and a color, and both need to be set for an artifact to work correctly :/

    @NyghtcrawleR : thanks for the theme :)

  6. MageKing17 says:

    Artifact… is a color? For what reason do you need such a hackish method?

    Also, artifact is a type, not a subtype (Equipment is a subtype of artifact, but artifact is not a subtype).

  7. wololo says:

    in Wagic’s code, there is no difference (yet) between types and subtypes. Note that this does not cause a huge problem since there is no subtype “artifact”, and the lists of “types” and “super” types are really limited and could be hardcoded somewhere if it ever becomes needed

    Artifact is a color in Wagic because I made a convenient confusion between “colorless” and “artifact” when I started coding. This is not a hack, only a wording issue. One word “artifact” stands for the “artifact” type, the other one is actually used instead of “colorless”.
    Wagic was initially built with the rules of the Revised edition, which made no real difference between “artifact” and “colorless”, which is why I mistakenly used the word “artifact” instead of “colorless”…

    Actually, most of the hacks come from the fact that I started coding with the rules of the revised edition (not the comp rules, but the 40 pages rules booklet…or rather…what I remembered from it). I am now slowly migrating the code to the latest rules, as we discover bugs…

  8. MageKing17 says:

    Ah, that explains everything. ;)

  9. LordBane999 says:

    Very well done Wololo, this homebrew you started is gaining speed quickly, and i like to add that despite the bugs there should just over 2000 working cards with your homebrew now, which is astounding because i don’t think even Magic Work Station (MWS) even had this many cards supported by it’s 3rd release.

    p.s. well not that important to me, do you think it may be possible to incorporate plainswalkers even if their a bit bugged? I was thinking about, and couldn’t you cheat their way in, by instead of using loyalty using the already use +/- counter abilities that you hard-coded? wouldn’t it be possible to just change the value tag each with their abilities, it wouldn’t be perfect but nothing ever is in a homebrew

  10. wololo says:

    LordBane999 : Thanks !
    The attack mechanism needs to be updated/rewritten for me to even start considering coding Planeswalkers.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>