Rosedale Collision Altering Plugin [MV & MZ]

chaucer · 2023-07-11T05:40:12+0900

Introduction This plugin changes the default grid based movement of RPG Maker MV and MZ and allows Pixel Movement, and calculates collision based off of user defined geometry. With the Rosedale Collision Altering GUI Tool you can specify custom shapes for each tile in any tile set in your project, this allows for highly accurate collision detection, while keeping your project size small.Features Adds Pixel movement to your game. Break the grid limitations of the default RPG Maker MV/MZ Engine. Allows specifying collider data for each tile in all tilesets of your project via an easy to use User Interface. Easily specify a custom collider size, and offset for the player. Easily specify a custom collider size, and offset for any event for each individual page. Includes a traction system based on region ID for unique feeling terrains, I.E. walking across an icey lake can cause the player to slide. Plugin is highly optimized, so calculations are extremely fast, and the code base is very clean and easy to extend upon. Because the plugin is geometry based, it can open up lots of possibilities for future features. Planned Features 8 Directional sprite sheet support. Parallax image colliders Support for Damage Floors Support for Counter Tiles Support for Terrain Tags Support for TSR_Mirror.js Support for OcRam_Passages.js move to destination function( a gridless move option ). cliff jump feature How to use Screenshots Download Links Steam for Rpg maker MV Steam for Rpg Maker MZ Komodo Store

● ARCHIVED · READ-ONLY

Started by chaucer Jul 10, 2023, 08:40 PM 340 posts Page 13 of 17 View original ↗

Artille

#242 Sep 23, 2024, 12:58 PM Source

chaucer said:
For your first issue, sorry I will have this fixed in the next version! I will try to have it out asap after this message is posted... so check for an update within an hour or so and it should be fixed >.<; sorry for the inconvenience!

For your second issue, this occurs because currently, I do not ray cast for collisions, while I COULD do this i wanted this plugin to be as performant as possible.. but I suppose, I can add an option to improve collision accuracy by using raycasts to prevent scenarios such as this, however, it will most probably be at a slight performance hit( not much though, but really, really, low end pc's may notice this ).

As for the third issue! This has been added!! I have added region restrictions to the plugin, but it will also be improved in the future :) So keep an eye out if it's not suitable for your needs.

The last one was a suggestion rather than an issue, but I'm glad it got added, this will pimp the ride fosho :D

Thanks for the great work and plugin
riceyo84

#243 Sep 23, 2024, 06:32 PM Source

Well, I come up with this method for this event instead. I hope it won't lag if I have more than one
event.
riceyo84

#244 Sep 23, 2024, 06:36 PM Source

for the the double post. I don't know how to remove this post.
chaucer

#245 Sep 23, 2024, 06:54 PM Source
I'm assuming your using some kind of zoom plugin o__o; cause those hitboxes are super off xDD or is this a bug report?

EDIT: also for a more performant event... you could.. run another conditional branch around ALL of these other conditional branches, that checks if variable X is the direction of the event in question...
JavaScript:
$gameMap.event( ID ).direction() != $gameVariable.value( X )
then at the VERY end of this conditional branch, set variable x to the direction of event ID.
JavaScript:
$gameVariable.setValue( $gameMap.event( ID ).direction() )
and that will ONLY run the code, when the direction of the event changes!

But evenn without this, I beleive the code should be very fast already as it's not really doing a whole lot. ^^;
AquaEcho

#246 Sep 23, 2024, 08:22 PM Source

Minor request: Could you make the region restrictions also have a terrain tag restrictions option too?
ShadowDragon

#247 Sep 23, 2024, 08:30 PM Source

also, slippery regions arent working still, neither HIME_TriggerLabels.
somehow, it is always true when on the event which is false.

when in front, it should work. as this has a very specific trigger event when in front.
if required, I can give you the setup for testing :)
chaucer

#248 Sep 23, 2024, 09:18 PM Source

ShadowDragon said:
also, slippery regions arent working still, neither HIME_TriggerLabels.
somehow, it is always true when on the event which is false.

when in front, it should work. as this has a very specific trigger event when in front.
if required, I can give you the setup for testing :)

I did not add support for Hime_TriggerLabels ^^; I simply added it to my todo list for now

As for slippery regions, hmm... are you using any other plugins which may overwrite this? may i see your setup in the plugin parameters?

AquaEcho said:
Minor request: Could you make the region restrictions also have a terrain tag restrictions option too?

I can look into this ^^; it shouldn't be too difficult
AquaEcho

#249 Sep 23, 2024, 09:30 PM Source

chaucer said:
I can look into this ^^; it shouldn't be too difficult
It shouldn't be, it's just a change of code from $gameMap.regionId to $gameMap.terrainTag
I edited Yanfly Region Restrictions to work with terrain tags that way.
chaucer

#250 Sep 23, 2024, 09:48 PM Source

AquaEcho said:
It shouldn't be, it's just a change of code from $gameMap.regionId to $gameMap.terrainTag
I edited Yanfly Region Restrictions to work with terrain tags that way.
Yeah, sorry if that came out wrong, I was stating that it wouldn't be that hard, technically all i gotta do is copy the function that checks regions, and replace the region id check with the terrain tag check lol, it is indeed a simple task xD just it might take me a bit to get to, as my bug reports/feature requests/compatibility patch requests are quite large, but I did make some decent progress on it last week ^^;
kakatototo

#251 Sep 24, 2024, 07:21 AM Source

