A couple of graphical errors...

[mpuppy4]

I'm working on a project with Pokemon Essentials XP and I noticed a few things that I'm not sure how to fix.
The first, I'm not really sure if it's a graphical error (it's probably not) but every time I go from one connected map to another, it turns to night. When I go back, it turns back to day. I currently only have two connected maps, and I'm not sure what caused this, since I don't think I tinkered with anything (unless the connections txt file can cause this).

The second is this stupid thing where, in playtesting, the boundaries between tile layers, so there's this annoying line between certain tiles. Eh... let me show you what I mean. These are some of the places where I noticed it was worst.


See what I mean? How do I fix this? It bugs me, and it looks unprofessional.

 

[Rot8er_ConeX]

The second is this stupid thing where, in playtesting, the boundaries between tile layers, so there's this annoying line between certain tiles. Eh... let me show you what I mean. These are some of the places where I noticed it was worst.
View attachment 78504
View attachment 78505
See what I mean? How do I fix this? It bugs me, and it looks unprofessional.

This is caused by using a non-standard zoom factor.

As for your other issue, I can't help you

 

[mpuppy4]

How do I fix this?

 

[tustin2121]

The first, I'm not really sure if it's a graphical error (it's probably not) but every time I go from one connected map to another, it turns to night. When I go back, it turns back to day. I currently only have two connected maps, and I'm not sure what caused this, since I don't think I tinkered with anything (unless the connections txt file can cause this).

Check the metadata for your two maps. One of them is set to being outdoors, the other is not. Set them both to outdoors using the debug tools or by editing the metadata.txt file manually.

This is common if you deleted all the example maps and began making new maps from that, as the metadata from the example maps is still there, and RMXP assigns new maps the first unused id, which could have old metadata associated with it. In fact, while you're editing metadata.txt, you should clear out the other maps' metadata, just so you don't run into that problem again.

The second is this stupid thing where, in playtesting, the boundaries between tile layers, so there's this annoying line between certain tiles. Eh... let me show you what I mean. These are some of the places where I noticed it was worst.
View attachment 78504
View attachment 78505
See what I mean? How do I fix this? It bugs me, and it looks unprofessional.

This bug comes from playing the game at anything other than the standard zoom factor of 2x (or "M" on the menu screen). The only viable "fix" for it is to reimplement the way Essentials does map zooming to get rid of the rounding errors that cause this. Or simply disable the game's ability to change zoom size (if you look in the PScreen_Options script section, the section of code to comment out to do this is clearly marked, as apparently it's often done).

 

[mpuppy4]

Check the metadata for your two maps. One of them is set to being outdoors, the other is not. Set them both to outdoors using the debug tools or by editing the metadata.txt file manually.

This is common if you deleted all the example maps and began making new maps from that, as the metadata from the example maps is still there, and RMXP assigns new maps the first unused id, which could have old metadata associated with it. In fact, while you're editing metadata.txt, you should clear out the other maps' metadata, just so you don't run into that problem again.

Thank you, this worked! I should probably look into what all of the txt files do.

This bug comes from playing the game at anything other than the standard zoom factor of 2x (or "M" on the menu screen). The only viable "fix" for it is to reimplement the way Essentials does map zooming to get rid of the rounding errors that cause this. Or simply disable the game's ability to change zoom size (if you look in the PScreen_Options script section, the section of code to comment out to do this is clearly marked, as apparently it's often done).

How do I reimplement the zooming? I don't want to have to limit players to one screen setting.

 

[Rot8er_ConeX]

How do I reimplement the zooming? I don't want to have to limit players to one screen setting.

You don't. That would require a heavy recoding of how Essentials draws maps, and if you're gonna do that, you might as well make the game 3D.

 

[mpuppy4]

Welp, I guess I'm stuck with lines then. Weird, I never noticed that in any other Essentials projects.

 

[tustin2121]

How do I reimplement the zooming? I don't want to have to limit players to one screen setting.

Yeah, sorry, I meant that mostly facetiously. Like I said, most people would remove the options to resize the screen if they didn't like what the resizing was doing to their graphics.

That would require a heavy recoding of how Essentials draws maps, and if you're gonna do that, you might as well make the game 3D.

Someone tried that already: It's called "perspective mode" (MAPVIEWMODE = 2) and it looks horrible. :(

 

[mathiasjrg]

Welp, I guess I'm stuck with lines then. Weird, I never noticed that in any other Essentials projects.

This will usually be fixed once you compress the game (you're ready to release a demo or share it with others) :)
So don't worry about it for now <3