[Edit 2019-03-10 - Fixed a couple of things that would kick an exception on the Log-in Settings page. Specifically, these dealt with the log-in servers and listeners settings. Version 126.96.36.199]
[Edit 2019-03-10 - Changed the two settings, HideWarningGump and HideWarningItem, to ShowWarningGump and ShowWarningItem.]
[Edit 2019-03-04 - Removed two (2) deprecated settings from the defaultpol.cfg file that ships with the Configurator. Those settings are: Keyfile and Multithread. No version change to the POL Configurator as the program was not affected.]
[Edit 2019-02-24 - Added the two new settings, HideWarningGump and HideWarningItem, to the Logging and Reporting page. Version 188.8.131.52]
[Edit 2018-12-28 - Fixed an issue with the way a missing uoclient.cfg file was handled. Version 184.108.40.206]
[Edit: 2018-12-27 - Removed a debug message that appears when selecting a server on the Log-in Settings page. Fixed an issue with the UO Expansion selection that was not adjusting the Max Art tile ID and the UOFeatureEnable byte value properly. This is version 220.127.116.11]
[Edit: 2018-12-26 - There was an issue that only occurred if you were missing or needed to replace your watch.cfg file with the default watch.cfg file. This has been fixed and the hosted files, installer and ZIP, have been updated. Please note that the version number is the same for this update. This is an issue with the Lazarus compiler. It is supposed to automatically increment the version build number but it does not do it and I forgot to manually increment it ]
[Edit: 2018-12-16 - The ZIP and installer files in this post has been updated to version 18.104.22.168. The screenshots in this post are now obsolete. See the documentation in the Documentation folder inside the Configurator installation directory for new pictures. This revision fixes a couple of issues with version 22.214.171.124. Previously if you clicked on the Load Profile button prior to saving any profiles the Configurator would throw an exception error. The other issue fixed has to do with editing an external program button. Sometimes erroneous information was placed in the edit window's text fields. It is supposed to put the name you gave to the program in the name text box and the location of the program in the location text box. Which it does now.]
[Edit: This is a bug fix release. The POL Configurator was writing an incorrect setting to watch.cfg. This release on 2018-09-22 fixes this bug. The link further down is updated. Fortunately, watch.cfg is not a critical file but it needs to be written correctly. Your watch.cfg file will have erroneous settings if you used a version of the Configurator prior to this release. To fix your watch.cfg file, open /pol/config/watch.cfg in an editor. Delete the current contents of the file. Paste the following into the file and save it. That's it.
Code: Select all
# # If Combat is set to 1, information regarding combat damage, hits, and misses, etc will be printed. # Default is 0 # Combat=0 # # If ProfileScripts is set to 1, profiling information will be printed when any script exits. # Default is 0 # ProfileScripts=0
[Edit: New version 126.96.36.199 Released 2018-08-14 - Added the new setting in ecompile.cfg, NumberOfThreads. Also fixed an error in one of the tooltips.]
[Edit: New version 188.8.131.52 Released 2018 -05-06 - Fixed the "Run POL" button on the eCompile page. Originally the two buttons to launch POL were to operate differently. The "Test Launch POL" button launched POL from a batch file. This was to keep the command line window open so you could see any errors if POL stopped running prematurely. You would need to press the 'Y' key and <enter> to exit and close the command window. The other button was supposed to run POL without a batch file, closing the command line window when POL stopped running. For some reason I made that button behave just like the "Test Launch POL" button. I finally got around to fixing that for this release.]
You'll forgive a little of self-indulgent pride here. Well, even if you don't forgive it I'm going to have it anyway.
This is a project I started 9 years ago. For some reason that I cannot remember I abandoned it and had totally forgotten about it. While I was going down the rabbit hole of deleting old stuff I rediscovered it and decided to resurrect what was then called POL CFG edit. I look at the code and I am amazed that I actually wrote the original program and, all but for a few bugs, it did what it was supposed to do.
It originally was just a graphical user interface (GUI) to configure pol.cfg. When I brought it back into development I decided to give it the ability to load and edit more than just pol.cfg. So I added servspecopt.cfg and combat.cfg to its repertoire along with a tiny file named watch.cfg. I was going to have tabs for each file but then I had an idea. I would split the settings up based on their function rather than the files they reside in. I came up with three basic functions, server settings which mostly are hidden from the player, gameplay settings which in some way are most visible to the player, and logging and error reporting.
[EDIT] Now it also handles *.mul file extraction from *.uop files thanks to Eos' fine little utility, generation of tile, landtiles, and multi cfg files, facet (realm) generation, ecompile.cfg settings, and eCompiling scripts. There is also a "POL clean-up" feature that you can use to delete unnecessary files. You'll find that on the eCompile page.
Here are screenshots of the six pages in the Configurator. I just recently added the instructions tab so you don't have to go dig up the text file. Using it is fairly straightforward though.
A note about the bug that was fixed in a previous release: It was a parsing error essentially. I read each line of the cfg files and look for a delimiter (separating character) between the setting name and the value. In all of the files, I read into the Configurator, except ecompile.cfg, those values are delimited by the equals symbol, '='. In ecompile.cfg the delimiter has always been at least one space character. This was an oversight on my part and was fixed prior to the public release of the second version of the Configurator. After its second release, a new parsing issue arose. Some people understandably use one or more <tab> characters rather than spaces and I had not considered that. So my parsing routine had to be updated. It is now, and everything should be fine. Please report any issues, preferably in a PM, so I can look into them. I find PMs easier to manage when getting bug reports.
Please note that the default settings for the POL Configurator are set to work with POL Core 099 and up and client version 184.108.40.206 and later versions, until the UO creators change the Art tile maximum. If you are using an older client you may want to set the Max Art Tile ID on the server settings page to the maximum art tiles of your client. Either 0x3FFF or 0x7FFF.
This is the current version.
Download the POL Configurator installer and give it a try.
I have had reports that the install creator I use to make the POL Configurator Installer being blocked by antivirus and anti-malware software with some antivirus programs. I am reasonably certain that my install creator is clean as not every antivirus program blocks it but because it does get blocked by some antivirus software I am providing a ZIP file of the program and supporting files. When unzipping this to an existing installation of the Configurator make sure that you tell your OS or ZIP file manager to overwrite all files.
When you first launch it you will get a pop-up box that warns you about a caveat you need to be aware of. The warning is repeated at least twice in the instructions and I will repeat it again below.
Note: Upon launching the Configurator it loads the default settings. If you have settings already configured for your server and you want to keep them, first make sure that the Configurator is showing your POL location in the box at the bottom of the form labeled "Location of your POL directory". Then click the "Load My Config Files" button. If you fail to do this, upon saving your settings you will change your previous configuration to whatever settings are showing in the Configurator and you will lose the settings that you had prior to using the Configurator.
See how you like it.