LibVilNam
跨模组村庄名称生成兼容库。
欢迎来到 [YOUR VILLAGE NAME HERE],村长大人!UwU
我到底在看什么字母汤?
VibVilNam 是一个村庄名称库(这其实就是它的名字,只是采用了 Linux 命名约定,所以所有单词都缩短到最多 3 个字符,并且“Library”放在前面而不是后面——就像“C Library”变成“LibC”一样),其他任何模组都可以使用它来以跨兼容的方式为村庄附加名称。
这到底是什么意思?
想象一下,你有一个模组会在村庄中放置某种交通标记(也许交通方式是步行,而标记是小地图上的路标;也许是一个传送石模组;也许是一个连接到程序生成网络的火车站),而另一个模组会在你进入村庄时欢迎你(也许是类似旅行者标题的东西,但针对村庄;也许是基于符号的)。现在,如果模组说“欢迎来到 (村庄 X)!”然后交通标记也被称为“(村庄 X)”,那该 多么美妙 啊?不幸的是,今天还不可能做到这一点。
……除非模组集成了 LibVilNam! 没错!厌倦了在运行足够大的整合包时多个模组给出冲突的村庄名称吗?我们来救场了!LVN 提供了一个库,其他模组作者可以挂钩其中,使其村庄名称与所有也支持 LibVilNam 的其他模组保持一致(见下文列表)。在某些情况下,模组本身甚至可能不需要直接支持 LVN,因为我们有一个迄今为止较短(但稳步增长)的官方集成列表,用于流行模组,我们在 LibVilNam 本身内为其维护支持。
你只有一个村庄命名模组?LibVilName 也可能有用!大多数名称生成模组只是盲目地将形容词/名词和城市般的词组合在一起,并从它们形成一个名称(例如 Sunnyvale、Steamtown、Icetopia 等)。这没问题,但很快就会变得重复和无聊。LVN 使用一种不同的技术,称为马尔可夫链,这有点像一个小 LLM(好吧,如果它很小,那么它就不再是 大型 语言模型,但你明白了)。它在提供的数据集上训练其对给定语言如何连接其音节的理解(参见下面的配置 LibVilNam 以了解如何提供它),然后尝试从中推断。这一切意味着你会得到听起来更真实且独特的名称,而且你对生成的名称风格有很大的控制(只需使用不同的训练数据集),让你可以相当容易地更改例如语言,甚至回到那些旧的重复名称(如果你出于某种原因喜欢它们)。[注意,马尔可夫链不支持任何花哨的 LLM 优化概念,如注意力机制(这是每个现代聊天机器人的核心),这在理论上使它们比 LLM 在内存效率方面更低(如果使用马尔可夫链生成一个完整的段落,它们需要太字节级的 RAM),但它们需要非常少的内存 开销(你的数据集本身就是模型——无需将数十 GB 的模型权重加载到 GPU 中),这在实践中使它们比 LLM 更适合生成短的单字序列(如村庄名称)——由于这一点,LVN 完全在你的 CPU 上本地运行,你不需要(实际上也不能)将任何 AI 垃圾 API 令牌放在任何地方。]
下载
支持的模组
以下是支持的模组列表。如果模组标记为 [AUTO],则不需要额外配置,它会自行获取 LibVilNam(或 LibVilNam(或第三方集成器)会获取它)。
第一方支持
这些是直接使用 LibVilNam 的模组,无论是将其作为直接依赖项还是作为额外的可能集成:
目前这里什么都没有! 构建了带有 LibVilNam 支持的模组?请向此文件提交 拉取请求,我们很乐意展示你作为我们的第一个消费者!
第二方支持
LibVilNam 本身通过 Mixins 与以下模组集成:
第三方支持
以下模组提供了 LibVilNam 和一些其他模组之间的集成:
目前这里什么都没有! 构建了带有 LibVilNam 支持的模组?请向此文件提交 拉取请求,我们很乐意展示你作为我们的第一个消费者!
用法 - 对于普通玩家
LibVilNam 的最基本用法简单得可笑。对于大多数模组(上面标记为 [AUTO] 的模组),你所需要的就是安装 LVN 和所选模组,你就可以享受模组间共享的村庄名称。有时,你可能需要安装一个额外的模组(上面第三方支持列表中的模组)来弥合差距,或者更改一些配置值以明确启用 LVN 支持(如果没有 [AUTO] 标记)。这是特定于模组的,因此这里没有记录。
然而,对于高级用途,请参见下文:
配置 LibVilNam
LibVilNam 的配置文件取决于你的模组加载平台。在 Forge 上,你可以在 ~/.minecraft/config/lvn-common.toml 找到它;而在 Fabric 上,则是 ~/.minecraft/config/lvn.properties(Linux 客户端通过官方 Minecraft 启动器运行,两者均适用——请根据你的操作系统、客户端/服务器情况以及启动器自行调整)。无论文件位于何处,它将包含以下键值:
padding: 村庄在每个方向上应额外声明多少区块作为其领土?这是为了容纳那些生成于村庄 附近(但并非 内部)的结构类模组,例如 Railways Untended 车站。默认值为 3(可配置范围为 1-5),此外还会向上取整到村庄边界框之外的最近一个区块(核心行为,不可配置)。
do_villagelike: 是否应该为“类村庄”结构(即那些通常拥有人形居民且看起来不像古代遗迹的结构,如林地府邸或堡垒遗迹)命名,还是我们只给真正的村庄命名?如果设为 true,将同时在 #minecraft:village 和 #lvn:villagelike 标签中查找结构;如果设为 false,则仅针对 #minecraft:village。如果你希望更精细地控制哪些结构被视为村庄,可以使用数据包编辑上述标签。
dataset: LibVilNam 用于训练其马尔可夫链村庄名称生成的数据集。单词之间以空格分隔。默认提供一个听起来像波兰语的名字集,详见下方的默认值说明。
lang: 上述数据集所用语言的破折号分隔的区域设置代码。如果使用奇幻语言,请选择一种字母表最接近的现实世界语言。不用担心,它不需要是字母表的严格子集/超集(即使是老牌的英语也足以应对大多数情况),只要别做太蠢的事,比如用日语数据集搭配希腊字母即可。默认值为 pl-PL 以匹配上述数据集。
选择数据集
默认情况下,LibVilNam 会在 此数据集 上训练其马尔可夫链。这是一个 精心挑选 的列表,包含 四千多个 各种波兰地理地名(村庄、城市、省 voivodeships、乡 gminas 和县 powiats —— 由于数据获取方式的原因,其中一些词也可能是街道名称的一部分)。我们决定走这条路,而不是在美国或英国地名上进行训练,原因是:
- 该模组最初是为 GhostLand 8 开发的,而 GhostLand 是一个波兰社区/整合包/SMP/Discord/我真的不知道 GhostLand 到底是什么 tbh,它有点像现代 Xbox 品牌营销,什么都聚在一起,我们希望这一版的名字更让人熟悉;以此区别于前几版拥有村庄名字的版本(第 6 版和第 7 版),那时的所有名字都是泛美式(参见上文大多数名称生成器的工作原理——巧合的是,这也似乎是美国为其县命名的方式)。
我们本可以仅仅在这个数据集上单独用于 GhostLand,但我花了太多时间使其可用,并且想要展示一下。
- 我们想利用这个项目的文化优势,为用户提供 真正独特 的体验。有点像《巫师》,你不会真的发现像所有重复性 MMO 或抽卡游戏中那种-generic-ass 哥布林或史莱姆,而是那些从我们当地的波兰/斯拉夫民间传说中汲取灵感的怪物,大多数玩家喜欢这种探索因素。同样地,由于作者对波兰语的熟悉程度(鉴于她一生都在这里长大),LibVilNam 生成的名字可以听起来非常独特地具有波兰特色,这让你能够探索这种语言的深度,因此应该更加有趣。
……理论上是这样。在实践中,我们理解有些玩家可能不想处理必须发音 „Sokołobrychodnorostrów”(我们在开发过程中由生成器产生的真实名字)的问题。出于这个原因,我们提供了通过使用不同数据集来更改生成器工作方式的能力。具体的操作指令在上面,这里我更想专注于如何获取它。一般来说,你有两条路线:要么从当地政府下载数据库并尝试自己处理数据(除非你们的政府提供的东西比我们的更有用),要么前往 SamCodes Markov,按下 Settings,设置 Length Range 3-23 + Order 3 + Prior 0.00 + Backoff 0(这些是 LibVilNam 使用的参数),并开始摆弄预制的数据集,直到找到一个能生成看起来像你可能会使用的名字的数据集。如果你需要一个起点,我们发现他们的 „Currencies” 数据集产生了一些有趣的结果,作为某种非特定奇幻语言看起来很酷(至少如果你假设 „Mark” 在该语言中意味着城市/城镇/村庄等,因为该后缀似乎相当常见)。
游戏内命令
/lvn-getvillage 用于确定你当前所在的村庄,以及是否在任何村庄中(使用所有 4 种可用的定位村庄策略)
/lvn-rename 用于重命名你当前所在的村庄(由上述命令打印的第 1 种策略确定)
世界文件
LibVilNam 在 ~/.minecraft/saves/[world name]/lvn/[dimension namespace]/[dimension id].csv 之间持久保存其村庄名称以便重启后继续使用。例如,对于位于 „My Forever World” 世界的 minecraft:overworld 维度中的村庄,路径将是:~/.minecraft/saves/My Forever World/lvn/minecraft/overworld.csv。
用法 - 面向使用者
目前还没有开发者指南或社区。我能说的只是使用 Modrinth Maven 添加依赖,然后查看我们在 GitHub 上的公共 API 来了解如何与之交互(真的很简单,我保证)。API 的实例可以通过 hub.guzio.lvn.internal.Main.i().getAPI() 获取(这是你唯一一次应该与 internal 包交互的机会,因为其中的其他内容高度依赖于平台和版本——与此同时,hub.guzio.lvn.API(除其构造函数外)和 hub.guzio.lvn.Village 中的公共方法都保证遵循语义化版本控制 SemVer)。
许可协议
- 代码和二进制文件均根据 MIT 许可证授权。本项目应用了两个 MIT 许可证:一个适用于大部分代码,另一个 适用于 Felix 的马尔可夫链库,该项目将其硬嵌入其中(并非通过 Gradle 作为软依赖,因为其生成器需要进行大量修改才能在此处使用(这就是为什么我也将自己列为 2026 年及以后的贡献者,这并不违反 MIT 许可证,因为原作者的版权声明和免责声明均已按要求保留),而且我也不担心更新问题,因为它似乎已被弃用)。
- 是的,这意味着你可以在整合包中使用它。是的,甚至在 Modrinth 之外的整合包中(没错,甚至是 CurseForge——只需直接包含文件即可),但在该情况下(为了符合 MIT 许可证的要求),你需要注明本模组的作者,方法是“在衍生作品中包含其许可证”。理想情况下,这应该是 README 许可证脚注中一个简单的链接,包含作者和模组名称(就像这样)——而不是埋在两层 ZIP 文件深处(先是整合包,然后是模组),即使这在技术上仍然算作包含。
- 请勿将此模组原样重新上传(或重新编译+上传,除非进行了重大更改(和/或此模组已弃用且你想保持其更新))到其他平台,特别是 9Minecraft(包括植入病毒不算作“重大更改”)或 CurseForge。不,CurseForge,我不关心这在 MIT 下在技术上是否合法。如果你拒绝下架任何冒充者,那么我就称这段文字为“具有法律约束力”(因为它技术上在上面提到了许可证,所以我们真的能确定它不像 GitHub 上的
LICENSE 文件或 Modrinth 上链接的许可证那样有效吗?我的意思是……当然不是(这只是一个解释性脚注),但是——你知道——你真的能确定吗?你敢冒着穿越这片法律灰色地带的风险吗,CurseForge?)并看看你会怎么操作……
- 内置的马尔可夫链训练数据集根据
CC BY-NC 4.0 许可。
- 徽标是由 NanoBananna 凭感觉绘制的,因为我完全不知道我想要这个项目的徽标看起来是什么样(但我还是想加点什么),更不用说我有能力把它做得像样了。既然我对这种粗制滥造的作品没有情感依恋,你可以随意处理它;我特此将其发布在
CC BY 4.0 下(这基本上就是图像的 MIT 许可证)。我没有选择完全的 CC0 公共领域 的唯一原因是,万一这个徽标最终出现在某个关于 AI 的吐槽视频中作为背景素材,我希望我的项目得到署名~~(听着,作为一个 Minecraft 模组,你很少有机会做广告;必须绝望地采取“有曝光就好”的策略~~,尤其是考虑到这个真正的模组是由人类制作的!,所以不会发生“氛围编码”带来的厌恶感/劝退效果)。
- 你不能直接复用 LibVilNam 的名称(至少添加一些后缀之类的东西)用于任何分支或(尤其是)不相关的项目。
鼓励的话
*如果你碰巧比我更有想法,并且设法实现了这个想法(或者只是想让人类化 NanoBannana 的“想法”的当前实现——说实话,整体设计相当不错(带有马尔可夫字面链和一些类似徽章风格的设计),只是极其不连贯(告示牌上生成的 3 个名称示例中有 2 个明确不是此模组所做的名称生成类型;链条扭曲成了怪物;书本看起来一点也不像 Minecraft)且缺乏灵魂),欢迎提交带有你的徽标的拉取请求! 如果你按照 CraftLDAP-风格的徽标许可理念发布 artwork,即根据 CC BY-NC-ND 4.0 许可,并愿意降低对善意衍生作品的要求(其中之一必须是 LibVilNam 本身,否则我将完全无法在法律上使用它)或其他更宽松的条件,那就更好了(我只是希望避免不允许衍生的东西(尽管任何贡献都值得赞赏,我相信可以达成某种安排),因为我认为这与任何创意作品的精神相悖——这就是为什么我将所有内容都发布在 MIT 下的原因)。
就这些了!
希望你享受这个愚蠢的小项目 :3
LibVilNam
Cross-mod village name generation compatibility library.
Welcome to [YOUR VILLAGE NAME HERE], village-chief-sama! UwU
What in the alphabet-soup am I looking at?
VibVilNam is a village names library (that's actually just its name, except it's written in the Linux naming convention, so everything is shortened to 3 characters max, and „Library” goes first not last - just like „C Library” becomes „LibC”), that any other mod can use to attach names to villages in a cross-compatible way.
And what the hell does that mean?
Imagine you have one mod that places some kind of transportation markers in villages (maybe the transportation method is walking and the marker is a minimap waypoint; maybe it's a waystone mod; maybe it's a train station attached to a procedurally generated network) and another mod that welcomes you when you enter a village (maybe something like Traveller's Titles, but for villages; maybe something sign-based). Now, wouldn't it be oh' so nice if the mod said „Welcome to (village X)!” and then the transportation marker was also called „(village X)”? Unfortunately, this isn't possible today.
...Unless the mod integrates with LibVilNam! That's right! Tired of multiple mods giving conflicting village names, when running large enough modpacks? We're here to the rescue! LVN provides a library that other mod authors can hook into to make their village names consistent with all other mods that also support LibVilNam (see list below). In some cases, the mods themselves may not even have to support LVN directly, as we have an as-of-yet-short (but steadily growing) list of official integrations with popular mods, for which we maintain support inside LibVilNam itself.
Do you only have a single village-naming mod? LibVilName can be useful, too! Most name-generating mods just blindly toss together an adjective/noun and a city-like word, and form a name from them (for example, Sunnyvale, Steamtown, Icetopia, etc.). This is fine, but it quickly gets repetitive and boring. LVN uses a different technique, called a Markov Chain, which is kinda like a small LLM (well, if it's small, then that's no longer a Large Language Model, but you get the idea). It trains its understanding on how a given language connects its syllables in a provided dataset (see Configuring LibVilNam below on how to provide it) and then tries to extrapolate from there. All this means that you get much more realistic-sounding and unique names, and you also have a lot of control over the style of generated names (just use a different training dataset), letting you fairly easily change eg. languages or even go back to those old repetitive names (if you liked them, for some reason). [ Note, that Markov Chains don't support any fancy LLM optimization concepts like Attention (which sits at the core of every modern chatbot), which theoretically makes them less memory-efficient than an LLM (if one was to use a Markov Chain to generate a full paragraph, they'd need exabytes of RAM), but they need very little memory overhead (your dataset itself kinda is the model - no need to load tens of GBs of model weights into a GPU), which in practice makes them far better than LLMs for generating short one-word sequences (like a village name) - thanks to this, LVN runs fully locally on your CPU, and you don't need to (can't, actually) put any AIslop-API tokens anywhere. ]
Download
- From Modrinth
- On GitHub, please build from source or download a release.
- CruseForge support is not planned.
Supported mods
Below is the list of supported mods. If a mod is marked as [AUTO], no extra config will be needed, and it picks up LibVilNam (or LibVilNam (or 3rd-party integrator) picks it up) automatically.
1st-party support
These are the mods that use LibVilNam directly, either by relying on it as a direct dependency or as an extra possible integration:
Nothing here yet! Built a mod with LibVilNam support? Please open a pull request to this file, we'd love to showcase you as our first consumer!
2nd-party support
LibVilNam itself integrates with those mods via Mixins:
3rd-party support
The following mods offer integration between LibVilNam and some other mods:
Nothing here yet! Built a mod with LibVilNam support? Please open a pull request to this file, we'd love to showcase you as our first consumer!
Usage - For regular players
Most basic usage of LibVilNam is laughably simple. For most mods (those marked as [AUTO] above), all you need is to install LVN and the chosen mod, and you can enjoy shared village names between mods. Sometimes, you may need to install an extra mod (those in the 3rd-party support list above) to bridge the gap, or to change some config value to explicitly enable LVN support (if there is no [AUTO] marking). That's mod-specific, so it's not documented here.
For advanced use, however, see below:
Configuring LibVilNam
LibVilNam's config file depends on your modding platform. On Forge, you'll find it at ~/.minecraft/config/lvn-common.toml and for Fabric, it's ~/.minecraft/config/lvn.properties (Linux client via the official Minecraft launcher for both - adjust for your OS, client/server situation, and launcher yourself). Wherever your file is, it will contain the following keys:
padding: How many extra chunks in every direction should a village claim as its own territory? This is done to account for mods that spawn structures close to (but not inside) villages, like Railways Untold stations. Defaults to 3 (configurable 1-5), on top of rounding-up to the nearest chunk outside of the village's bounding box (core behavior, cannot be configured).
do_villagelike: Should „village-like” structures (ie. those that generally have some humanoid-ish inhabitants and don't seem like some ancient ruins, such as Woodland Mansions or Bastions) also be given names, or do we only assign names to actual villages? Will look for structures in both #minecraft:village and #lvn:villagelike tags if true, only for #minecraft:village if false. If you want more fine-grade control over what structures count as villages, you can edit the aforementioned tags using a datapack.
dataset: The dataset on which LibVilNam trains its Markov Chain village name generator. Words are space-separated. Defaults to one that gives you Polish-sounding names, see below for defaults.
lang: Dash-delimited locale code for the language in which the dataset above is written. If using a fantasy language, pick an IRL one with the closest-matching alphabet. Don't worry, it doesn't need to be a strict subset/superset of letters (even the good'ol English should be enough for most cases), just don't do anything too stupid, like a dataset in Japanese and a Greek alphabet. Defaults to pl-PL to match the dataset above.
Picking a dataset
By default, LibVilNam trains its Markov Chain on this dataset. It's a hand-curated list of over four thousand various Polish geographical place-names (villages, cities, wojweództwos, gminas, and powiats - and some words may be parts of street-names, too, because of how the data was obtained). We decided to go this route, instead of training it on eg. American or British places, because:
- This mod was initially developed for GhostLand 8, and GhostLand is a Polish community/modpack/SMP/Discord/I-don't-really-know-what-GhostLand-is-tbh-it's-kinda-like-modern-Xbox-branding-where-it's-everything-all-at-once, and we wanted the names to be more familiar this edition; something to differentiate it from prior editions with village names (6 and 7), where all names were generically-American (see: how most name generators work, above - and coincidentally, this also seems to be how USA invents its counties).
We technically could've just used this dataset on GhostLand alone, but I spent too much time on making it usable and wanted to show off.
- We wanted to leverage this project cultural advantage to provide a genuinely unique experience to our users. Kinda like in The Witcher, you don't really have generic-ass goblins or slimes, that you'd find in all repetitive MMOs or Gatcha games, but rather monsters that draw inspiration from our local Polish/slavic folklore, which most players enjoy, due to a certain exploratory factor. Likewise, because of the author's familiarity with the Polish language (given how she grew up here all her life), names generated by LibVilNam can sound uniquely-Polish, which lets you explore the depths of this language and should as such be more enjoyable.
...in theory. In practice, we understand that some players may not want to deal with having to pronounce „Sokołobrychodnorostrów” (*real name produced by our generator during development). For that reason, we offer the ability to change how the generator works by using a different dataset. The exact instructions for doing that are above, here I'd like to instead focus on obtaining it. In general, you have 2 routes: either you download a database from your local government and try to massage the data yourself (unless your gov't provides more useful stuff than ours), or you head over to SamCodes Markov, press Settings, set Length Range 3-23 + Order 3 + Prior 0.00 + Backoff 0 (that's the params used by LibVilNam), and start messing around with pre-made datasets until you find one that generates names that look like something you might want to use. If you need a starting point, we found that their „Currencies” dataset produces some interesting results, that look great as some sort of non-descript fantasy language (at least if you assume that „Mark” means city/town/village/etc. in that language, as that suffix seems somewhat common).
In-game commands
/lvn-getvillage to figure out in what village are you right now, and if in a village at all (using all 4 available strategies for locating villages)
/lvn-rename to rename the village you're currently at (determined by the 1st strategy printed by the command above)
World files
LibVilNam persists its village names between restarts in ~/.minecraft/saves/[world name]/lvn/[dimension namespace]/[dimension id].csv. For example, for villages located in the minecraft:overworld dimension of the „My Forever World” world, the path will be: ~/.minecraft/saves/My Forever World/lvn/minecraft/overworld.csv.
Usage - For consumers
There is no developer guide or community yet. All I can say is use Modrinth Maven to add a dependency, and then check out our public API on on GitHub to figure out how to interact with it (it's really simple, I promise). An instance of the API can be obtained via hub.guzio.lvn.internal.Main.i().getAPI() (that's the 1st and last time one should ever interact with the internal package, as everything else there is highly platform- and version-dependent - meanwhile, public methods in hub.guzio.lvn.API (except for its constructor) and hub.guzio.lvn.Village are guaranteed to follow SemVer).
License
- The code and the binaries are licensed under MIT. There are two MIT licenses applied to this project, one governs most of the code and the other one applies to Felix's Markov Chain library that this project hard-embeds inside (not a soft-dependency via Gradle due to the fact that his generator needed some extensive modifications to be usable here (this is why I also included myself as the 2026 and onwards contributor in the license, which is not against the MIT license, as both the original author's copyright note and the disclaimer are preserved as needed) and it's not like I'm concerned about updates, given that it seems to be abandonware)
- Yes, that means that you can use this in modpacks. Yes, even in packs outside Modrinth (yep, even CF - just use a direct-file-inclusion), although in that case (to comply with MIT license requirements), you'd need to credit this mod, by „including its license in derived work”. Ideally, that'd be a simple link to the license, with the author's and the mod's name, directly in your pack's README's license footnote (like this one) - not buried deep within 2 layers of ZIPs (first the pack, then the mod), even if that's technically still inclusion.
- Do not reupload (or recompile+upload, unless significant changes were made (and/or this mod got abandoned and you want to keep it updated), as part of a complete fork) this mod as-is onto other hosts, notably 9Minecraft (*including a virus doesn't count as „significant changes”) or CurseForge. No, CurseForge, I don't care how technically legal it would be under MIT. If you refuse to take down any impersonators, then let me call this little string of text „legally binding” (Because it technically says License above, so can we really be sure that it's not as valid as the
LICENSE file on GitHub or the linked license on Modrinth? I mean... Of course it's not (this is merely an explainer footnote), but - you know - can you really be sure? How brave would you be to passage over this vail of legal gray-zone, CurseForge?) and see how you roll...
- The built-in training dataset for the Markov Chain is licensed under
CC BY-NC 4.0.
- The logo is vibe-drawn by NanoBananna because I had absolutely no idea* what would I even want this project's logo to look like (but I still wanted to add something), let alone would I have the abilities to make it look in any way decent. Since I don't hold any emotional attachment to slop, you're free to do whatever with it; I hereby release it under
CC BY 4.0 (which is basically MIT for images). The only reason why I'm not going with a full-on CC0 Public Domain is that just in case this logo ends up being a B-Roll in some rant about AI, I want my project credited (listen, you don't get a lot of opportunities for advertising as a Minecraft mod; gotta be desperate and go with an all-press-is-good-press approach, especially with how the actual mod was made by a human!, so no „vibe-coding” ick/turnoff happens).
- You cannot directly reuse the LibVilNam name (at least add some suffix, or something) for any fork or (especially) unrelated projects.
Words of encouragement
*If you happen to have more of an idea than I did, and also managed to realize said idea (or would just like to humanize the current realization of NanoBannana's „idea” - cuz tbh it pulled-off quite a nice design overall (with the Markov literal-Chain and a sort of emblem-style design), it's just laughably in cohesive (2 out of the 3 generated name examples on the sign are explicitly not the kind of name generation this mod does; the chain is contorted into an abomination; the book looks nothing like Minecraft) and soulles), a pull request with your logo would be hugely welcome! Even more-so if you release the artwork under CraftLDAP-style logo-licensing mentality, ie. license it under CC BY-NC-ND 4.0 with the willingness to lower the requirements for good-faith derivative works (one of which would have to be LibVilNam itself, otherwise I'd literally be legally unable to use it) or something more permissive than this (I just would prefer to avoid stuff that don't allow for derivatives (though any contribution is appreciated and I'm sure an arrangement can be worked out), as I think that goes against the spirit of any creative works - there is a reason why I publish everything under MIT).
That's all!
Hope you enjoy this silly little project :3
评论 0
登录后参与评分
还没有评论,来抢沙发吧