https://linen.dev logo
Join Discord
Powered by
# ceramic
  • b
    No, but that's something you can certainly do using existing A* libraries
  • h
    @billowy-waiter-28954 , getting an error on running an empty project in clay; I updated my very old clay version t 17.7 and tried to build the template project and hit this error. Attached the full commandline flow incase that helps.
  • b
    It seems it fails to compile a shader, did you use some custom shader?
  • h
    nope. Just did --init newproject
  • h
    I did upgrade from 0.3.1 so I am not sure if that has something to do with this
  • b
    I think you didn’t run the command from the right directory, it doesn’t find ceramic.yml, check the logs
  • b
    Oh well you did re-run it again after
  • b
    Try to run the full command: ceramic clay run web --setup --assets
  • h
    That fixed my issue. Thanks!
  • h
    How would I use plugins in ceramic? I want to set up a simple main menu screen with buttons that link to other scenes. I see that there are ui & elements entries in the ceramic.yml, which I have uncommented. I am not able to import elements.Im in my scene class. what step am I missing?
  • b
    what do you mean by "not being able to import"? Do you have an error?
  • a
  • h
    Thanks got it to work now. The issue I faced was that autocomplete wasn't working for the Import elements statement and I assumed that its not working.
  • b
    haxe autocomplete can be a bit quirky from time to time. And in some cases you need to rebuild the project to be sure your changes in ceramic.yml are all taken into account
  • f
    Is there any way to have an additional ceramic.yml file that's only added depending on the variant?
  • b
    No, but you can add conditionals as explained in the reference (posted by @ambitious-knife-25690 just above)
  • f
    how would i use that to add files to spine export?
  • b
    You can't do that with the current spine export script. You could create multiple assets folders and include the ones you want depending on your variant however
  • b
    Copy code
    yaml
app:

    # ...
    if blah:
        +assets:
            - some/asset/dir
  • f
    i'm doing that already
  • b
    Then that's it. If you want to export spine projects to different assets folders, you either do that by using Spine command line directly (instead of ceramic), or you could also modify 
    ExportSpine.hx
    file in spine plugin so that can support custom paths (I don't need that myself so I don't plan to add that feature, but pull requests are welcome). You'll need to run 
    ./node post-install.js
    to rebuild plugin commands if you modify them
  • a
    For some reason when I ran 
    ceramic init --name myproject
    and got the resulting project
  • a
    I get an error saying 
    Library x is not installed
    ...
  • a
    eg hscript is not installed etc
  • a
    it exists in the 
    .haxelib
    folder
  • a
    but it doesn't exist in my global haxe install
  • a
    so I run 
    haxelib install hscript
    outside of the ceramic project directory
  • a
    and then I have to move on to the next library
  • a
    haxelib install polyline
    etc
  • a
    not sure why ceramic is using global haxelib when a local project exists
1...353637...124Latest