Thank you! The update was successful!
By the way, I was told that it was compatible with TSR mirror, but when I installed it, it looked like it had split into two parts.
The current version of TSR mirror is 1.4.0, but is this not compatible?
(The TSR mirror is installed below.)
ShadowDragon

#252 Sep 24, 2024, 09:08 AM Source

chaucer said:
As for slippery regions, hmm... are you using any other plugins which may overwrite this? may i see your setup in the plugin parameters?

Here is the simple region setup

Settings used at this point

and Plugin List as not all is used in this map

there might be plugin removed, and added as most of my own.
SRD_SlipDamaged is also region based as I need this for my HUD so this one is
crucial, so there are plugins reguired, but noting to slippery so far I see it.
chaucer

#253 Sep 24, 2024, 12:00 PM Source

kakatototo said:
Thank you! The update was successful!
By the way, I was told that it was compatible with TSR mirror, but when I installed it, it looked like it had split into two parts.
The current version of TSR mirror is 1.4.0, but is this not compatible?
(The TSR mirror is installed below.)

So... I've done a lot of updates since then. and I'm sure TSR has as well ^^; I'll need to take another look into this again D: lol

@ShadowDragon

the values you are using seem a bit high... it'd be hard to notice any sliding at all with them.. try lowering the values( this is why i allow for 4 decimal places ^^; something like 0.02 may be a bit more noticable. if that still doesn't work I may need to ask you to pm me a demo project, as In all my testing it works for me :(

Also wait what version of the plugin are you using, the latest is 1.13.1(or 1.13.2 I dont remember exactly... sorry lol too many updates last few days D: ). There should be a traction AND a friction value not just a traction value.. this seems like a version before 1.12.X( I think, that's where i added the improved settinngs for slippery regions... )
kakatototo

#254 Sep 24, 2024, 01:44 PM Source

Thank you. I'm looking forward to it.

I also have one more request about the collision tool.

1. I'd like to be able to work in a full-screen window.

2. I'm currently creating a 1920x1920 map with Parallax Mapping. If I try to set this with the collision tool, I have to set each 48x48 one by one.

If I could use the par tab (or create a new all tab?)
to display the entire image that's currently open and set the collision for that image, my work would be much more efficient.

I know you're busy, but I'd appreciate your consideration.
chaucer

#255 Sep 24, 2024, 01:52 PM Source

so... firstly, about this new request..

fullscreen is being worked on, and will be available in the next patch.

second... this ones not as easy. because of the way colliders are handled in the editor, they all need to be in a 48x48 cell... it's unfortunate... but for right now... this won't be added, I DO plan to add this in the future.... allowing to draw directly to a parallax map... but for right now... this is a HUUUGE undertaking...

I apologize....
ShadowDragon

#256 Sep 24, 2024, 04:41 PM Source

chaucer said:
Also wait what version of the plugin are you using, the latest is 1.13.1(or 1.13.2 I dont remember exactly...
using 1.13.2 as you can see in the plugin list.
but as the plugin allow 0 to 1, I though 0.4000 could work.
I try lower it 0.0200 to see what happens.

Edit:
I try with 0.0025 and friction of 0.0050
and 1 with , 0.0050 and 0.0025 for stopping, but there is a bug on it.

when walking and stopping works, but if you use 2 regions (maybe 1 too) and
you turn around, it shoots with high speed, specially with dashing (which I have on 2).
on Ice slippery that works awesome just speed up instead of slow down before walking
or slip to the opposite direction.

if you know Summon Night - Swordcraft Story 2, there is a slippery part, but this also
slide continues more, so I need more testing to get around the same effect of that.

but lower values definitely helps, specially below 100 to make it noticeble better and
make it work better :)
kakatototo

#257 Sep 25, 2024, 01:50 AM Source

Thank you! I'm looking forward to future updates!

There's one more thing I'd like to request in the next update.
I'd like a dialog to warn me when I exit without saving.
All the collision I spent so much time setting up has disappeared...
chaucer

#258 Sep 25, 2024, 12:42 PM Source

@kakatototo consider it done Q.Q so sorry...

@ShadowDragon

About gaining traction to quickly, if I'm guessing from your screenshot you provided with the regions you setup, if the player reaches the end of the slippery region, his traction becomes normal again. in which case, when you turn around, and move back onto the traction modified region, you will have started the move with full speed, as you started on a normal tile, so when you enter the traction region, you will keep the momentum. if I am wrong here, let me know but I've quite thoroughly tested this and couldn't replicate it other than in the situation mentioned.
AquaEcho

#259 Sep 25, 2024, 07:01 PM Source

Is it just me or does the new chaseTarget function not work (in MV)? The event just doesn't move at all. I wanted to test it out.
chaucer

#260 Sep 25, 2024, 07:17 PM Source

hmm.... thanks for the report, I'll look into this I might have broken path finding... again... for like the hundredth time Q__Q sorry, I'll look into it asap, that should definitely be working, by chance, the event is not completely blocked off from the player right?
ShadowDragon

#261 Sep 25, 2024, 07:31 PM Source

I started moving on the slippery tile and move back and forth, I might got out
before turning back, but I can send a gif for the result if needed as it's easy
to replicate.

edit:
most reconizeable on 2 regions only with different tranction and friction.
0.0050 tranction, 0.0025 friction (region 1)
0.0075 tranction, 0.0050 friction (region 2)

from region 1 to 2 and when you turn around, it has high speed.
best replicateable with dashing (this time on 1 in the parameters.

so it seems, 2 regions next to each other doesn't play nicely.
1 region works correctly.