Powder Sim 2

  • greymatter
    26th Jun 2013 Member 0 Permalink
  • jacob1
    26th Jun 2013 Developer 0 Permalink
    @cyberdragon (View Post)
    although actually there is no difference, you don't actually need any check at all, but put BOUNDS_CHECK if you want. BOUNDS_CHECK is just defined as true in case we decide to actually put back the check in the future. It isn't needed because of that 4 pixel wide area at the edges of the simulation where elements aren't allowed.
  • wolfy1339
    26th Jun 2013 Member 0 Permalink

    Who wants to code fancy graphics from Powder Sim?

    also what is the element PIND? It was causing me compiling errors until i just deleted it.

    Who thinks we should delete LOVE?

  • cyberdragon
    27th Jun 2013 Member 0 Permalink

    PIND...it's mine...Powder Indestructable, I'll look into it. And NNNOOOOOOO...NOT LOVE!

  • wolfy1339
    27th Jun 2013 Member 0 Permalink

    @cyberdragon (View Post)

     ok,

    some more details: Identifies itself twice in ElementClasses.h and ElementClasses.cpp

  • cyberdragon
    27th Jun 2013 Member 0 Permalink

    Mine doesn't, replace ElementClasses

  • wolfy1339
    27th Jun 2013 Member 0 Permalink

    @cyberdragon (View Post)

     oh yes it does! it defines itself twice.

  • cyberdragon
    27th Jun 2013 Member 0 Permalink

    WHERE?!

     

    #define PT_PIND 191
    #define PT_LIND 192
    #define PT_GIND 193
     
    elements.push_back(Element_PIND());
    elements.push_back(Element_LIND());
    elements.push_back(Element_GIND());
  • jacob1
    27th Jun 2013 Developer 0 Permalink
    deleting an element will not open up any space, so I recommend you don't, unless you are planning on not having it compatible with tpt and changing everything. Since if you did fill it in with something else it would break any saves that already have LOVE and they would show your element instead. And you can't shift back the id's 1 to make an extra space either, that's worse. There's enough room for 256 elements, that should be enough ... and if it isn't, it's possible to increase the amount of possible elements to 512 or something but it will require a new save format and i'm not doing that all myself to give to you.

    I see no reason for PIND to define itself twice, you might actually have the file in there twice somewhere causing the problem. Also it's not really indestructible, it's just a copy of EQVE. So either add the exceptions in BOMB, DEST, SING, CRAY, AMTR, LIGH(?), and CONV, or just enable EQVE instead.
  • xetalim
    27th Jun 2013 Member 1 Permalink

    @allmoddersofpowdersim2:

    PLEASE

    if you add an element give it the right element ID....

    if you want to compile and have 2 elements with the same ID you get errors, we dont want that
    AND

    do the directives right

    the GIND element had the PIND element directives

    and ALMN had the RBTY element directives.....

Locked by jacob1: lock requested