paradise-lost Wednesday 28 October 2020
- This?
- UD is probably the end portal in that caseAs it does not need to really change orientation, nether does as you can build it two waysAh yes, hereJust an accessor mixin for a bucket's fluidThis one is a bit more complicated, mixin in to WorldRenderer#render to do... bad things https://github.com/Dragonoidzero/Pulse-Flux-MH/blob/master/src/main/java/net/azzy/pulseflux/mixin/ShaderRendererMixin.java
- Uh, an issue I see with the aether is that there is kind of a lack of building blocks. The dimension really doesn't give you much, with probably the most egregious example being woodsI had been thinking about this for a bit but it may be a good idea to add some more wood kinds, giving crystal trees and golden oaks their own wood would be minor, swift, and it would be an assured improvement
- Tbf, working on the Aether just requires some level of knowing what your doing and in my case working with years old Kino-era code And knowlege is gained either from reading docs, or learning from others and their mistakes most of the time...or trying to lone-wolf it and self-teach yourself works sometimes too(edited)
- Ah. I was gonna say if so, technically, you can yeet Kino's code on the dimension and biomes temporarily, then combining your code with that of the already existing item and block code, you can trim down a lot of the work so far.Also I might add that the new textures DO look pretty nice xD
- But here's the list of what was working in Kino's code:
I'm likely missing stuff in this list, though also afaik Aether II added capability for farming in the Aether so technically it can be backported as a new legacy feature since your acting as a "fork" sort to speak for this project assumedly.(edited)- Blocks and Item logic and mechanics working, except for the portal data which can be replaced by kalucky's version (Likely more optimized) - The Api module is complete, since not much really breaks that. In the GOTV branch, there is a merged api module I built that integrated both I and II's api together, since I had the intent of a project built to support both Legacy and Aether II addons - Advancements are working, afaik - Dimensions, Biomes, Feature generation needing revisions from 1.16.x destroying the remanants of Kinos code. Need revisions under any circumstance - Mixins are 90% working, besides the data for the prior point - Json metadata *should* be ok, though likely has minor syntax issues in it, since despite them working, MC threw warnings when last used - I am all up for adding stuff to the aehter to make it nicer (not easier) to live in. It is a fun place to explore but kind of bland and sucky to base in, nothing much to do or build withIt would probably be more fitting of an addon as previously stated thoSomething interesting to think about: The aether was made to be a proper, contrasting dimension to the nether
- Have a base mod/module that adds things as they used to be, and a renewed addon/module that brings it up to par with post 1.16 netherNew biomes, new mobs (maybe a counterpart to piglins), and most certainly new building blocks and farming
- I mean it could have been pulled off, but I'd say too many mistakes were made and not enough developers onto it anymoreAether Legacy originally was also a different story, since before Gilded yanked it, it was being developed on almost daily, on 1.12.2, 1.14.4, a Universal Jar project in process as well (Which allowed usage of 1.7 - 1.12.2 Aether Legacy in a single jar), and the GOTV project too(edited)
- I see Modding as two generalized sides: You can do things for fun and for the community, inspiring others to follow you Or you can run it as a corporation, only looking out for the profit and monetary and fame of it allAnd I definitly see Gilded as a corporation on a sinking ship without a leader
- Azzy, do you happen to have gitlab? I have a feeling you'd have a hoot over some of Kino's intresting coding in this As for me coding on this project, I might be intrested, though I already explained what I'd do first if i were (Which was to merge in Kino's existing logic, except for the broken pieces, which would be reimplemented, to cut down how much initial work is needed before rewrites)
and I'll think about it
