@josaaku Thanks for letting me know! You're right it's not working since I forgot to have it check if QMovement is installed, only checks for QuasiMovement.
In the Collision map plugin, is there a reason <cm=FILENAME> is now using a ":" instead of an "="?
I changed it in line 125 so my 150 maps using the equals sign would work.
Does using "=" cause some problems?
Also I'm running into random collisions.
Using only plugins: Qplus and QMovement, create new map, walk around, bump into invisible object, then after a while crashes with this error.
@ZcheK Nope using = is fine. I had just changed the original to use : or =, but started leaving out being able to use =. Since using <cm:filename> just matched all the other notetags. So when making the new plugin, I left out the = part assuming no one was using = anyways.
That's odd. They might be vehicles. If you can, try to recreate it in an empty project, and send it over. Or if you're comfortable with JS and want to try debug it your self, then move the player over those colliders and use these functions in the console.
Code:
// Gets any character classes near the player
ColliderManager.getCharactersNear($gamePlayer.collider('bounds'));
// Gets any non character classes, pure colliders ( like tiles ) near the player
ColliderManager.getCollidersNear($gamePlayer.collider('bounds'));
I think it's the vehicles.
New Project - New map - Remove Followers- enable Qplus/Qmovement - Player can't walk on top left square - assign vehicles to middle of map - create another map - player can't walk where the vehicles were on previous map.
@ZcheK Yeah I think so if they're on 0, 0 when not assigned to any map. I'll have that fixed in next patch. I've also found a bug. After saving, you can't move until you close / reopen the game.
I'm using Aramis Sprite zoom to change the player's size depending on depth, but it doesn't seem to work with Q or Quasi Pathfind.
Are you still developing your depths plugin?
@ZcheK For the depths, I have the Y Scaling plugin nearly ready (codes been complete for like 2 months, just too lazy to write the help). But the height depth I won't be making / working on.
I was wondering if there already was a function in your movement plugin that checks for collisions? Like a function that gets two events or the actor and an event as parameters and returns true if they are colliding. Something like this would really help me with implementing a very simple ABS in my project.
That functions accepts 2 parameters; A collider as the first, and a function as the 2nd. Character objects are passed into the function, if the function returns true that character is kept, if it returns false that character is ignored, if it returns 'break' it'll stop looking for characters ( this is useful if you only need to check for a single collision, if a collision is found no need to continue checking other characters)
Here's an example from the collision checking for characters:
Code:
var collider = this.collider(type);
var collided = false;
ColliderManager.getCharactersNear(collider, (function(chara) {
if (chara.isThrough() || chara === this || !chara.isNormalPriority()) {
return false;
}
if (this.ignoreCharacters(type).contains(chara.charaId())) {
return false;
}
collided = chara.collider('collision').intersects(collider);
if (collided) return 'break';
}).bind(this));
return collided;
(From Game_CharacterBase.prototype.collideWithCharacter)
* Note that function returns an array of all the characters that it found.
Here's another example of getting all events that intersect a passed in collider:
Code:
var events = ColliderManager.getCharactersNear(collider, function(chara) {
if (chara.constructor === Game_Event && !chara._erased) {
return chara.collider('interaction').intersects(collider);
}
return false;
})
I then created a new project, copied all the files from that new game, to fill in the holes on the Master Demo.
The only thing I changed to the Demo was adding a guy who when talked to brings up the save menu, and I turned off quick testing in the QPlus file.
I am using 1.3.5.
When I reloaded a save file, the game crashed. I get these error reports.
TypeError: Cannot read property '17' of undefined
at Function.ColliderManager.getCollidersNear (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:984)
at Game_Event.Game_CharacterBase.collideWithTile (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:1508)
at Game_Event.Game_CharacterBase.collisionCheck (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:1489)
at Game_Event.Game_CharacterBase.collisionCheck (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QM+CollisionMap.js:320)
at Game_Event.Game_CharacterBase.canPixelPass (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:1443)
at Game_Event.moveTypeRandom (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:2575)
at Game_Event.updateSelfMovement (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:2553)
at Game_Event.updateStop (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:2544)
at Game_Event.Game_CharacterBase.update (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:1621)
at Game_Event.Game_CharacterBase.update (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QSprite.js:418)
Then the game reloaded fine the next few times. Then, after the loading was working, I saved again, then got this mostly similar error that said "19" instead of "17" for newer reloads.
TypeError: Cannot read property '19' of undefined
at Function.ColliderManager.getCollidersNear (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:984)
at Game_Event.Game_CharacterBase.collideWithTile (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:1508)
at Game_Event.Game_CharacterBase.collisionCheck (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:1489)
at Game_Event.Game_CharacterBase.collisionCheck (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QM+CollisionMap.js:320)
at Game_Event.Game_CharacterBase.canPixelPass (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:1443)
at Game_Event.moveTypeRandom (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:2575)
at Game_Event.updateSelfMovement (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:2553)
at Game_Event.updateStop (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:2544)
at Game_Event.Game_CharacterBase.update (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QMovement.js:1621)
at Game_Event.Game_CharacterBase.update (/C:/Users/Brian/Documents/Games/QMV-Master-Demo-master/js/plugins/QSprite.js:418)
And so on, make new saves, get the same errors, but with a new number.
Don't know what the error really is. Something with collisions?
What REALLY confuses me is why it reloaded those few times, but not any other time. Like... that is bizarre.
@TheTitan99 Thanks for reporting. I think that's probably related to the current save bug I found a few days back. It was suppose to be fixed in the initial version, but I forgot to add that file into the build list. The issue is that when you load a game it should reload the collidermanager, but since I forgot to add the functions dealing with loading, it doesn't happen. So it tries to load a grid (so 19 or 17 would be x or y positions) but since that grid is empty (since it hasn't reloaded), it crashes.
But I'll do a few more tests to be sure its all fixed. Update should be in a few days.
Fixed the default player / event collider config not being used
+ couple of other stuff
QPathfind 1.0.1
Small change on restarting pathfinds. Don't remember what it was for, if I finished the fix. But think it was related to QMovement compatibility
New Plugin
QM+CollisionMap - v1.0.x
Download - https://github.com/quxios/QMV-Master-Demo/tree/master/js/plugins/QM+CollisionMap.js
This is an addon to QMovement plugin. This addon adds a feature that lets you use images as a collision map.
Main difference from old version is that: white and transparent colors are now passable, all other colors are impassable. I made it this way because have "precise" colors can cause issues. For example, I have my monitor calibrated and have my gamma value changed. So if I make an image thats pure #FF0000, all red, and load it into MV and check the pixel color I'll get something like #FF0302 instead of #FF0000 because the gamma correction was applied when the png is being decoded. So only black, white and transparent are accurate colors. For this reason I won't be bringing back region maps since that requires exact colors.
That's too bad you about the region map part, as this is something I also really need from your old plugins. I'm confused as to how changing the gamma could affect how the game sees the colour at a code level? I set my monitor colours to something crazy just now, and your old region plugin still works. How could other editors, like Adventure Game Studio, not have this gamma messing up colour region detection problem, if this were the case?
@ZcheK Well I searched online and found that the color change is done by the browser when its loading the image files. And that lead me to answers saying I would have to manually decode images, or use some decoder like https://github.com/arian/pngjs to get the true/real values. As for the other editors, like I said this is down by the browser (when playing locally it creates a chrome browser). Not sure if those other engines also do that, if they then it might just be an issue with the chromium mv uses.
second(e97 in this case) - just empty event that alway there
when i enter map it's all ok - sound is there but,
i save game, then reset game(f5) and load the save = no sound
i close game completely then open again, load game = no sound
but if i make any slightest changes in my project(evan enough to just save project) then load that save and as result sound is back to place where its must be...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
