Difference between revisions of "OXPConfig"
m (no dependencies added) |
m (→Overview) |
||
| Line 10: | Line 10: | ||
For a user the only chance to avoid it is to remove oxps from the AddOns folder, but this is not a very elegant way to handle this. And with more than 200 oxps out there it is a timeintensive task, sorting them, moving them in and out - every day. Again and again. And before [[User:Eric_Walch|Eric Walchs]] [[OXP_mission_offering|solution for the missionscreen-handling]] the potential for clashes was immense, but there are still a few oxps that need some tweaks to avoid this problem. And there are more possible clashes. Music- and soundfiles can collide, even complete missions can get broken and the user will never be able to finish them. That's why I wrote OXPConfig. A small tool to help scripters and users, because it gives everybody the ability to enable/disable special features of oxps (like the enhanced logging) that are supporting this. | For a user the only chance to avoid it is to remove oxps from the AddOns folder, but this is not a very elegant way to handle this. And with more than 200 oxps out there it is a timeintensive task, sorting them, moving them in and out - every day. Again and again. And before [[User:Eric_Walch|Eric Walchs]] [[OXP_mission_offering|solution for the missionscreen-handling]] the potential for clashes was immense, but there are still a few oxps that need some tweaks to avoid this problem. And there are more possible clashes. Music- and soundfiles can collide, even complete missions can get broken and the user will never be able to finish them. That's why I wrote OXPConfig. A small tool to help scripters and users, because it gives everybody the ability to enable/disable special features of oxps (like the enhanced logging) that are supporting this. | ||
| − | And with a detailed logfile it will be a lot easier to see what happened... ...and to fix it. The BulletinBoard is always the best place to report problems with oxps and there are a lot of helpful and experienced oxp'er (not to mention the development team) ready to stick their nose into your problem. So every bit of information can help to recognize the weak points and before you'll post it there, collect all necessary data (OS, OS-version, Oolite version, Latest.log, stderr.txt). A few oxps are already supporting enhanced logging features [[BuoyRepair]], [[ | + | And with a detailed logfile it will be a lot easier to see what happened... ...and to fix it. The BulletinBoard is always the best place to report problems with oxps and there are a lot of helpful and experienced oxp'er (not to mention the development team) ready to stick their nose into your problem. So every bit of information can help to recognize the weak points and before you'll post it there, collect all necessary data (OS, OS-version, Oolite version, Latest.log, stderr.txt). A few oxps are already supporting enhanced logging features [[BuoyRepair]], [[Famous Planets 2.0.OXP]], [[Fuel_Station_OXP|Fuel_Station]], [[Hyperradio_js_OXP|Hyperradio]], [[Lave_Academy_OXP|Lave Academy]], [[Localhero_OXP|Localhero]], [[OXPConfig]], [[ScriptTimer]], [[Vector_OXP|Vector]] and [[Welcome_Mat_OXP|Welcome Mat]] and I hope that more oxps will use this way in future releases to be included into the database. |
===Features=== | ===Features=== | ||
Revision as of 17:58, 5 June 2010
Contents
Overview
Ouch, that is weird! Why doesn't it work? What the heck...!?!
Have you ever seen such comments about oxps? But not always it is an error in this particular oxp. Very often it happens that several oxps are trying to do their business at the same time (e.g. displaying a missionscreen or playing a music- or soundfile). Usually the last oxp overrides the other commands and everything is fine. But not always and then very strange things can happen.
For a user the only chance to avoid it is to remove oxps from the AddOns folder, but this is not a very elegant way to handle this. And with more than 200 oxps out there it is a timeintensive task, sorting them, moving them in and out - every day. Again and again. And before Eric Walchs solution for the missionscreen-handling the potential for clashes was immense, but there are still a few oxps that need some tweaks to avoid this problem. And there are more possible clashes. Music- and soundfiles can collide, even complete missions can get broken and the user will never be able to finish them. That's why I wrote OXPConfig. A small tool to help scripters and users, because it gives everybody the ability to enable/disable special features of oxps (like the enhanced logging) that are supporting this.
And with a detailed logfile it will be a lot easier to see what happened... ...and to fix it. The BulletinBoard is always the best place to report problems with oxps and there are a lot of helpful and experienced oxp'er (not to mention the development team) ready to stick their nose into your problem. So every bit of information can help to recognize the weak points and before you'll post it there, collect all necessary data (OS, OS-version, Oolite version, Latest.log, stderr.txt). A few oxps are already supporting enhanced logging features BuoyRepair, Famous Planets 2.0.OXP, Fuel_Station, Hyperradio, Lave Academy, Localhero, OXPConfig, ScriptTimer, Vector and Welcome Mat and I hope that more oxps will use this way in future releases to be included into the database.
Features
- Storing and loading of configurations
- Automatic loading when Oolite is started (configurable)
- Selective loading of changed oxps (configurable)
- Default configuration is stored and can be reloaded
- Internal logging (configurable)
Info
This tool gives you the ability to configure several oxps. It changes internal (local) settings of the oxps to enable (or disable) logging or audio functions and special settings to recognize errors or to avoid clashes, but it is for sure no cheat-tool. The oxps have to support these functions too - to be implemented in the database - so not every oxp can be included. This oxp runs without the debug-console and is primarily meant for non-scripters and lazy scripters, but if you really need debug-options it is highly recommended to install the Debug.oxp (written by Ahruman) and if necessary the console (written by Ahruman and ported to Windows by Kaks). Compatible oxps can use this sign to show that they can be configured by OXPConfig.
The handling is simple:
- Dock at a main station
- Open the Options-Menue (F2)
- Step to the Gameoptions (where Oolites options resides). Wait till activation message comes
- Step directly to the SYSTEM_DATA_SCREEN (F7)
- Do your settings and store them if you've changed something (in OXPConfig and save your game in the usual way)
- To deactivate it - step to any other screen (you'll get a message)
Requirements
- Oolite v1.73
- No dependencies
Download
OXPConfig1.08.zip - (11KB) Updated 04/09/2009.
