• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Realm Works 1.0.11

L

liz

Ex-Staff
A new release is now available. This version requires a login to proceed after installation. This was done as some information used for the beta team (and eventually everyone else) needs to be brought down during login before certain functionality can be used and this can lead to a crash if the information is not present.

This update fixes issues that were discovered following Realm Works 1.0.9 and 1.0.10. You can find the full list of issues addressed and past release notes in the Release Notes within Realm Works.
 
I cannot seem to download 1.0.11. The last version I can seem to download is 1.0.1011.168. And I keep getting an error (sent in twice) about something like "an entry already exists" for an event that I've had for some time.
 
You have 1.0.11. (When the RW people give version numbers they drop the 1000 in the third part.)

Can't help you with the error, though. :(
 
ryntak4536 said:
I cannot seem to download 1.0.11. The last version I can seem to download is 1.0.1011.168. And I keep getting an error (sent in twice) about something like "an entry already exists" for an event that I've had for some time.
Click to expand...

Please submit a bug report if you haven't already.
 
I'm now encountering the "an entry with the same key already exists" error. Bug report submitted. Crashing immediately after loading the realm every time.

This is RW's way of telling me to relax and read for a while. :)
 
Mine were reported. However, I found it was specific to one event entry. Instead of letting RW close, I kept it opened, then renamed the entry. It no longer does it.
 
The bug causing my errors has been found and I should be back up and running after the next patch. Just posting back here so folks know that these things are resolved quickly.

Thank you to the entire RW team!
 
You must log in or register to reply here.
Back
Top