DOE: REMU (Ruleset, Extension & Module Updater) Extension

Printable View

Show 40 post(s) from this thread on one page

May 26th, 2018, 08:29
dulux-oz

1 Attachment(s)

DOE: REMU (Ruleset, Extension & Module Updater) Extension
Overview
This Extension is a supplementary tool designed to work in compliment to the FG-Updater - not to replace it. The DOE: REMU allows Fantasy Grounds to automatically check to see if various Community Developed Rulesets, Extensions and/or Modules (REMs) are available for update. If an update is found the DOE: REMU can download the REM and place it in the correct directory within the User's copy of Fantasy Grounds.

A screenshot is provided.
Attachment 23582

Full details are provided in the accompanying Manual (a Module). The Manual can be opened by Fantasy Ground v3+ using any Ruleset, with or without the Extension being loaded.

Special Setup
Because this Extension does things that Fantasy Grounds was never designed to do, it requires some special care and attention when first setting up. It also requires some "helper" programs which MUST be located in a very specific folder on the computer's hard drive. This information and the Helper programs are provided in a separate pdf Document (DOEREMU_Setup_Guide_Windows.pdf) and an Installation program (DOEREMUHelpers.exe) available below.

Please Please Please Please read the Extension's accompanying Documentation BEFORE installing the DOE:REMU

Version
- 1.0.0 - Initial Creation
Manual Version
- 1.0.0 - Initial Creation
Rulesets
This Extension works with:
- CoreRPG Rulset v3.3.5+.
Dependencies
This Extension is dependent on:
- DOE Base Extension v3.2.1
Rulesets By Dulux-Oz
- DORCore
Other Extensions By Dulux-Oz
Downloading The Extension
This Extension is no longer avaliable for download.

Loading The Extension
This Extension is loaded exactly like all other Fantasy Grounds Extensions - by first copying the .ext file to the Extensions Folder under the Fantasy Grounds Folder and then re-starting Fantasy Grounds. If the Extension is compatible with the currently installed version of a given Ruleset it will be displayed in the Extensions List for that Ruleset and can be loaded by clicking on the Checkbox next to the Extensions name.

If the Extension has large red 'X' next to its name in the Extension List then the Extension or an Extension that this one is dependent upon is not compatible with the chosen Ruleset. Make sure that you have downloaded and installed the latest copy of this Extension and any Extensions this one is dependent upon.

When Fantasy Grounds Updates
After a Fantasy Grounds version update you should verify that all Extensions (not just this one) have been either updated themselves or verified by the Extension author that they work with the new version of Fantasy Grounds. If you have any issues with Fantasy Grounds after an update then it is best to disable all Extensions and then re-enable them one by one until the issue re-appears.

Helping Out
If you like this Extension and find it useful, you may like to consider showing your support by making a Donation so that this Software and similar Software can continue to be maintained and developed.

Donations can be made via PayPal to:
- [email protected]
Thank you
May 27th, 2018, 00:30
LordEntrails

1 Attachment(s)
Dulux, I'm not getting this to work. I don't get a the Warning or Setu window when I start the maintenance campaign. Here are the stesp I did;
1. Read the Setup Guide.
2. Install the Helpers per the guide above.
3. Download the DOE:REMU Manual and install it in FG.
4. Download the DOE:REMU Extension and install it in FG.
5. Download and install the DOE: Base (latest!) and install it in FG.
6. Create a new CoreRPG campaign titled something like "DOE:REMU Maintenance"
7. Load the DOE Base and DOE REMU extensions.
8. Open the campaign, load the DOE REMU Module, read it.
Attachment 23590
May 27th, 2018, 01:33
Andraax

Did you click the REMU button in the upper right?
May 27th, 2018, 01:58
LordEntrails

Quote:

Originally Posted by Andraax

Did you click the REMU button in the upper right?

Nope! Missed that in the instructions.
May 27th, 2018, 02:12
LordEntrails

Very nice Dulux. I'll be looking to add my modules to this after I read more.

