R0J0hound's Forum Posts

  • That just means your browser is clearing cookies/cache when it restarts. Why?

    Maybe it’s a browser setting that does that. Maybe your hard drive is low on space and windows is automatically cleaning up temporary files, which include cookies, to free up space. Or maybe it’s some other program/browser addon that’s triggering the cleanup.

    You’d just need to check around.

  • With an async function you can’t return a value, you’d just set a value somewhere from the function.

  • Here’s one possible solution.

    First step is to find the lowest x and y of each group of blocks and subtract that from the xy of each block. Next you can add the xy pairs to dictionary for one group, and remove them with the other. If it’s empty both sets of blocks are in the same shape. 

    Var xmin=0
Var ymin=0

Every tick
— dictionary: clear

For each block1
— set xmin to loopindex=0?block1.x:min(xmin,block1.x)
— set ymin to loopindex=0?block1.y:min(ymin,block1.y)

For each block1
— dictionary: add key (block1.x-xmin)&”,”&(block1.y-ymin) with value 0

For each block2
— set xmin to loopindex=0?block2.x:min(xmin,block2.x)
— set ymin to loopindex=0?block2.y:min(ymin,block2.y)

For each block2
— dictionary: remove key (block2.x-xmin)&”,”&(block2.y-ymin)

Dictionary: is empty
— blocks are in same configuration

    Only time that wouldn’t work is if multiple block1’s were in the same position.

    Another option is to convert both sets of blocks to arrays. You’ll need the bounding box (min,max xy) of both, then populate the arrays. Then you could loop over the arrays and check if each is identical in both. As a quick easy out you can check the sizes first.

  • Unique workflow. That’s probably the kind of thing you’d need to do yourself as you’ve noticed it’s very time consuming to do. Even if it could be done in an automated way, the possibility of renaming the type/behavior or variables in general would make it infeasible to do.

    What you can do is create a project to copy from that you build as you go since there would be some actions and conditions used more than others. Overall that would let you try that workflow more and firsthand find pros and cons with it.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Don’t mind at all. It was meant as a public domain template of sorts. Just be sure to change the plugin id.

  • It’s short enough and simple enough you can try changing it and see. I thought defining the paths with sprites was simpler. I won’t be making an array version.

  • It’s just built on top of the sdk template which specifies version 2 in the c3 addon.json. I’d assume the rest of the template is v2 compliant, but it’s not reasonable for us to find and update parts of the template that may use v1 stuff. Beyond that my goal is just to get it working.

    You can look at the runtime portions of official plugins in the browser console but the edit time portions are minified.

  • I finally fought through the build process to make a plugin. It's based on the drawing plugin template but a bit more complete so maybe it may be useful to you.

    dropbox.com/scl/fi/c8nu95x3r8mdjw15z7dcw/convexPolygon.c3addon

    It renders convex polygons, and lets you change the array json of the points at edittime and runtime. Also when it does it changes the size and origin so that the bounding box/quad is as small as possible around the points.

    I'm not encountering the bounding box issue you had.

    When you add it initially it's white so you'll want to change the color right after to add it. I wanted to set the color with code, like the spritefont plugin does, but that doesn't seem to be an option somehow. Also it looks like you have to manually add ACES to set the blend mode with events.

    I almost got used to modifying multiple files to add something. There really is a lot of tedium that you have to wade through to even get to the point of doing something interesting. The loop of modifying files, packaging them into a c3addon, loading it into c3 and restarting c3 to test it really takes a toll. Getting past the vague errors to even get the plugin to install was the biggest breakthrough I'd say.

    I found the SDK manual helpful in parts but overall hard to navigate, but that was mainly due to the sheer amount of different classes. When I got the the runtime portion the SDK docs stopped being helpful and had to resort to browsing code in the debug console. Turns out at runtime the renderer function names start with lowercase letters while edittime starts with Uppercase. Also it found it odd that the draw function had to be done differently at runtime than edittime.

  • Have you tried looking on discord? There were more active addon devs on there. There probably isn’t a simple graphical example, but you may be able to get some ideas by looking at existing plugins.

    I’ve looked into making a plugin a few times but decided the process isn’t something I wish to work through.

  • I mean, the last post was instructions of a way to do it. If I made a capx it would only follow those instructions. I’ll defer to other people’s solutions in the meantime. There’s a lot of other things vying for my time currently.

  • You do not have permission to view this post

  • There isn’t a best way. There are many different ways like I roughly listed in the previous post, each with pros and cons. But realistically you’d just pick one.

    Create a sprite and call it node. Give it two instance variables: path and index. You’d then place instances of node on the layout in the shape of the path you want. Next you’d set the instance variable values. You’d set index to 1 for the first node, 2 for the second, and so on. You’d then set path to the same value 1 for all of them. You can create more paths later by just having different values of path.

    Next you need something to follow the path. Create a sprite and call it mover. Give it two instance variables: path and target. Also give it the bullet behavior.

    In events you’d then do something like 

    Start of layout 
— mover: destroy

On click
Node: path=1
Node: index=1
Repeat 10 times
— create mover at (node.x-loopindex*32, node.y)
— mover: set path to 1
— mover: set target to 1

For each mover
Node: path=mover.path
Node: index= mover.target
— mover: rotate 100*dt degrees toward (node.x,node.y)

Mover: on collision with node
Node: path=mover.path
Node: index= mover.target
— mover: add 1 to target

    You can change the rotation speed by changing 100*dt. You probably want to change the bullet speed too. Too fast with too slow of turning will prevent it from being able to reach the next node, but that’s easy to tweak. You can change the amount and spacing of the movers in the event that creates them. You probably want to delete the movers once they reach the end of the path somehow.

    As an exercise you could also stretch a sprite between consecutive movers to avoid visual gaps.

    Edit:

    Third party plugins are useful, but users seem to avoid them because they don’t like that the people that made them don’t usually stick around till the end of time to fix possible issues that come up from browser or construct change. You’re already using c2 that could possibly break from a browser change although that’s not very common. As to if third party plugins make it harder to port? That’s a question for those who do the porting.

  • I’m already unfamiliar with the game and the formula. But I’m assuming the formula is mostly correct.

    I’d want to verify this, but assuming it’s correct this should give to probability that exactly k of the unknown n dice are the same value.

    Prob(n,k) = fact(n)/(fact(k)*fact(n-k))*((1/3)^k)*((2/3)^(n-k))

    That’s with wilds. Without wilds 1/6 and 5/6 sounds reasonable.

    Normally for the ai to decide to say Liar or not it looks at the probability that there are at least k dice with the same value.

    So for example if there are four unknown dice.

    The probability of at least 2 being the same would be:

    Prob(4,2)+prob(4,3)+prob(4,4)

    And the probability of exactly two being the same would be

    Prob(4,2)

    The formula with the summarization I gave before would find at most or

    Prob(4,2)+prob(4,1)

    Which doesn’t seem right.

  • You shouldn’t need to be working with CssPx at all. The bounding box/quad is already in layout coordinates and the renderer takes layout coordinates as parameters. Also layout coordinates don’t change when the widow/scroll or the layout size changes.

    So for example in the draw() function of your plugin you could do something like this to draw a triangle centered on the object.

    const x=inst.x, y=inst.y;

    Renderer.convexPoly([x,y-50, x+50,y+50, x-50,y+50]);

    The bounding box would be based on the objects size and center so ideally you’d change the object size so that the bounding box would be tight fitting around the points of the polygon.