#SWIM & CUB
1 messages · Page 1 of 1 (latest)
I want to create these cub export files for settings (sprawln, pf, core) and add them to macros for swade with instructions and download links inside the journal.
Well, I already have that on SWIM. Sometimes I feel like we're working on similar things at the same time. That's not very efficient and if one of us runs out of time, the module becomes abandoned. Maybe it's too late now but I'd like to invite you over to SWIM anyway. If you're interested you could move over all your macros to there and we split them up into utility and immersion macros. I understand if you would prefer to do your thing but I think joining forces makes our modules more stable and resilient. Take your time to think about my offer if you need. =)
I wanted to help with SWIM, but you want things I don't.
Sound effects and animations are something that a macro module shouldn't handle.
I want simple and reliable over time macros.
This makes easier to fix.
Some macro I remove automation for edges.
I did that because you can't deal with it without become insane. lol
I'm trying to use swade core and br2 to deal with this things.
But, I'm interested in join forces.
I really don't want to try to do things with macros that a module or system can do better.
I just want to complete some stuff.
The fear macro: it open the swade card for a spirit roll. The user can add his egdes or whatever. Then, It tells him about the outcome.
I also don't like git docs. It's horrible to look out.
I prefer add journals with full inscruticons.
Tell me what you think. We can try to do some stuff.
I agree, that SFX and VFX is handled better by a full fledged module. But I am not skilled enough to do that. I was trying multiple times but just couldn't get it to work. But I was the first who tried to do this for SWADE and I believe there is nothing as powerful as the Ammo management macro. It's also the most annoying one to set up ever created. 🤣
I also agree that we clearly want different things but that might work in our favour. We can learn from each other and built on each others code more easily if working together I think. I liked your participation and by joining forces we could have automated and non-automated versions to coexist in the module.
Journal Entries are good to look up in foundry but I find them harder to navigate and markdown is just so much easier to write. But I don't mind instructions in journal entries.
I need to go now but I will get back to you if you're interested. I'm sure we can work something out. =)