Cilerba

Blurp. I think you VMed me in like September...XD" Sorry for not responding. I sort of just got back to checking PC.

=]

It depends. It'll probably be a while before CNG can finish it, since there's an awful lot of coding involved, but if he thoroughly debugs it and follows through with it, then it'll probably be a lot less buggy than Essentials. That only leaves the issue of having to re-learn all the methods, scenes, etc. It's a bit of a gamble, but I wouldn't go as far as to say it's a bad choice though.

Sorry. I hate making suggestions that take forever to implement. But, that's all that comes to mind. And Essentials has a way with pestering developers for no apparent reason.

That's a pretty random error message. It doesn't even tell you what went wrong. I sent you the whole kit didn't I? The safest and surest thing at this point is probably to port your stuff over into the kit I sent you. And just in case, only port a few custom scripts at a time (starting with whatever menu system you're using, of course), and see if any of them break it. That way we can narrow down the cause.

<33333

ok, you're welcome.

oh, i put a method call in scene map called pbGetMouseInput. it was what i was working on for that clickable sign thing. removing it should fix the issue.

ok, i'll be waiting.

i mean go through and find any script changes you ever made that you want to keep, paste them in a text file or something, and replace your scripts.rxdata file with the one in the kit I sent you. it seems like a compatibility issue between scripts, but it's hard to target as is. just keep a copy of the scripts.rxdata file you're currently using just in case.

do you have all of your custom scripts and whatnot in a separate script section? it might be easiest to move all of you custom scripts somewhere and just put the scripts.rxdata from the one i sent you into you kit (but keep the old scripts.rxdata just in case).

can you think of any changes since the last time we messed with the resolution (which has bee a while)?

that's pretty odd. then there must be something else interfering with it. probably. is it the same error when you copy both over as when you just copy one?

well, it should have just been the PokeBattle_ActualScene script. But maybe try PokeBattle_Scene too?

well...i could zip it up and send you the whole project. maybe it got messed up when copy/pasting it. you could just copy/past the whole script section in, and it should work. at the very least, you could see that it works at that resolution. here's the link: http://www.sendspace.com/file/5el382

I have a question then: have you made any changes to PokeBattle_Scene (not ActualScene, which I sent you)? The error says there's an undefined method/variable adjustbattlespritey, which makes sense, since I just did a search on my kit and the only occurrences of that are in PokeBattle_ActualScene and PokemonSprite.

Have you changed kits since the last time I helped you? I made all of the changes in the same kit as the last one I used for changing the resolution. And just to make totally sure, you completely got rid of the old PokeBattle_ActualScene, replaced it with this one, and then compiled just to be safe right? That error is one of those un-descriptive ones that doesn't really tell you what went wrong, just that something did.

All right, let me know how this works. It still doesn't support double battles though, like the last one. And let me know if I messed up the shadows for flying pokemon, since I forgot until the end and had to fix them real quick. Here's the link: http://www.sendspace.com/file/yq43v4 I'm sure you can tell where it goes by the name of the txt file ;)

Great (and beautiful) minds think alike, dontcha' think? :D

ok, cool. I just started a little on it. I'll let you know when I finish.