Replies: 1 comment 1 reply
-
|
after investigating this a bit more it seems that some addons are being favored over others for SetSaveData initially i thought its just taking the bigger file size as the preferred one because it appeared to be the case with 5 addons i mounted.. until i mounted a 6th one which was smaller than the other 5 and suddenly cs_script started to favour it (also the order in which we mount the addons seems to not play any role at all, cs_script will still pick favorites) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Im not sure if this is the intended behavior but when mounting an addon like ie
map_workshop id1 de_nukein order to load onto de_nuke with additional assets (like a prefab with the script etc) SetSaveData will save into thesave_id1.txtfilehowever if we were to mount two addons like ie
map_workshop id1,id2 some_cool_other_mapwhere id1 is again our prefab with the script and id2 is some other workshop map, SetSaveData will save into thesave_id2.txtfile. (also the order in which we mount the addons does not matter for saving data it seemsid1,id2orid2,id1will both use the id of thesome_cool_other_mapmap)this will potentially override the id2's own save file if it had any and make it impossible to store stuff synced between maps
my suggestion is to somehow make the script aware of what addonid its running from and always use that id for SetSaveData and GetSaveData
alternatively use the last mounted id, which in the case of
map_workshop id1,id2 some_cool_other_mapwould be id2 for the saveBeta Was this translation helpful? Give feedback.
All reactions