Page 1 of 1

jRose Online

PostPosted: Sun Feb 09, 2020 10:24 pm
by Luke
Hi Dear's i listening that jRose Client got Oro Map. Please server files and client of jRose. Thank You. :roll:

Re: jRose Online

PostPosted: Mon Feb 10, 2020 3:33 pm
by rl2171
Luke wrote:Hi Dear's i listening that jRose Client got Oro Map. Please server files and client of jRose. Thank You. :roll:


There are other planet maps on jRose as well, but there is no server files that I have seen.

If you want the client, go download it here:

http://www.roseon.jp/start/download.asp

Re: jRose Online

PostPosted: Mon Feb 10, 2020 4:44 pm
by Luke
Thank You rl2171, but you dont know/have any database.sql or npcs.sql ?
I cant host a server. When i click on file .bat then is nothing like TRose.exe @TRIGGER_SOFT@ _server 127.0.0.1
Can't open a Japan ROSE Online anymore.

Re: jRose Online

PostPosted: Mon Feb 10, 2020 8:41 pm
by rl2171
Luke wrote:Thank You rl2171, but you dont know/have any database.sql or npcs.sql ?
I cant host a server. When i click on file .bat then is nothing like TRose.exe @TRIGGER_SOFT@ _server 127.0.0.1
Can't open a Japan ROSE Online anymore.


I have not seen one personally, you will have to extract it yourself, if they have not encrypted it.

More than likely no one has built one based on jRose, so you won't be able to do one unless you program it yourself.

Re: jRose Online

PostPosted: Thu Feb 13, 2020 3:27 pm
by PurpleYouko
The last version of JRose that I have is about 2 years old and nothing is encrypted there. I was able to get into the VFS easily.

It does seem that a lot of the older VFS editors have stopped working properly but it has nothing to do with file formats changing and much more to do with modern computers running different runtime libraries in which many of the good old commands have been deprecated.
I often have to throw together some custom code to extract the things I want from a VFS these days

Re: jRose Online

PostPosted: Tue Feb 25, 2020 2:10 am
by wolfwing
That's actually not the case, it's because the extractors have been compiled with the AnyCPU .NET flag, meaning they'll run in 64 bit on modern systems. I should take the time to change the flags to 32 bit on all the .NET based tooling, that will fix the issue.