Feature Suggestion: please add an extension version field to the extensions. Currently it’s hard to know what versions are the latest or know if what we’ve downloaded is in fact the latest version.
Thanks!
Printable View
Feature Suggestion: please add an extension version field to the extensions. Currently it’s hard to know what versions are the latest or know if what we’ve downloaded is in fact the latest version.
Thanks!
Perhaps I've missed somewhere, what is the refund/return policy on Forge items?
Since 2500 seems to be becoming a major price point in the Forge, would it be possible to add 2500 as a gold buy?
I think it's been mentioned before, but can the FGUUpdater show the names of the extensions that are being updated, rather than the meaningless UUIDs, please?
We're not all developers and your Average Joe will never figure out that in order to understand what extension has received an update they need to go to the logs, grab the UUID and slap it in the URL of the Forge to see what extension it is. UUIDs are for devs, not for users.
Sometimes extensions break, so knowing which extension has just been updated would also speed up the process of reporting bugs and declutter the House of Healing - Unity forum.
I once again would like to request that the DEFAULT amount of line items be (much higher). Personally, I would prefer it to be ALL rather than 10. I'm just talking about "Manage Craft", not within the store. I understand why the storefront may want to have limitations, but I cannot figure out any good reason why CRAFTERS should want their list limited. It's a real pain to have to adjust that EVERY SINGLE TIME I go back to that list looking for a title beyond the initial 10.
I have a number of extensions and is a pain to identify which extension relates to which store item - or whats recently been updated.
I would like a log somewhere of what forge was downloaded/updated that can be reviewed after the update event (keep that last months worth if updates?) that can be looked at via a click on the FG loader screen. After all the information goes off the screen in a blink of the eye...
For a list to be maintained - when you perform an FGU update, all you need to do is to grab an index of the module name, the file/uuid name, as well as a URL to the store item. This can then be used to track what forge items referes to which..
How about a separate button to click to update Forge items just like the normal update button.
This would would in the same manner as the current "Check For Updates" which would give me the GM the option to download new extensions..etc before a game (or not) without having any nasty surpriuses in the game due to broken extensions. I believe the advice used to be "do not update extensions before a game" but this is no longer possible with a single button.
Also, can we have the option to retain previous versions og extensions so that we can revert if required. Yes I can hear you saying this will be a problem, but not really its very easy as you apply this simple process to retain 3 previous versions:
We can the see which extension was updated, when (file date) and have the ability to revert back to a previous version by manually:Code:if exist "extension.ext.003" delete "extension.ext.003"
if exist "extension.ext.002" rename "extension.ext.002" "extension.ext.003"
if exist "extension.ext.001" rename "extension.ext.001" "extension.ext.002"
if exist "extension.ext" rename "extension.ext" "extension.ext.001"
download "extension.ext"
I use a similar method often when I need to save a weeks worth of log files in a batch script.Code:if exist "extension.ext" rename "extension.ext" "extension.ext.new"
if exist "extension.001" rename "extension.ext.001" "extension.ext"
When updating files, there's no way to see what files exist on any one title. I've had to memorize (for lack of writing it down) all 30 (and growing) titles and is there just an extension or is it an extension and a module. So when I go to upload I have to upload ALL the files and am prone to missing one.
I can think of two solutions.
1) Have a list view available of files in the current build (and be able to see and verify after upload)
2) Be able to upload just the file in question being updated and have it replace that file only keeping the others intact (and have a way to delete files if necessary)