Jump to content

Ai4rei

Members
  • Posts

    425
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by Ai4rei

  1. Thank you. Updated to 2.8.3, fixes and updates translations, no functional changes.
  2. Have you diffed 'restore login window' by any chance? If so, the auto-login won't work. The setup looks fine to me. Version 1.3.0 Added settings to lock down some features, intended for paranoia defaults in embedded INI (see the included INI for details). Fixed the client could fail with error "Requires elevation to execute" when using Start or Replay buttons. Anyone interested in some basic skinning (background), something to the effect of RO Patcher Lite skinning (put a bgskin.bmp file next to the .exe to try) ? Version 1.3.1 Fixed missing button labels, when user name was saved.
  3. RO Credentials About Simple and tiny client launcher+login. Has no prerequisites and runs on all Windows versions. Known Issues [aavc] This tool is not safe for computers running Avast Anti-Virus. Download binary, reference source Q & A Is it customizable? Yes. How? With resource editing tools, such as ResourceHacker. All text and icons can be customized. Settings can be edited in an INI file (included). What is "reference source"? You cannot compile it (unless you provide the missing components), but see what functionality the latest binary contains. I want it to be xyz.exe, but it does not read the INI file. Why? You have to match the INI name to the EXE name. rocred.exe -> rocred.ini mytest.exe -> mytest.ini How can I embed an INI file into the EXE? Add the INI file as RCDATA resource named CONFIG with ResourceHacker. How do I use background skinning? Create a file named bgskin.bmp (magenta #ff00ff is considered transparent). You can also embed the file as BITMAP resource with the name BGSKIN. Window size is adjusted to the bitmap size, position of controls must be set in the INI. Buttons can be skinned as well, see the INI for names. Can I add custom buttons, if so, how many? Yes, see the INI template for details. There is no defined limit on how many, the only constraints are available memory, GDI resources and INI size limit on some platforms. By the way, custom buttons can be skinned as well. Why does the client not auto-login when I press "Start"? The client must be 2010-08-04aRagexeRE or newer and must not have the "Restore Login Window" patch. This work is licensed under a Creative Commons Attribution-Noncommercial 3.0 Unported License.
  4. Administrator and compatibility mode have no effect on OpenSetup. Try the lastest version. If it still cannot detect your video modes, please post a screenshot of the display tab in "dxdiag" (start via Win+R).
  5. Thank you both very much!Updated to 2.8.2, fixes a Lua loading bug and adds sanity checks for Lua for people with Lua errors in client (and messed up installs). Also updates above translations. There is no public 2.8.1, because it was not stable. New bits: TEXT_ERROR_INSANE_ENGINE, "Selected settings engine has determined, that your installation state will interfere with the correct loading and saving of settings.\r\n\r\nSee opensetup.log for details."
  6. Click the [?] in the upper right, then click on the option you want to know about.
  7. Updated to 2.8.0, adds configurable "HKLM to HKCU", visual resolution input and a batch of bug-fixes. For details see website.
  8. The patcher has timed out while downloading said patch, your connection might not be stable enough to transfer a 25 MB file from Korea in one piece. Try to get the file from elsewhere and do a manual update.
  9. Both formats do the same, declare and assign Lua tables. Basically:TableName = { FieldName = 123 }is the same as:TableName = {} TableName["FieldName"] = 123System folder contains the default files for the settings and also the table declarations. So deleting it makes things only worse.
  10. The first post contains a link to the translation template on pastebin. The template itself should be obvious to translate, if not feel free to ask. When translated, post it on pastebin or somewhere; it will be included in the next release then with attribution. There is no translation team, there's a bunch of people contributing their translations. So you are free to translate whenever you want.
  11. The latest version supports Windows 8. It will ask for administrator upon saving regardless, because settings are written into an area of the registry that can be written by admins only (unless you use a custom build with saving to HKCU, which needs a modified client as well).
  12. Updated to 2.7.0, adds Spanish translation, settings reset and configurable engine on startup. For details see website.
  13. Always specify your client version or provide the WDG error log.
  14. There's a bug in the error message itself, but another thing bugs me. Have you started OpenSetup "as Administrator" or do you have UAC off (since I do not see the UAC shield on the buttons)?
  15. Great. Here we go: Updated to 2.6.6.210, updates to Russian localization (new bits and fixes) by Jarek.
  16. Thanks! Mind reviewing the current localization template?
  17. Only a small range of clients reads from data. By the time OpenSetup Lua support was implemented, clients already read from savedata.
  18. The switch affects only where OpenSetup saves the settings, it has no direct effect on the ragexe. You have to set the switch depending on which client you use. Also every time you switch between LUA/REG modes, all settings are reloaded from respective storage. Yes, some settings are saved to registry, even in LUA mode.
  19. Updated to 2.6.4.204, fixes graphics card resolution list issue on Windows 8. If you use Windows 7 or 8, you are encouraged to update. Source has also been updated to reflect relevant changes. Edit: Since today's release was such a fail, let's do this again and better (2.6.5.207).
  20. Current unpacked themida clients are not considered compatible. The diff also is not fixed to any ID, so you should be able to use new hair styles with old clients.
  21. Updated: WDGSkipPacketHeaderObfuscation Updated for use with non-sakray clients. WDGSkipLicenseScreen Updated for use with non-sakray clients, care of . binary builds, sources
  22. Code changed in that spot, so the diff broke.
  23. Updated: WDGDisableHShield Rewritten, untested. binary builds, sources For translations use WDGTranslateClient, which was made for the translation project you linked to. Maybe someone even maintains the translation file for it.
  24. What is it supposed to do? In progress.
  25. I see, Gravity added an another Hackshield related function in the initialization path. Even for the clients I stated.
×
×
  • Create New...