You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the past when i attempted to import an ItemLotParam_enemy csv, the values associated with the fields lotItemBasePoint0x would be clamped down to 34463 if the number in the csv was higher, this was very useful for my workflow, but in the new update this doesnt seem to happen. I hope this is not an intentional change.
Ive recently updated to the new version (1.8.1 - 1.9.1)and realised i couldnt import a CSV file that had worked just fine in my previous version, after some investigating i figured out the issue was fairly benign, so i hope it gets fixed.
The text was updated successfully, but these errors were encountered:
I'm personally a little conflicted, since on one hand it's obviously more convenient. But on the other, if you don't know what you're doing (or what value types are) this behavior would cause confusion.
Maybe adding a prompt to clamp going forward and it explains what's happening if you do.
In the past when i attempted to import an ItemLotParam_enemy csv, the values associated with the fields lotItemBasePoint0x would be clamped down to 34463 if the number in the csv was higher, this was very useful for my workflow, but in the new update this doesnt seem to happen. I hope this is not an intentional change.
Ive recently updated to the new version (1.8.1 - 1.9.1)and realised i couldnt import a CSV file that had worked just fine in my previous version, after some investigating i figured out the issue was fairly benign, so i hope it gets fixed.
The text was updated successfully, but these errors were encountered: