Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[LazyWizard]

Version 2.8 is out, get it here (mirror).

Thanks to Liral for contributing the KeplerOrbit class. Um, several months ago. Something something living up to my username...

Changelog:

2.8 (April 05, 2023)
======================
Updated to be compatible with Starsector 0.96a
Updated bundled libraries:
 - kotlin-stdlib: v1.5.31 -> v1.6.21
 - kotlinx-coroutines: v1.5.2 -> v1.6.4 (custom build)
 - These are the last versions that support Java 7
Added org.lazywizard.lazylib.campaign.orbits.KeplerOrbit:
 - Submitted by Liral, this provides more accurate orbits than EllipticalOrbit
Changes to CombatUtils:
 - Updated to use CombatEngineAPI's bin-lattice system where applicable, as
   requested by several modders since those methods introduction

[Someone432]

Where can I find a version compatible with 0.95? I'm really lost here

[SpaceDrake]

Consult LazyWizard's Github. However, unless you're looking to run a game of Starsector with extremely specific un-updated mods, there's no real reason to run .95 anymore; .96 is just .95 But Better. Still, it's up to you.

[LazyWizard]

Version 2.8b is out, get it here (mirror) (mirror 2).

Changelog:

2.8b (February 02, 2024)
==========================
Updated to be compatible with Starsector 0.97a
Changes to LazyFont:
 - Changed default blendSrc back to GL_SRC_ALPHA (was GL_ONE since 2.4c)
Deprecated org.lazywizard.lazylib.campaign.orbits.KeplerOrbit:
 - Deprecated at the request of its contributor

[Madao]

Thank you for your efforts LazyWizard

[Killer of Fate]

Version 2.8b is out, get it here (mirror) (mirror 2).

Changelog:

2.8b (February 02, 2024)
==========================
Updated to be compatible with Starsector 0.97a
Changes to LazyFont:
 - Changed default blendSrc back to GL_SRC_ALPHA (was GL_ONE since 2.4c)
Deprecated org.lazywizard.lazylib.campaign.orbits.KeplerOrbit:
 - Deprecated at the request of its contributor

holy *** that response time, wtf?

[sanya02]

 If I use version LazyLib v2.8b for 0.95.1. Will there be any problems?

[TimeDiver]

If I use version LazyLib v2.8b for 0.95.1. Will there be any problems?

Won't work; newer releases are NOT backwards-compatible with older versions of StarSector.

Having said that, the download for v2.7b is still around and IS explicitly-compatible with 0.95.1a:

The link: https://github.com/LazyWizard/lazylib/releases/download/2.7b/LazyLib.2.7b.zip

[Vali]

Hey just downloaded the game again after a while of not playing. Im trying to get this mod to work, it said wasn't compatible with the game mode, and then when i tried to re-download it, it wont even show up in the game start menu mod function. Im at a loss as to what to do

[LazyWizard]

LazyLib 3.0 is out, get it here (mirror 1 | mirror 2).

This is a major release that takes advantage of the move to Java 17 to make some long-awaited upgrades. Existing code using LazyLib should remain compatible, but there's a small chance that something could have been broken during the library updates. Please let me know if you encounter any problems!

Full changelog:

3.0 (March 27, 2025)
======================
Updated to be compatible with Starsector 0.98a and Java 17
Updated to Kotlin 2.1 and the K2 compiler
Updated bundled libraries to take advantage of the move to Java 17:
 - kotlin-stdlib: v1.6.21 -> v2.1.20
 - kotlinx-coroutines: v1.6.4 (custom build) -> v1.10.1
 - jetbrains-annotations: v23.0.0 -> REMOVED (now included in kotlin-stdlib)
Changes to jar file locations:
 - Moved LazyLib-Console.jar and Kotlin-Runtime.jar to jars/internal, to
   better signify that they aren't meant to be added as mod dependencies
Added org.lazywizard.lazylib.ShapeUtils:
 - Copy of org.lazywizard.lazylib.opengl.DrawUtils, except its methods
   return a list of vertices instead of drawing the requested shape
