while this arguably comes close to falling to a convert to thread and tell the author to file a bug report/use a normal thread, not going to. however in terms of this being a learning experience:
How can i see how it evolves over time
you can view the releases for the package bottom right corner (on desktop). this is also available via the api (iirc)
or report issues
use a normal thread (tbh, what this should have been), or message the user on [pick a platform there on]
Please add a link to version control for this mod
while i support this, i dont support what comes after..........
i will make it a thumbs up.
this is kinda not good/toxic(for lack of a better word coming to mind rn) tbh, aka do what i want, else i will just leave this review up (at least not hurting) and not make it positive (till you do what i want) isnt really the best......
as reported to you on discord over a week ago, this mod is breaking other mods (that load after it) by writing to the global namespace. context: (https://github.com/mt-mods/pipeworks/issues/97) please fix this and resubmit for review
please use the packages issue tracker or threads for bug reports
converted review into a thread
please use package issue tracker or threads for bug reports
converted review into a thread
github shows the author is still to a degree active, additionally looking at your issue, the error does not seem to match your claim
please use threads or the packages issue tracker for bug reports
converted review into a thread
please use packages issue trackers or threads on cdb when not available for bug reports
converted review into a thread
please use threads or a packages issue tracker to report bugs
converted review into a thread
please use threads or a packages issue tracker to report bugs
converted review into a thread
self reviews are not allowed
converted review into a thread
please use the packages issue tracker or a thread for reporting bugs
converted review into a thread
please use the issue tracker or a normal thread for bug reports
converted review into a thread
while this arguably comes close to falling to a convert to thread and tell the author to file a bug report/use a normal thread, not going to. however in terms of this being a learning experience:
you can view the releases for the package bottom right corner (on desktop). this is also available via the api (iirc)
use a normal thread (tbh, what this should have been), or message the user on [pick a platform there on]
while i support this, i dont support what comes after..........
this is kinda not good/toxic(for lack of a better word coming to mind rn) tbh, aka do what i want, else i will just leave this review up (at least not hurting) and not make it positive (till you do what i want) isnt really the best......
please use packages issue trackers or normal threads for bug
converted review into a thread
please use the issue tracker/normal threads for bug reports
converted review into a thread
please use issue trackers or normal threads for bug reports
converted review into a thread
please use issue trackers or normal threads for bug reports
converted review into a thread
see title ^^
see title ^^
no, cdb reviews are not for bug reports
also migrated this package to Dirkfried and there fork (cdb should make a new release tonight) as the existing one is abandoned
please use the issue tracker/a normal thread for reporting bugs
converted review into a thread
please use the issue tracker for reporting bugs
converted review into a thread
please use the issue tracker or a normal thread for bug reports
converted review into a thread
as reported to you on discord over a week ago, this mod is breaking other mods (that load after it) by writing to the global namespace. context: (https://github.com/mt-mods/pipeworks/issues/97) please fix this and resubmit for review
please use the issue tracker for bug reports