Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/ilyvion/ilyvion-laboratory


https://github.com/ilyvion/ilyvion-laboratory

rimworld-mod

Last synced: 8 days ago
JSON representation

Awesome Lists containing this project

README

        

[![RimWorld 1.3](https://img.shields.io/badge/RimWorld-1.3-brightgreen.svg)](http://rimworldgame.com/) [![RimWorld 1.4](https://img.shields.io/badge/RimWorld-1.4-brightgreen.svg)](http://rimworldgame.com/) [![RimWorld 1.5](https://img.shields.io/badge/RimWorld-1.5-brightgreen.svg)](http://rimworldgame.com/) [![Build](https://github.com/ilyvion/ilyvion-laboratory/actions/workflows/ci.yml/badge.svg)](https://github.com/ilyvion/ilyvion-laboratory/actions/workflows/ci.yml)

> [!IMPORTANT]
> You might be used to downloading people's GitHub mods by using the **Code -> Download ZIP** method, but this won't work on my repos[^badpractice]; I make use of proper releases and you can always find the latest version of the mod for download on the [Releases page](https://github.com/ilyvion/ilyvion-laboratory/releases/latest).

ilyvion's Laboratory is a library/framework mod for use by my other mods to avoid code duplication across my mods. Anyone is free to make use of this as a dependency, but I don't want to promise that things won't break for third parties, so depend on it at your own risk. I'll do my utmost to prevent breakage, though, so there's a very low (but still non-zero) chance you'll be screwed.

Just to be perfectly clear: **_I take no responsibility whatsoever if your mod blows up due to me making a change to this mod — depend on it at your own risk and don't @ me if something breaks for you!_**

## License

Licensed under either of

- Apache License, Version 2.0, ([LICENSE.Apache-2.0](LICENSE.Apache-2.0) or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license ([LICENSE.MIT](LICENSE.MIT) or http://opensource.org/licenses/MIT)

at your option.

`SPDX-License-Identifier: Apache-2.0 OR MIT`

### Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in the work by you, as defined in the Apache-2.0 license, shall be
dual licensed as above, without any additional terms or conditions.

[^badpractice]: I think this is really bad practice, but I won't fault less experienced developers for not setting up a whole build and release workflow since it's a rather advanced DevOps topic. Still, you won't find me doing it because, again, I think it's really bad practice for a whole host of reasons.