Dooge Posted August 22, 2016 Posted August 22, 2016 Sorry bout the title, the old title was not working too well compared to the neighbours title... So the real title is: Best practice for 'tag' / 'label' database. I am adding lot of idles to my Slut mod, and while doing it, I'm considering making that idle system into a separate mod, a modders resource/framework, sort of 'sexlab' but for idles. Modders could just call function from that mod with desired tags, and random idle(s) would play, suitable for the situation. Say, NPC refuses PC, then script would call PlayIdles('Standing', 'Authorative', 'Refusal') as part of the dialogue. Now... since there are people here who have done same already for sex animations, it's useful to know their experiences. What approach you would take to make a label system? And what not to do? I could make a small exe to keep database of all idles included, for easy tag/label assignment, and it would then output the required psc automatically to copypaste into the resource mod. Previously I have used jcontainers too, as well as storageutil. All have good and bad sides, but what I am interested is someone elses opinnion. Lot of tags and big lists would mean lot of looping. Not good. Bitmask would allows only one loopthrough of all animations. Is the Lua for jcontainers done, does it work well? Anything intensive would be great to take place outside papyrus, right? What else? Or while I'm at it, perhaps I just do dll throug SKSE Perhaps the Jcontainers/LUA is best approach, would allow testing functions outise Skyrim, meaning less time wasted loading and crashing Skyrim
Guest Posted August 22, 2016 Posted August 22, 2016 My advise for the implementation is to look how sslBaseobject does, and do the same. The external exe is probably useless. About names, here you have to decide. Don't use too much tags, never use two tags that are too close to each other, and give the ability to use multiple tags (just replicate what sslBaseObject does.)
Dooge Posted August 22, 2016 Author Posted August 22, 2016 My advise for the implementation is to look how sslBaseobject does, and do the same. The external exe is probably useless. About names, here you have to decide. Don't use too much tags, never use two tags that are too close to each other, and give the ability to use multiple tags (just replicate what sslBaseObject does.) I did have alook at it, but I now fancy making my own .dll instead of papyrus script For the tags, I agree, it should be strict and clear
Recommended Posts
Archived
This topic is now archived and is closed to further replies.