Open vico93 opened 7 years ago
First, we'd need to have releases for 1.10-1.12. We don't even have a release for those, and you want to implement 1.13 functionality? I mean, when it comes out, @SquidDev could probably add that stuff in, but we should focus on getting some backlogged releases out the door.
First: for releases, we have https://cc.crzd.me/ by @SquidDev Second: again, this would be a good addition for organization server-side.
@vpontin I wouldn't call the .jars available on http://cc.crzd.me releases, they are more like in dev builds. Releases need to be tagged as such on github and/or uploaded to curseforge.
On 1.13: I don't think there's much point discussing it until it's much closer to release - we haven't even had a snapshot. There's going to be a lot of internal changes, so the resource pack/data pack distinction is the least of our worries :).
On releases: cc.crzd.me is great, but it doesn't come close to something on CurseForge. People aren't going to find it unless they are tuned into the CC community, and the dev builds are definitely not going to make it into any major mod packs. Sadly there is naught we can do, as releases are entirely up to Dan.
Also, @MineRobber9000 there's no guarantee I'll be the one to port it to 1.13. I'm more than happy for someone else to give it a go :p.
Well, seems like in 1.13 Data Packs will be a thing.
What about add support for load the files currently supported in resource packs from datapacks? For example, bios, custom programs etc (i still dont use this feature, but i know this currently exist), everything under computercraft's namespace folder would be parsed (for example:
awesome_data_pack\computercraft\<files here>
).