In order to ensure that committed files don't break content, certain checks are performed on import. Any files not passing those checks will be rejected and not committable. FWN will show you error messages that describe exactly what went wrong. You can just fix it in the toolset and drag & drop the file in again.
|Impl. Status||Type||Check||Error given by FWN / description|
This means you are not in the permit-list for uploading non-area templates - meaning anything other than .are and .git. Other files than those two are not required to make new areas, and as such the initial permission set given to users is limited to that.
All files downloaded from FWN are tagged with the last-commit ID.
This is to ensure that no data is lost by overwriting commits of other users. For most resrefs, the commit oid is stored in the Comment field (for .git files, it's a variable in VarTable).
Any commits you make that would overwrite data by other users or newer commits are rejected outright. You can overwrite files without a propery commit tag if you were the last one to commit data, on the assumption that you are uploading a new version of a work-in-progress resref.
Areas are checked to always have the proper area prefixes. See Ref conventions.
Area has a invalid tileset. This means we can't display the map you built, because you didn't use the correct module.
Area size needs to be divisible by 10 to fit the global area grid. See Ref conventions for details.
All objects placed in areas are checked to not have improper scripts set.
All uploaded templates that have script hooks are checked for invalid scripts.
A localised string has too many values on a given struct/label. This usually means there's a english value set and one in another language. To fix this, edit the object at the described path and only put a value into english. Set your toolset to english (Options -> Language) to prevent this from happening in the future.
|PLANNED||ATs||Area Transitions are verified to be link-complete - no dangling ATs are allowed. This works by parsing all Waypoint and Door tags.|
|PLANNED||AT-Tags||All tags involved in Area Transitions are verified to be unique module-wide.|
|PLANNED||Route Waypoints||Route waypoints and NPC tags are verified to be unique module-wide.|
Added data to resrefs
Resrefs added to FWN will receive some local variables describing where the resref came from, who added it, and so on.
|OK||string||The sha1/commit ID that sourced this resref.|
|OK||string||A human-readable string describing where the object was spawned (or "" if not applicable).|
|OK||string||The email that committed this specific version of that resref.|
|OK||string||A UTC-formatted timestamp. May change in the future.|
This table lists all modifications your resrefs will receive when they are being deployed to the server. These are completely transparent to you - you are not expected to take care of them.
|Impl. Status||Refs||What is being done?|
|OK||Mod_Area_List is always cleared. Mod_CacheNSSList is always cleared. These fields are being managed by FWN.|
|OK||area tags are always set to their resref|
|OK||areas receive the default area-enter scripts|
|OK||Doors (/Door List) receive the default door scripts|