Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

ConSoft

2
Posts
A member registered Aug 02, 2025 · View creator page →

Recent community posts

I found where the issue is coming from however I don't know if the fix I did worked or not as I'm not a coder in any way and I'm unfamiliar with how your plugin works.

By comparing the old plugin to the new one in Visual Code Studio, I was able to pinpoint which change between the versions causes this error. On line 558 (556 for v.1.1.0), there is an if statement checking the following:

"if (video._source && !video._source.paused)"

The old version looked like this:

"if (video._source && video._source.paused)"

By removing the bang operator and changing it back to the old if statement, the plugin functions as normal (so even if there's a Wait or text command in between loading a video and playing a video the video will play as expected).

Again, due to how unfamiliar I am with coding I don't know what this if statement is for or why this change fixes it (assuming it's not breaking something else), I at least hope my investigations on this will help you stamp out this issue.

(2 edits)

I believe there's a bug with this plugin. If there's something that interrupts the event processing, like a wait command or text box, videos won't play even if they're loaded.

Here is how to recreate the bug

1: Make a new game project.

2: Only use this plugin.

3: Make a map event, can be triggered by anything, but for this example make it triggered with the action button.

4: Use the plugin commands or scripts to preload a video, set an id, then play the video.

5. Start a new game and trigger the event: the video should play normally.

6. Go back into the project and put a "Wait" command of any length in between the preload video event and play video event; for this example set it to 60 frames.

7. Start a new game and trigger the event: the video will not play.

This is using the most up to date version of the plugin 1.2.0.

Edit: I tested with both mp4s and webms. The problem persists even between the two.

Edit2: I tested using the old 1.1.0 version and it did not have this problem.