Jump to content

Houp

YLANDS TEAM
  • Content Count

    381
  • Joined

  • Last visited

Posts posted by Houp


  1. Hi,

    popped out tiles should be easy to delete. They should be selected after popping up. (so you need to just press Delete)

    OR

    you can hold ALT when dropping script tile to already occupied slot. It should replace the one underneath.

    -----------------------------

    Quote

    I think this 'one click to edit' should stay but using the delete key should still delete the tile while in this mode.

    I think you (and I am sure I would) would hate it. You would delete your tiles while editing them by mistake. -> However, behavior change 1.10 - 1.11 is there by mistake. We will think how to improve it.

     


  2. 10 minutes ago, Mello1223 said:

    Hi. it looks great, and I will definitely like to look at the script, but the attachment cannot be downloaded. a friend who wanted to download a set of my tools also reported a similar problem to me

    I see. I tried to share it with google drive. (link is in the previous commit)


  3. Hi,

    maybe a feature "Regenerate ocean surface" is something which may be helpful for you. It will fill holes in the terrain. Water volumes are meant more for pools/lakes on the land.

    regenerate ocean.PNG

    Placing underwater animals is now quite limiting to ensure that AI will work correctly for them. You may try to place sharks in the safe spot first and then move them to more narrow places.

    Houp

    • Like 2

  4. Hi,

    I know there is probably lack of documentation for this feature so I will try to explain here:

    Normally only Global storage, Entity storage and Game logic storage have unique IDs and they will update from the placed compositions. Any other game logic objects and all entities will not update. There is no simple rule what should update and how. (missing/new objects in new composition, already modified objects in current game etc.)

    For easier use of Game set we have introduced Script module game logic. It can reference only Game logic objects and only those with no world representation (eg. no Particle effects, Barriers, Trigger zones, ..).

    1. Create Script Module Source
    2. Reference all GLs you want to have updatable
    3. Click Export in properties of Script Module Source
    4. Create composition with Exported Script Module.
    5. Past it in the different game B
    6. Fill references to objects in target game/world (like Particle effects, Barriers, Trigger zones, .. entities)
    7. ....
    8. Go back to the game with Script Module Source
    9. Update referenced Script Module game logic objects
    10. Export it again
    11. Place it in the game B
    12. It will update local copy of script module with new values but it will keep all existing references to local objects (from Step 6)

     

    ----

    Last note:

    In VS, custom instructions/variables can have different scopes (Member, Module, Global)

    If you want to have access from other objects in game B to instructions/variables from the Script module then set scope as "Global"

    If you want to have access just among GLs from script module to each other then chose scope "Module"


  5. On 6/4/2022 at 5:46 AM, Mello1223 said:

    @Houp btw, what is the difference between "on fix update" and "on update" event in event listener?

    "On update" triggers once per frame -> you have 80 FPS then it triggers 80x in one second. You have 30 FPS then it triggers 30 times per second.

    "On fixed update" does not depend on your FPS. It will trigger the same amount of times per second each second. It may trigger even 2 or more times per one frame.

    "Fixed update" is used for physics/movement of objects with collisions.

    Those events are not Ylands specific. You can for example check: https://learn.unity.com/tutorial/update-and-fixedupdate#

     

     

    • Like 1

  6. Hi, it depends:

    Time trigger + script delay with small time delay may result with more than 1 triggering per 1 frame. (one long frame on slow PC)

    Event listener + On Game Update event will trigger only once per each frame.

     

    So:

    A) you are fine to track movement once per second -> I would use Time trigger

    B) you want to track movement once each frame -> I would use Event listener + "On game update"


  7. Hi, those should be 2 separate issues. At the moment I can answer the part about templates and destroying referenced objects on export..

    Problem is caused by custom variables/instructions with scope set as Global in scripts of referenced objects by templates. I agree that the error message could be more informative.

    1. For Entity templates you should not need to have those variables/instructions available in other scripts -> the game prevents you to reference scripts which will not be available in playtest/after export.
    2. Bigger problem are Group templates where is valid to have references among objects in the referenced group but it will still prevent you to playtest. At the moment it is not possible to use "destroy on export" feature for Group templates. :( It will be fixed in next update.

    scope.PNG

    • Like 1
×