Auto-Updater and Bugfixes
First of all, I want to say thank you to everyone who tried out the client, reported bugs and gave feedback. I hope you enjoyed fluorescence, even if some of you had a rather rocky start :)
One of the things I noticed pretty soon after the release was that a lot of bugs required only very small and easy patches; but distributing the patched file again would take quite some effort. Thus, I created a small svn-based auto updater for fluorescence. You can download it at http://code.google.com/p/fluorescence/downloads/. Just extract to an empty directory and run the updater executable. This will keep your local copy up to date with the latest release.
Please report any problems with the updater to the bugtracker, as well as any bugs you encounter with fluorescence.
The latest version of fluorescence does not require the RunUO patch to run correctly, as the packet code has been updated to conform to the latest SA version. In addition, creating a shard now allows you to set an “High Seas” option to handle the slightly different mul format. uop files are not supported (yet). Furthermore, using skills is now possible (skill gump).
11 Responses to “Auto-Updater and Bugfixes”
Drk84 - July 23, 2012
Great job:D
Suwing - August 9, 2012
Nice !
Any tutorial to how to test it ? (how to set files, add shard, etc.)
Good luck!
spin - August 9, 2012
Just start fluorescence and click “Create shard”. If you have a somewhat recent UO version without UOP files (HS, SA, ML) it should work out of the box.
Unfortunately, there are no tutorials yet, but if you run into problems you can just post here, use the mailing list at http://groups.google.com/group/fluorescence-client or the OrBSydia forum at http://orbsydia.com/forum/forumdisplay.php/187-fluorescence
Suwing - August 11, 2012
OrBSydia look like in maintenance.
Could you give an exemple of config.xml folder shard please ?
I add one but when I clic on in the game nothing happen. The game close.
my config.xml file :
I don’t know what is wrong.
spin - August 11, 2012
Whenever the client does something unexpected, check the fluorescence.log file first. I tried to print meaningful error messages there.
Check out http://code.google.com/p/fluorescence/source/browse/defaultConfig.xml to see all available config options. Depending on your UO version, it could be that the client detects a missing file (e.g. map1.mul). Handling these errors is not really implemented yet, and only leads to the client shutting down. If that is the case, just add a tag like
<map1 enabled="false" />to the files section of your config file.Suwing - August 12, 2012
Ok working !
New classic client => too new
Old Samurai Empire client => too old
Add both in same solder => ok!
Any ip server to test or need to run home server ?
Thanks :)
spin - August 12, 2012
Smoothening the startup process is the next thing on my todo list. Looks like a lot of people having trouble with that.
There is no public server to test fluorescence. I recommend running a RunUO 2.2 home server.
Suwing - August 12, 2012
There is a tutorial here : http://www.ultima-x.com/play-ultima-x-uo-private-server/
They say to stop update of the new classic client at 7-0-7-1. I’ll try it soon. I think is more good than my custom funky install ;)
spin - August 12, 2012
I also mostly use a client that is patched to one of the last SA versions. But I already started working on making the loading process more tolerant, and got even the 4.0.0 up and running.
The new version will go online next week.
Suwing - August 15, 2012
Well I don’t know why but I can’t update my client. So using 9anniversary install. Client is 6.0.1.10
Hope I’ll find solution to get more recent stuff =)
spin - August 15, 2012
Check the “patchlog” file in your Ultima Online directory. It usually tells why the patcher fails.
Leave a Reply