Is it me or I just ran out o' luck? - Renewal Technical Support / Bug Reporting - WarpPortal Community Forums

Jump to content


Photo
- - - - -

Is it me or I just ran out o' luck?


  • Please log in to reply
6 replies to this topic

#1 Berecus

Berecus

    I made it Off Topic

  • Members
  • 86 posts
  • LocationBehind you
  • Playing:Ragnarok Online
  • Server:Currently on Hiatus

Posted 29 May 2013 - 10:08 AM

My chars wont show and i dont know why i used the right client im sure and picked the right server, but still...and it says that my skillsescript.lua:14712:table index is nil...
Not sure how to fix this...
  • 0

#2 DrAzzy

DrAzzy

    Really Azzy? Already?

  • VMod Retired
  • 15606 posts
  • LocationNew England
  • Playing:Ragnarok Online
  • Server:Chaos-Clandestine Society

Posted 29 May 2013 - 10:21 AM

Reviewing previous threads you've been posting in, I would suspect that your installation is severely mangled, probably due to letting the patcher apply some of the patches from 2011 when you had that problem, and you now have a mix of up-to-date files and 2011 vintage files.

Two approaches:
Delete patch.inf - let it patch from all the way from 2011, which should sort out whatever happened to your data files

- or-

Uninstall RO, delete the RO folder, then reinstall RO.

Also - in the future, these issues should go in the same thread, so I don't have to look up the previous threads where it's explained how you go to where you are now.
  • 1

#3 Axylus

Axylus

    Too Legit To Quit

  • Members
  • 2383 posts
  • LocationEngland, United Kingdom

Posted 29 May 2013 - 11:15 AM

You could also repair your installation, which will revert it to the same state it was in when you first installed the IRO client. However, if you installed the client before 2012, then I'd recommend that you instead reinstall the client using the latest version of the installer.

If you do choose to repair your installation, then ensure you first create a backup of all the personal files in your client folder, such as screen shots, chat logs, and AI system configurations.

Edited by Axylus, 29 May 2013 - 12:20 PM.

  • 0

#4 Berecus

Berecus

    I made it Off Topic

  • Members
  • 86 posts
  • LocationBehind you
  • Playing:Ragnarok Online
  • Server:Currently on Hiatus

Posted 29 May 2013 - 06:41 PM

So i just reinstalled it, should i just let it patch from 2012?






It was downloaded this year but the patch starts from 2012.
  • 0

#5 Berecus

Berecus

    I made it Off Topic

  • Members
  • 86 posts
  • LocationBehind you
  • Playing:Ragnarok Online
  • Server:Currently on Hiatus

Posted 30 May 2013 - 01:53 AM

it happened again wtf
it was fixed
then after i opened client
booom back to 2011>.>
wtf is wrong with this?
  • 0

#6 Berecus

Berecus

    I made it Off Topic

  • Members
  • 86 posts
  • LocationBehind you
  • Playing:Ragnarok Online
  • Server:Currently on Hiatus

Posted 30 May 2013 - 03:52 AM

Hmmm ok so i fixed it at first by reinstalling but it takes a GODLY amount of time...
Then it repeated,almost punched the pc at this point in time, so I waited and patched from 2011 then boom unable to write file...
It was stuck on repacking resource files for 20~30 mins
Hoping for PERMANENT solutions
  • 0

#7 DrAzzy

DrAzzy

    Really Azzy? Already?

  • VMod Retired
  • 15606 posts
  • LocationNew England
  • Playing:Ragnarok Online
  • Server:Chaos-Clandestine Society

Posted 30 May 2013 - 09:15 AM

Unable to write file generally means you forgot to run the patcher as admin. You need to run the patcher as admin.

Once you get it starting successfully and working, then - if you see it start to patch from 2011, immediately cancel it (don't let it get those patches applied), and replace patch.inf with a recent one (ie, what ren linked to in first thread, or from http://drazzy.com/patch ). What happened last time is that some of those patches got applied before you canceled it, and you got at least one that reverted a more recent patch.

We don't understand what causes the patcher to set patch.inf back to 0 (causing it to repatch from 2011) - so we don't have a permanent fix for it, just a workaround when it happens.
  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users