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

[Griver03]

yeah great when it works, im not at home so i can test it on tommorow 
n1 blizz like everytime 

[Griver03]

hi again 
the script works fine and looks good !

but can it be that many rmx-os scripts dont work with 1.17 ??
i had many errors with some scripts that works fine with 1.15 so idk ^^

[Blizzard]

Have you updated all your scripts?

[Griver03]

yep !
i had errors with who's online list,the abs controller and inividual kill counter...

and ates and global day and night didnt work right, but at this i was tired so i cant say 100% its a bug ^^

i use blizzabs 2.84, rmx-os 1.17 and controller 1.30 so yes 

[Blizzard]

I already replied in the Controller thread. I'll take a look at ATES and the GDNS script. As for the other scripts, post in their respective threads, I'm not the one who made them.

[Griver03]

big thx for checking the global daynight sys  and ates
and thx for replying
ill post the errors in those threads where they belong too.

[Blizzard]

I just checked ATES and GDNS and everything seems to be working fine. What is the problem you encounter?

[Griver03]

at first login te tinting works fine but after i relogged te screen was yellow like i didnt turn the tinting on but like i said i was tired ^^
so i try this night again to get this working
sry for that

[Blizzard]

You didn't set up ATES properly if you don't get the right screen tinting.

I have uploaded RMX-OS 1.18. It might fix some problems that you were having so you should try it.
Keep in mind that you should update following plugins as well:

• Blizz-ABS Controller


• Global Switches and Variables


• User Logger

[Griver03]

ok thx for the next update ^^ and like the controller i try it tonight 

[Griver03]

ok sry for that but this time you fail blizz 

1.18 is buggy !!!

when you login and then press F12 and relogin the error comes up...
when you login and close the client and then start it again and login the same bug...
when you create a char too...
yoo cant login more than one time and sometimes the bug comes even if you start the client and login or register a new user...

i tested it first with blizzz abs and controller after that only 1.18 and its the rmx-os not the controller or abs...

http://img837.imageshack.us/i/error1m.png/

[Ryex]

Stack Fail.

[Blizzard]

Don't use F12. It causes problems with scripts that use aliasing. You can get a script that prevents F12 completely.

[Noob]

hey, i was gonna tell u this a while back but 4got. common events dont work in rmxos. they crash all other players that are logged in. this occured both locally and globally.

[Griver03]

but the error occurs too when i just close the client and then reopen it and login 

[G_G]

How do I get a client's $game_party? You said something about the network class had parties but I didn't find anything on it.

[Blizzard]

If you have the Blizz-ABS Controller, you can access $network.party that has an array of all usernames in the current party. I can't remember if it includes the current play as well (I think it doesn't).

[RoseSkye]

Eh.
*MySql works
*Navicat works
*ruby.exe doesn't
*client doesn't as well

Ruby keeps terminating itself. I've tried all the solutions proposed to other people, but I assume I must not understand something. This is very annoying because I had read the FAQ and the Installation Guide up and down for 3 days and I still couldn't solve it. I've uninstalled and re-installed mysql and ruby 3 times. My ports are not blocked (I'm not using a router). MySql is up and running, and Navicat is obviously connected. I've no clue why my client nor ruby is connecting. I know you get this alot and I definitely tried to solve this on my own to no avail. This is my last  option. Perhaps someone can show me something I'm doing wrong or point me to some flaw in my workings.

cfg file: ShowHide

NAME = 'RMX-OS Server'
HOST = 'localhost'
PORT = 3306
RMXOS_VERSION = 1.18

LOG_MESSAGES = true
LOG_ERRORS = true
LOG_ACTIONS = true

DEBUG_MODE = false

MAXIMUM_CONNECTIONS = 50
LOGIN_TIMEOUT = 30
AUTO_RESTART = true
RESTART_TIME = 10
USE_IP_BANNING = true
PREVENT_ZOMBIE_CLIENTS = false
RUBY_PROMPT = true
OPTIMIZE_DATABASE_ON_STARTUP = true
DATABASE_CONNECTION_TIMEOUT = 60

SQL_HOSTNAME = 'localhost'
SQL_USERNAME = 'root'
SQL_PASSWORD = '12rosesfallingforyou'
SQL_DATABASE = 'rmxosdb'

INBOX_SIZE = 10

EXTENSIONS = [
]

[Wizered67]

I could be wrong on this one, but isn't 3306 the port set for MySQL to use? If it is, the 2 can't both use the same port as far as I know.

[RoseSkye]

I could be wrong on this one, but isn't 3306 the port set for MySQL to use? If it is, the 2 can't both use the same port as far as I know.

:| If you're right it'd definitely be a 'd'oh!' moment for me. All I need is confirmation now. FUUUUCK -.- it worked. I can tell Blizz is shaking his head in disgust now. I'm sorry, man...

Edit: Only problem now is rmxos client is not connecting (forcibly closed by the remote host) on 3306 and the server is offline on 54269.

SERVERS.push(['Localhost', '76.125.16.128', 3306])