Immense Events
06-06-2020, 04:54 PM
Hey, I was wondering if you could implement this script into pokemon essentials? I realize it's a longshot, you'd probably have to reverse engineer the darned thing, as it is its own engine. But my friends at pokemon essentials (the devs) don't plan to implement a system where you can have immense events; they tell me to use extra events.
However, with extra events, you get the problem of overlapping events when a character event turns.
Here's my layout for example
=X=
=X=
ZYZ
^ ^
E E
= is a blank, passable area of the sprite. No event is located there.
X is the vertical impassible events, when the character is facing up or down
Z is the horizontal impassible events, when the character is facing left or right
Y is the main sprite/character itself, also impassible.
^ E is a seperate event (another character or object) that already occupies the tile the arrow is pointing to.
As you can see from this example, it only has four events to create a seemingly impassible creature. However, two issues arise with this:
You must set your graphic to at least 1% opacity to have the tile be collidable, meaning there's that 1% defect in graphics.
If the event deals with multiple types of characters, like creatures with different sizes, you'll need to accomidate for each individual character and all of it's associated blockade events. This could cause heavy slowdowns, as Pokemon Essentials is already slow in sophisticated games.
So, here's my question: Will you, or someone out there, modify this piece of code to work for essentials? I still realize it's a longshot, but I know someone who could possibly work with you, he is the dev, and only dev of pokemon essentials. While he points you to the correct code, you can work on that piece of code. I will give full credit for your work, as I will with other people's scripts.
However, with extra events, you get the problem of overlapping events when a character event turns.
Here's my layout for example
=X=
=X=
ZYZ
^ ^
E E
= is a blank, passable area of the sprite. No event is located there.
X is the vertical impassible events, when the character is facing up or down
Z is the horizontal impassible events, when the character is facing left or right
Y is the main sprite/character itself, also impassible.
^ E is a seperate event (another character or object) that already occupies the tile the arrow is pointing to.
As you can see from this example, it only has four events to create a seemingly impassible creature. However, two issues arise with this:
You must set your graphic to at least 1% opacity to have the tile be collidable, meaning there's that 1% defect in graphics.
If the event deals with multiple types of characters, like creatures with different sizes, you'll need to accomidate for each individual character and all of it's associated blockade events. This could cause heavy slowdowns, as Pokemon Essentials is already slow in sophisticated games.
So, here's my question: Will you, or someone out there, modify this piece of code to work for essentials? I still realize it's a longshot, but I know someone who could possibly work with you, he is the dev, and only dev of pokemon essentials. While he points you to the correct code, you can work on that piece of code. I will give full credit for your work, as I will with other people's scripts.
