Rebrand #476

New issue

Open

opened 2026-02-23 23:07:28 +00:00 by LunarTides · 0 comments

LunarTides commented

2026-02-23 23:07:28 +00:00

(Migrated from github.com)

Warning

This was made at midnight, right before going to bed. This issue might be a bit ramble-y, and I might not carry out everything laid out here.

The 4.0 update should probably feature a rebrand.

Version

The version system is kinda stupid. This project is nowhere near stable, nor do i really support any prior version. The stable release of the 3.0 update still has bugs that I caught quickly after release, but haven't patched in stable yet.

Therefore, it would be better to have a 0.x.x system for now, to allow for faster updates. (As opposed to the multi-month long updates currently.)

I'll have to see what version this project should end up at after the rebrand.

Name

You may have noticed that I've been avoiding the name of this project, Hearthstone.js, and have been calling it "this project." You may also have noticed that I've called this issue "Rebrand" instead of "Change version format."

As you may have guessed, it's time for Hearthstone.js to get a new name.

Don't get me wrong, I'm quite attached to the name Hearthstone.js due to nostalgia, but it's a bit too bland. Although this project will probably never completely separate from the identity of a Hearthstone clone, and will probably never outshine the original, I'm quite happy with what I've made, and so want to give it the name I feel it deserves, so that it can walk on it's own, outside the shadow of its "inspiration." (Heavy quotes)

I've not quite settled on a name yet, but I have a few ideas in mind.

Effect

The version change won't cause much trouble.

The name change on the other hand, would require sweeping changes to the codebase. I'd also have to change the subdomain away from "hs." But it shouldn't be that bad.

> [!WARNING] > This was made at midnight, right before going to bed. This issue might be a bit ramble-y, and I might not carry out everything laid out here. The 4.0 update should probably feature a rebrand. ## Version The version system is kinda stupid. This project is nowhere near stable, nor do i really support any prior version. The stable release of the 3.0 update still has bugs that I caught quickly after release, but haven't patched in stable yet. Therefore, it would be better to have a 0.x.x system for now, to allow for faster updates. (As opposed to the multi-month long updates currently.) I'll have to see what version this project should end up at after the rebrand. ## Name You may have noticed that I've been avoiding the name of this project, Hearthstone.js, and have been calling it "this project." You may also have noticed that I've called this issue "Rebrand" instead of "Change version format." As you may have guessed, it's time for Hearthstone.js to get a new name. Don't get me wrong, I'm quite attached to the name Hearthstone.js due to nostalgia, but it's a bit too bland. Although this project will probably never completely separate from the identity of a Hearthstone clone, and will probably never outshine the original, I'm quite happy with what I've made, and so want to give it the name I feel it deserves, so that it can walk on it's own, outside the shadow of its "inspiration." (Heavy quotes) I've not quite settled on a name yet, but I have a few ideas in mind. ## Effect The version change won't cause much trouble. The name change on the other hand, would require sweeping changes to the codebase. I'd also have to change the subdomain away from "hs." But it shouldn't be *that* bad.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

LunarTides/Hearthstone.js#476

No description provided.

Rows
Columns