![]() ![]() ![]() So some mods will then use reflection and other techniques to try and work out what version of a mod is in that folder - is it a local build from source, or just copied over from workshop? Is it an old copy from workshop, or something else.? The problem then arises "which version of Traffic Manager" - you don't know the workshop ID so there is now way to know. In this situation the developers are usually not even attempting to make their mods compatible in offline mode, they are just doing it to make their development cycle a bit easier.Īs an example, mods that integrate with Traffic Manager (TM:PE) will expect it to be in a folder called "TrafficManager" because that's where it gets put when you build from source. To work around this, devs generally expect offline mods to be in specific folder names based on the folder that the mod xcopies to when compiled from source. However, in offline mode, everything is in the Addons/Mods folder, so the PluginInfo reports PublishedFileId as ulong.MaxValue for all of those mods = useless for determining which mod it is. That PluginInfo contains a PublishedFileId (id of the item in workshop), so it's easy _and accurate_ for mods to determine which other mods are subscribed. In online workshop mod, mods query the PluginManager to get the PluginInfo for each subscribed mod. You might still run in to compatibility issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |