Tag: Branch: Tree: ad8ba5a50b

cornedgy

firefx

master

renaming

stonecollision

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'ad8ba5a50b'

${ noResults }

Commit Graph

7 Commits (ad8ba5a50b042bd60b40ee2145a0243ad1aee8b5)

Author	SHA1	Message	Date
Aaron Suen	ad8ba5a50b	Simplify naming ... The idea of reusing the "stone" from the name was clever, but it has some drawbacks. - It doesn't fit in with NodeCore's generally purely concatenative naming scheme, where adjectives are prepended to general names for things. - It would make translations (or just general understanding) more difficult for non-native speakers. - It's a little weird separating certain words, like tarstone and cloudstone, because "tar" and "cloud" appearing on their own now seem to imply that that material is somehow used in the composition of the go stones. Having all of the stones have "go" in their name also reinforces that these pieces are meant to be part of a logical set, used together, and are meant to be used for the game of go (in case somebody sees one in isolation and doesn't know what it's from). It also makes it easier to just search for "go" in szutil_givemenu and find all the go stones; searching for "stone" yields too many results.	1 year ago
capitalthree	3e3a0ca98d	refactored (generalized) connected-search code. Added aux1 connected-group mining for stones and territory markers, and added flood-fill placement behavior for territory markers, with aux1 as an override to always place one.	1 year ago
capitalthree	6a77451fc0	added smaller territory marker stones for scoring	1 year ago
capitalthree	812bc837ba	deglobalized and unhoisted	1 year ago
capitalthree	6a4acfa519	neighbor search respects both physical walls (solid blocks) and goban-indicated walls	1 year ago
capitalthree	30868bec31	node categorization code to identify go stones, physical walls, empty spaces, and also semantically-meaningful concrete variants	1 year ago
capitalthree	7cd53d2e89	initial commit	1 year ago