Dalton Posted September 2, 2022 Share Posted September 2, 2022 (edited) I can't express how much time this function would save. Being able to import attributes from another TEW2020 mod for a worker with the same name would cut down modding/converting by dozens of hours. Edited September 2, 2022 by Dalton 6 Quote Link to comment Share on other sites More sharing options...
CGN91 Posted September 4, 2022 Share Posted September 4, 2022 That would be neat Quote Link to comment Share on other sites More sharing options...
St. Templar Posted September 5, 2022 Share Posted September 5, 2022 Clarify this for me, just because I want to be sure I'm recognizing what you're suggesting. -- Currently, if I want to pull a worker from one database into another one, that worker comes with the attributes they are assigned in the second database. For example, if I want to import Kevin Von Erich from the database The Big Bang into the database WCW Lives, it will import Von Erich, his work history, his attributes, skills, etc. -- You're suggesting that if I build Kevin Von Erich in my WCW Lives database, I could just import his attributes from The Big Bang database. Is this right? St.T Quote Link to comment Share on other sites More sharing options...
BrokenCycle Posted September 6, 2022 Share Posted September 6, 2022 (edited) 21 hours ago, St. Templar said: Clarify this for me, just because I want to be sure I'm recognizing what you're suggesting. The way the game currently works means that all Attributes are tied to the worker. And, converting a 2016 mod doesn't quite work that well. So if you were to make a database from scratch, or convert a 2016 mod, you would need to go through the (painful) process of setting all the Attributes. If Attributes were separate from the worker, and worked like an importable asset, any mod maker could essentially make a huge database that could be used for other mods as freeware. Edit: I do consider this kind of a misstep in making the game. I'm assuming that by tying it to the worker Adam wasn't aware of what that would do to the game until it was too late to be changed? I don't know. But I do think that this is such an annoyance that it deters people from modding, unfortunately. Edited September 6, 2022 by BrokenCycle 1 Quote Link to comment Share on other sites More sharing options...
St. Templar Posted September 6, 2022 Share Posted September 6, 2022 3 hours ago, BrokenCycle said: The way the game currently works means that all Attributes are tied to the worker. And, converting a 2016 mod doesn't quite work that well. So if you were to make a database from scratch, or convert a 2016 mod, you would need to go through the (painful) process of setting all the Attributes. If Attributes were separate from the worker, and worked like an importable asset, any mod maker could essentially make a huge database that could be used for other mods as freeware. Edit: I do consider this kind of a misstep in making the game. I'm assuming that by tying it to the worker Adam wasn't aware of what that would do to the game until it was too late to be changed? I don't know. But I do think that this is such an annoyance that it deters people from modding, unfortunately. Okay. That all makes sense. Good idea, then. Thanks for explaining. St.T 1 Quote Link to comment Share on other sites More sharing options...
Dalton Posted October 29, 2022 Author Share Posted October 29, 2022 On 9/5/2022 at 8:35 PM, BrokenCycle said: The way the game currently works means that all Attributes are tied to the worker. And, converting a 2016 mod doesn't quite work that well. So if you were to make a database from scratch, or convert a 2016 mod, you would need to go through the (painful) process of setting all the Attributes. If Attributes were separate from the worker, and worked like an importable asset, any mod maker could essentially make a huge database that could be used for other mods as freeware. Edit: I do consider this kind of a misstep in making the game. I'm assuming that by tying it to the worker Adam wasn't aware of what that would do to the game until it was too late to be changed? I don't know. But I do think that this is such an annoyance that it deters people from modding, unfortunately. On 9/5/2022 at 11:40 PM, St. Templar said: Okay. That all makes sense. Good idea, then. Thanks for explaining. St.T BrokenCycle has the crux of it, yes. Basically, if attributes for a worker were treated as a "set" rather than individually added to workers, it would drastically cut down modding time. Basically, attributes should be treated like moves. Each move set has moves, and the move set can be imported to be tied to a worker. Replace "move set" with "attribute set" and "moves" with "attributes" and that's what I am suggesting. It would save HOURS of modding time. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.