Two things to take notice of;
1) the quick start instructions seems to imply that the update window opens automatically.
2) the manifest file was not able to be downloaded like the other files in the repository were. I assume this is since I was not using a git client and just a browser, but I suspect other might find similar challenges. Doing a right mouse, save file as saved an html file that was useless, I ended up cutting and pasting the text as displayed into notepad++ and saving the file that way.
May 27th, 2018, 03:49
dulux-oz

Notes noted - I'll see how to fix things.
And, fot the record, I wasn't using a git-cliet to download the Manifest file (when I tested things) :)
May 27th, 2018, 04:46
dulux-oz

Quote:

Originally Posted by LordEntrails

Very nice Dulux. I'll be looking to add my modules to this after I read more.

Two things to take notice of;
1) the quick start instructions seems to imply that the update window opens automatically.
2) the manifest file was not able to be downloaded like the other files in the repository were. I assume this is since I was not using a git client and just a browser, but I suspect other might find similar challenges. Doing a right mouse, save file as saved an html file that was useless, I ended up cutting and pasting the text as displayed into notepad++ and saving the file that way.

Just to clarify:
1) You mean in the Manual (the mod file)?
2) Right-click and choose "Save Link As" - I'll put that in the doco as well.

Cheers
May 27th, 2018, 06:07
LordEntrails

Quote:

Originally Posted by dulux-oz

Just to clarify:
1) You mean in the Manual (the mod file)?
2) Right-click and choose "Save Link As" - I'll put that in the doco as well.

Cheers

Correct, the quick start entry in the mod file is where I went astray. reading the full details it was clear,just not in the QS entry.

I'm using Chrome, and with the other git entries (like the extensions and mods, there is a download link. On the git page for the .rem file their is not, it displays the text. When I right clicked on the save as from the directory listing, it saved the file as an html, not xml file. I can get you screen shots and more details as needed.
May 29th, 2018, 00:08
dberkompas

No idea what I've done. I blew away my campaign based on CoreRPG, blew away the directory that is created with the DOEREMUHelpers.exe

I downloaded the DOEREMU.ext and DOEBase.ext and put them in the extensions directory, and deleted the manifests directory.

I then run the .exe, and it put in C:\ so it creates the appropriate directory.

When I create a new campaign (LIVE, not test or dev), and load the modules, I get the following error.
[28.05.2018 18:46:13] Script Error: [string "DOEREMU/Scripts/lsREMUManager.lua"]:239: import: Unable to open file

I looked at the code, and it looks like it has something to do with manifests, which I haven't even loaded.

Dave
May 29th, 2018, 04:28
dulux-oz

Quote:

Originally Posted by dberkompas

No idea what I've done. I blew away my campaign based on CoreRPG, blew away the directory that is created with the DOEREMUHelpers.exe

I downloaded the DOEREMU.ext and DOEBase.ext and put them in the extensions directory, and deleted the manifests directory.

I then run the .exe, and it put in C:\ so it creates the appropriate directory.

When I create a new campaign (LIVE, not test or dev), and load the modules, I get the following error.
[28.05.2018 18:46:13] Script Error: [string "DOEREMU/Scripts/lsREMUManager.lua"]:239: import: Unable to open file

I looked at the code, and it looks like it has something to do with manifests, which I haven't even loaded.

Dave

Hi Dave,

I think what you're saying is that this is a new "Maintenance" campaign but that you previously had an old "Maintenance" campaign (I call them MCs from now on) ie that you're starting over, yes?

If this is so, then the persistent Manifest Registration from the old MC is being picked up by the new MC and so it is trying to load the registered manifest, and because the Manifest file isn't there its complaining. So, its sort of a bug (which I'll code a fix for) but if you place the actual manifest file in the /manifests/ folder under the FG Data Folder (you may have to manually create the manifests folder) and then restart your new MC you should be good to go. Alternatively, you could manually edit the GlobalRegistry.lua file and take out all the relevant infor qand data structure contained within. Alternatively, you can ignore the error, go i and deregister the old Manifest and then register a new one (on the same one - same difference).

BUT, if I've mis-read what you've been doing and trying to do then you'll need to tell me because I'll need to come up with a different solution.

Show 40 post(s) from this thread on one page