Skip to main content

Browse GamesGame JamsUpload GameDeveloper LogsCommunity
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
Kadajah27 days ago(+1)

Hey Michelle, how are you doing?

First, I apologize for the errors you encountered. After analyzing the log you sent (and thanks for that!), it looks like a failure occurred during the map's `update()` call, seemingly involving a function from `VisuMZ_1_EventsMoveCore.js`. I added that plugin to my project and was able to reproduce the error; I then added the missing variables to my plugin's setup to satisfy `EventsMoveCore`'s movement update requirements, so I believe that is now resolved.

I also noticed an error regarding the creation of the Player 2 sprite on Player 1's screen, and vice versa. This happened because, when I originally designed this plugin a long time ago, I couldn't solve the dynamic update and movement issue without causing an FPS drop (hence the "Parallel Lives" concept—players weren't supposed to meet, lol). However, time has been on my side, and I now know how to fix that problem, so it is resolved as well.

I also added an update function for when you use parallax backgrounds on the same map; now, they update dynamically on both screens instead of just one. Previously, the parallax would load when the map started but stop updating, which caused a black screen.

I also improved the camera to allow characters to get closer to the map edges without leaving the view due to RPG Maker's built-in grid limits.

I included a small, working demo file to demonstrate interactions between the two players on the same screen; I hope it helps.

One note: DSX (Dual Screen X) is a bonus included in the package, but it modifies the exact same classes as Parallel Lives. They weren't designed to work together, so errors may occur if both are enabled simultaneously; personally, I don't recommend using them together.

Regarding your design, we’ll need to give some thought to the HUD issue, since Player 2 isn't treated as a second player (`gamePlayer()`) but rather as a movable event; significant, perhaps radical, changes might be required to make it behave the way you need.

Please download the V30 zip file again; it already includes all the fixes I mentioned here.

Reply
Michelle Rakar20 days ago

Hi, thank you so much for making these updates so quickly! It looks like the issue of the players not showing up on each other's screens and the parallax backgrounds displaying as black are both resolved and working now for me! That makes a lot more sense now. Thank you for that additional context and for including the demo project file too. That's been super helpful to really understand how it's working a lot better.

I'm still having a couple of plugin conflict issues on my end, though, unfortunately. I made a fresh new project file to test and added just these plugins:


And this is the error message I'm still receiving:


It seems to only happen when the PluginCommonBase plugin is turned on, even though the error itself mentions VisuStella's EventsMoveCore plugin.

I did notice some weirdness in my original project with the VisuStella plugin, though, so it's possible they're both conflicting in their own ways. I'm using the Events Move plugin in my project primarily for spawning events on the map, so I did notice those are still only showing up on player 1's screen instead of player 2's, so I'm not sure why that is either. I know plugin conflicts like VisuStella can be tough to decode with the obfuscated code, but I really appreciate your help with this!

Reply
Kadajah18 days ago

Hey Michelle, how are you doing?

The error isn't all that different from the first one we encountered; the plugins you're using are trying to update a variable that my plugin doesn't use, which leads to the error:

[Cannot read property 'forEach' of undefined] Basically, the plugins are trying to read a list that doesn't exist.

Creating compatibility with VisuStella is a real headache; even if I manage to fix the issue now, a simple update on their end can cause new problems to pop up.

I made a small tweak to my plugin's setup to force the use of the variables I created within the `update()` function. This might bypass the error, but it will likely prevent some procedural generation features from other plugins from working.

Please download the `ParallelLives_test` file; it includes the code modification designed to skip this error.

Another issue is that my plugin generates a second screen, but the other plugins aren't aware of this and weren't designed to handle two display environments. So, unless the plugins are built to inject elements into both screens, some procedural generation might fail. This is undoubtedly a bigger problem, and I'd love to help you solve it, but I'll need more information. Would you like to add me on Discord for more direct support?

Reply
AboutFAQBlogContact us
Copyright © 2026 itch corp · Directory · Terms · Privacy · Cookies