Navigation

    forum
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Users
    • Groups
    1. Home
    2. PapaMufflon
    3. Topics
    • Flag Profile
    • block_user
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Groups
    • Blog

    Topics created by PapaMufflon

    • Cannot build extension when on it
      Technical Issues and Bugs • • PapaMufflon

      2
      2
      Posts
      3293
      Views

      This has been the case for a long time. I've worked around it by not having my builder move to the construction site if creep.pos.isNearTo return true.

    • Cannot create construction site for an extension on plain terrain
      Technical Issues and Bugs • • PapaMufflon

      3
      3
      Posts
      4373
      Views

      Aha - it has to be > 4 steps away from a source!? If I had known this in advance...

    • It should not be possible to delete creeps or even rooms from memory
      Technical Issues and Bugs • • PapaMufflon

      2
      2
      Posts
      3751
      Views

      The Game and the Memory objects are two completely separate things. Game gives you the actual objects, while in Memory you as user can store abritrary information. Basically it is a nice gesture from the game to automatically create the memory entry for you when spawning a creep which could as well be a task you have to do on your own...

    • Tooltip at sidebar->creep->body part is always 100
      Technical Issues and Bugs • • PapaMufflon

      5
      5
      Posts
      6094
      Views

      Chrome

    • Room.lookAtArea always returns plain terrain
      Technical Issues and Bugs • • PapaMufflon

      3
      3
      Posts
      5113
      Views

      I have/had similar problems with lookForAt. Strangely, it does seem to work when using the different method header. room.lookForAt('creep', 10, 10) <- does not return the correct information room.lookForAt('creep', room.getPositionAt(10,10)) <- seems to returns the creep correctly...