Changes to CollisionUtils:
 - Fixed getCollisionPoint(Vector2f lineStart, Vector2f lineEnd,
   CombatEntityAPI target) returning null if entire line was within target's
   bounds without touching a bounds segment (now returns copy of lineStart)
 - getNearestPointOnBounds() no longer requires you to call bounds.update();
   as with all other CollisionUtils methods it now calls update() itself
Changes to ColorUtils:
 - Added genRandomColor(), returns a Color with random RGB values
Changes to FastTrig:
 - atan() properly reduces its argument if it's not between -1 and 1
   (credit to Genir for the bug report and the fix)
Changes to LazyFont:
 - Fixed display of fonts whose texture scaling doesn't match their texture size
   (credit to Psiyon for the bug report and the fix)
 - Added buildUntilLimit(String line, float fontSize, float maxWidth), which
   returns a substring of line that will fit within maxWidth width
 - Unicode smart quotes (single and double) are converted into basic quotes
 - Attempting to create a DrawableString with missing character data will only
   log a warning once per missing character, instead of every time one is used
   (explanation: if the font doesn't define Ç, it will log a warning the first
    time you try to draw one while replacing the missing character with either
    a question mark, or empty space if the font doesn't define a question mark)
 - LazyFont.loadFont() will now make up fake data for a space character if the
   font file lacks one (it creates an invisible pixel with extra padding)
 - Cached fallback char used when font doesn't contain a requested character;
   very slight performance improvement
 - Added missing Javadoc to LazyChar
Changes to VectorUtils:
 - Added toFloatArray(List<Vector2f> vectors), which converts a List of
   Vector2fs into an array of floats containing their coordinates
 - Added toVectorList(float[] coordinates), which converts a float array of
   coordinates into a List of Vector2fs
Removed org.lazywizard.lazylib.campaign.orbits.KeplerOrbit
 - Removed at the request of its contributor
Removed from org.lazywizard.lazylib.ui.LazyFont:
 - Removed drawText(); use createText() instead
 - Removed appendText(); use append() instead
 - Removed getColor() and setColor(); use get/setBaseColor() instead
 - Removed checkRebuild(); use triggerRebuildIfNeeded() instead

[ChocoMoo]

how is this already updated. its only been 2 hours since 0.98

[Gantradies]

i, am having a bunch of issues getting stuff to run properly via TriOS atm-
could be a quirk/bug on its end, but there's a bunch of mods (including ones that just got updated for the new patch!) that are refusing to recognize/enable with lazylib 3.0-
like the ship-weapons pack,
underworld ect-
will poke around at stuff a little, try and see if its an actual problem or the game just being weird on my end xD
has anyone else been seeing anything similar?

[Huntster]

Yes, I'm seeing the same thing as Gantradies. Everything with dependencies are showing errors in TriOS, saying "Required Mods: LazyLib (disabled 3.0.0)" and soforth, even though that's the current version. Bit confusing.

[LazyWizard]

i, am having a bunch of issues getting stuff to run properly via TriOS atm-
could be a quirk/bug on its end, but there's a bunch of mods (including ones that just got updated for the new patch!) that are refusing to recognize/enable with lazylib 3.0-
like the ship-weapons pack,
underworld ect-
will poke around at stuff a little, try and see if its an actual problem or the game just being weird on my end xD
has anyone else been seeing anything similar?

Yes, I'm seeing the same thing as Gantradies. Everything with dependencies are showing errors in TriOS, saying "Required Mods: LazyLib (disabled 3.0.0)" and soforth, even though that's the current version. Bit confusing.

Those mods haven't been updated for 0.98a yet so they might not work anyway, but the issue you're having is because they declare a specific version of LazyLib as a dependency.

You can get them to work (assuming nothing broke in 0.98a) by editing their mod_info.json and removing the line "version": "2.8b", from LazyLib's dependency entry.

[Raatle]

I have a mod in development. CollisionUtils.getCollisionPoint seems to be returning some really odd results in the latest patch. Returning null when it shouldnt or returning values that are vastly inaccurate. Dont know if its linked to 0.98a or Java 17. Will be looking further into it myself.