Elliott's Forum Posts

  • Is there a way we can display collision polys in-editor ala C2?

  • You can convert the font to a spite font:

    https://www.scirra.com/manual/166/sprite-font

  • I can't wait to try them out - will be downloading later! Thank you Jeremy

  • Surely you could just use the browser object to just get the browser URL and then break the game if it doesn't match your own site? Hell you could even force the page to redirect to your own page.

  • An ethereum plugin would be very interesting!

  • To be honest I always assumed that buttons appeared in the raw HTML as they exist outside of the canvas - this would make adding the above code very straightforward. I must have been dreaming though, as they don't in the quick test I just did... now I'm very confused!

    Ashley or R0J0hound for confirmation?

    Merry Christmas!

  • They wont, FTP is simply the method with the export will be uploaded to the website

  • Yes - you'd simply export the game as HTML5 and then upload the files to your site's public_html via FTP or by your hosts file manager (i.e cPanel)

    You can then use any password protection you would use on a standard webpage; though most hosts will offer a simple though basic password protection feature. Alternatively you can just delist the page from search engines, hide it from crawlers, and give the page address a gibberish title and then share that with your audience.

    If you're using C3 you can create a ephemeral preview that exists for as long as you maintain the preview with Remote Preview

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I managed to get a workaround with the following:

    + System: On start of layout
-> mobiPath: Spawn deathBullet on layer 0 (image point 1)
-> deathBullet: Set angle toward (mobiPath.ImagePointX(2), mobiPath.ImagePointY(2))
-> deathBullet: Set distance to mobiPath.Width

+ deathBullet: Bullet distance travelled = deathBullet.distance
-> deathBullet: Destroy
[/code:1dd5rjdu]

I still have no idea why the first example didn't work - in my head they do the same thing

  • Hey guys, could someone check my logic - I have no idea why it's not working!

    + System: On start of layout
-> mobiPath: Spawn deathBullet on layer 0 (image point 1)
-> deathBullet: Set angle toward (mobiPath.ImagePointX(2), mobiPath.ImagePointY(2))
----+ deathBullet: Bullet distance travelled = mobiPath.Width
-----> deathBullet: Destroy[/code:wbxm5uy9]

I'm trying to make a spawner create an object that will travel the distance of its parent before being destroyed - but the above code doesn't work

Any insights would be greatly appreciated

    I think Construct has a lot of potential. It is great for producing prototypes rapidly. For smaller Indie companies, I think Construct could even be used commercially if Scirra put more emphasis on the export and distribution process. C3 needs a native mobile share function and an export to Android/iOS with maximum work flow efficiency. That way more companies would use this software.

    I agree that C3 needs a native share function* - but the reality is that this benefits indies more than companies; agencies and corporates will simply write their own functionality and bundle it as a plugin.

    * Do the web share functions just not work when wrapped?

  • If you export the project as HTML5, you can edit the buttons by editing the index.html in a text editor like Brackets or VS Code

  • I don't quite have the time time to comb through am 11,000+ line CSS file, but I will save you some time by saying that you can style Constructs HTML elements by simply targeting their element followed by their type - rather than a class or id.

    For example:

    Textbox:

    input[type="text"]{ /*Your CSS*/}

    Button:

    input[type="button"]{ /*Your CSS*/}

    And so on.

    If you require more granular control, you can style the elements by inlining the styles through editing the exports .html file

    EDIT//

    Having read your latest post - I would simply suggest editing the exported HTML file to include the material CSS as an external stylesheet and adding the classes and extra attributes outlined in the tutorial to the existing form elements (being careful not to change the ids, as I assume that's how Construct knows how to tie in event logic)

  • Yes* - however once it becomes a C3 project, you will only be able to open it in C3.

    *Assuming it doesn't use a 3rd party plugin that the developer has not ported to C3.