I think the persean abyss introduced in 0.97a gives a lot of oppertunity to add more towards hyperspace for mods, but there are a few components missing to make it more seamless.
Im gonna mention two things that would be really helpful and i think relatively easy to implement that should help a lot with it.
1. A Settings.json config that disables the clamping of the hyperspace map.
The default behaviour of the hyperspace map (or any map in general) is to not allow moving the camera past the maps bounds.
I think it would be very useful to be able to disable this behaviour through a simple config that a mod can disable if needed.
2. Add a dynamic stat to the player fleet that modifies the abyssal depth.
Replacing the entire "HyperspaceAbyssPluginImpl" class just to modify the abyssal depth would be prone to incompatibility between mods, and is a rather jank way to do so.
I am currently considering adding areas outside of the map bounds, and it would be nice to be able to add a multiplier to the current depth to avoid abyssal behaviour, like the slow down or background change when needed.
3. Enabling a Terrain Plugin to render to the starscape map.
This one is optional, as i asume this requires more work than the others, and is not as essentialy, but being able to only render towards the non-starscape version of the map feels very limiting even outside of the scope im talking here, as most people appear to prefer using the starscape map.
Overall i think most of this would be very useful to modders, as the main area of the persean abyss is very small, and you wouldnt want to clutter it to much, or come in to conflict with whatever a future vanilla update is adding. I would really appreciate if the first two points could be integrated!
Author
Topic: [Modding] Enable modding outside of the bounds of Hyperspace. (Read 285 times)