[XP] RPG Maker XP Online System (RMX-OS)

[KnightPL]

start the serwer and i have a problem  

C:/Ruby200-x64/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in 'require': 193: %1 is not a valid Win32 application.      D:/RMX-OS/Server/bin/2.0/mysql_api.so <LoadError>
from C:/Ruby200-x64/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in 'require'
from D:/RMX-OS/Server/RMX-OS.rb:83:in '<main>'

What is it?

I have windows 7 x64 home premium

[Blizzard]

You have installed Ruby x64, you have to install Ruby x86.

[exile360]

My project is now fully updated to rmx-os 2.0 with all the scripts I had previously. I did some extensive testing today with a friend, and found a few bugs.


The following are general bugs with rmx-os 2.0:

1) /ginfo crashes the game with the following error:

Spoiler: ShowHide

Which refers to line 1690:

        raise 'A'

Not actually sure what this 'A' is even supposed to be. xD
This happens whenever the command is used, regardless of whether the character actually has a guild or not. This is quite strange, I'm sure it didn't happen in the 2.0 beta that I tried.

2) Sending a pm gives the receiving player a "You have unread PMs" message, however does not display an ID. It's difficult to tell what the ID of the received PM is, and without it you can't read it (unless I'm doing something wrong here).

3) /global messages don't display in the chatbox. The command is received by the server and I think it even sends the message back, but the chatbox doesn't display it (yes I am using an admin account)

4) When trying to log in with a correct ID but incorrect password, the system displays a "Username does not exist" message even though the username exists and is correct.


The next few are bugs with my project specifically:

1) Attempting to trade crashes the game with the following error:

Spoiler: ShowHide

Which refers to line 3842

@message_window.update

Any idea what could be causing this?

Nevermind the above, I fixed it myself. I needed to update the line because of my Multiple Message Windows script. However, I have now run into another issue. Trading does work, however the person that ACCEPTS the trade request always disconnects upon trade completition. The person that sends the request is fine. The items still get traded, but I'm sure people would get annoyed from disconnecting every time. Not sure whether this might be a general rmx-os 2.0 issue or just my project, too lazy to try it out on a fresh client right now. I know it worked fine in the beta, though.

2) This isn't really a bug, but I'll list it here anyways. I have a common event which checks if Q is pressed, and if so, the questlog opens. The problem is that it opens the questlog while you're typing in the chatbox as well, thus stopping and deleting your message whenever you type q in the message. Is there any script command I could put in a conditional branch to check whether the chatbox is active (entering a message) or not, so I could disable this while it is?

And one suggestion as well:

Would it be possible to prevent the character from moving and interacting with NPCs while the chatbox is active (entering a message)? It's annoying that the character moves around and/or talks to an NPC whenever you use the arrows to scroll the chat or press enter to send a message.

Think that's it for now. Sorry to create more work for you... Cheers!

[Blizzard]

1) LMAO! I was debugging this and forgot to remove some stuff. Just remove the line. I'll reupload it.

2) Use /pmunread. "You have unread PMs" is a generic message and it would be confusing once there is more than one unread PM.

3) I'll check that.

4) I'll check that, too. Some stuff was changed as it used to display "Username or password incorrect."



1) Possibly a bug. I'll check if trading works fine on a default project.

2) You should disable it when the chatbox is active. Check @chatinput_window.active in Scene_Map for that.
[EDIT]Or check $game_temp.chat_active, that's simpler.[/EDIT]

3) Actually that already works. I am sure that this is another of your scripts messing with you. Try removing your scripts one by one to find out which one (make a copy of your Scripts.rxdata before you do so that you can quickly restore everything once you found the problematic script).

EDIT: All problems have been fixed, but I didn't check trading.

EDIT: I fixed the trading.

[exile360]

So much <333 for you Blizz. Everything tested and working, thanks!

Still can't put a finger on what's causing my char to walk and interact while chat is active, but I'll keep trying. Some scripts are a bit difficult to remove from the project, without creating other errors.
Edit: Ok, it was my Multiple Message Windows script again. But as to why it's happening, I'm clueless. Oh well, it's not gamebreaking anyway.

Btw, I see you updated the guild name sprites, and they look cool! The on-map chat is displayed on the tag now, though. xD I wanted to look into it myself and alter the position of the chat text sprite, but couldn't quite figure it out. I assume this would be a bit more complicated to code anyway, as the game would need to check whether a guildname sprite is active or not, and then adjust the chat text location. It's completely fine to just put it back the way it was as well and save the trouble.

[Blizzard]

Lol, I knew that I forgot something. I'll fix that right away.

EDIT: Alright, it's fixed. I also noticed that I didn't add a message when trading was canceled or successful. And I also added in the manual that Ruby x86 has to be installed, not Ruby x64.

[exile360]

Epic. I wish I could spam the level up button more often.

[Blizzard]

I also actually fixed another bug. When somebody's usergroup or guild status changes, their name sprites don't update. e.g. Somebody leaves a guild and their name sprite will still say that they are part of the guild. I fixed that, too.

[Xolitude]

Hey Blizzy, Love the new update But as I read through these replies I didn't see my problems so I think it's just me..

But, testing on my local net(My PC, and then another pc within my house), The chat double sends and it's a bit laggy.

Do you think that is just because it's local net? The server, and 2 clients all running on the same area?

[Blizzard]

It's not impossible. If the server can't distinguish properly between the clients or something is wrong with the network, it could be possible to receive a message twice.

[Xolitude]

When my friend tries to register, he gets this error^^^, and I don't at all.

[Blizzard]

1. Check in the database if the account was actually registered.
2. Turn on message log on the server and try to register again. See what happens and post the message log here.
3. Make sure that his client has scripts that are up to date. The RMX-OS v2.0 server will not respond properly to clients of RMX-OS v1.x.

[Xolitude]

1. Check in the database if the account was actually registered.
2. Turn on message log on the server and try to register again. See what happens and post the message log here.
3. Make sure that his client has scripts that are up to date. The RMX-OS v2.0 server will not respond properly to clients of RMX-OS v1.x.

1. Nope
2.

2013-07-06 22:58:23 UTC; -1 () - Incoming Message:
HAI
2013-07-06 22:58:25 UTC; -1 () - Incoming Message:
CON	2.0	1.0
2013-07-06 22:58:25 UTC; -1 () - Outgoing Message:
CON	0	2.0	1.0
2013-07-06 22:58:26 UTC; -1 () - Outgoing Message:
PNG

3. I believe so?

EDIT: It seems to be the new client/server version because I reverted back to an older  server version/client and it works just fine.....

[Blizzard]

Are these all messages after trying to register? Because there are only messages for entering the server, there is no message that a registration was attempted.

[Xolitude]

Are these all messages after trying to register? Because there are only messages for entering the server, there is no message that a registration was attempted.

Yes, these are all that I got when he hit register.

[Blizzard]

Turn on debug and error logging and try again. Post these two as well. You might want to delete them before starting the server.
I think that the connection might have died down for some reason and the message isn't properly received by the server (even though the server should report when a client causes a bug and crashes the connection).

[Xolitude]

Ugh it isn't really giving me anything.... I'll just wait until you make a new update /:

[Blizzard]

I can't make a new update if I don't know what the problem is since it's working fine with me. Try redownloading RMX-OS, maybe that helps.

[Xolitude]

Figures I'm the only one this happens on...

Nope, re-downloading didn't work... /:

[Blizzard]

I have reuploaded RMX-OS 2.0. I only updated some parts of the script to better support resolutions that aren't 640x480 that I forgot previously. Aside from that nothing was changed.