User:Ch4zm/Maps Revamp

Version 600

To fix:

• User:Ch4zm/Maps Revamp/Terminology - terminology (patterns, stamp patterns, map patterns, etc.)
• User:Ch4zm/Maps Revamp/Package Reorg - rearrange package into legacy and next gen functionality

To expand:

• User:Ch4zm/Maps Revamp/Two-Color Patterns - define two-color stamp patterns (mixed colors)
• User:Ch4zm/Maps Revamp/Map Pattern Templates - define templating system for map patterns
  • quadrants or sextants
  • spaceship crashes

• User:Ch4zm/Maps Revamp/New Map Patterns

smoothing out verbiage

• "pattern" is the common term for the stamps we're using (circle-dot notation)
• unfortunately, we are also using "pattern" to refer to map name... so we should refer to those patterns as map_pattern
• map pattern = the pattern for that map
• (recursive... a map pattern is composed of other patterns... so is still a pattern... just like a hassler pattern that uses other patterns composed together is itself a pattern)

package organization

lots of questions...

first: pretty settled on this, we'll make an orphan branch and start from scratch

next question is, should package be renamed.

• only thing that uses it is the api, (oh and the gollyx-backend-generator, dang)
• those are using requirements and pointing to a repo
• will swap out default branch so it's now the orphan branch, but still have tags pointing to commits, consistent all the way through
• api will have legacy functionality available
• gollyx-backend-generator should not need anything changed. that api should stay the same.

src/ directory:

• will have a legacy subdir

maps api functionality and import:

• maps lambda api will swap out "maps" import with "maps.legacy"
• legacy endpoints left alone
• new endpoints - how to differentiate? this is where we get some complicated questions

option 1: api endpoint can have /v2/ in them, and package is renamed to maps2

• we're updating the imports anyway, so...
• this might lead to greater expansion of the api - more parameters being fed to maps, not just size, asking for patterns vs map patterns

option 2: don't change the package name, don't add any /v2, just keep piling on new endpoints, everything before Hellmouth VI will use legacy submodule, everything VI and later will use modern stuff

• cut a new version 600
• this is the way

two color patterns

in addition to b3s23_patterns there would be a b3s23_3state_patterns with maybe an x o . notation

└── src
    ├── b3s23_patterns
    │   ├── 78p70.txt
    │   ├── acorn.txt
    │   ├── airforce.txt
    │   ├── backrake2.txt
    │   ├── bheptomino.txt
    │   ├── bisectingpuffers.txt
    │   ├── block.txt
    │   ├── brx46b.txt
    │   ├── bunnies.txt
    │   ├── centinal.txt
    │   ├── century.txt
    │   ├── cheptomino.txt
    │   ├── coespaceship.txt
    │   ├── crabstretcher.txt
    │   ├── cthulhu.txt
    │   ├── dinnertable.txt
    │   ├── dove.txt
    │   ├── eheptomino.txt
    │   ├── eve.txt
    │   ├── flotilla_14wss.txt
    │   ├── fred.txt
    │   ├── glider.txt
    │   ├── gosper_gun.txt
    │   ├── grandpa_13629876.txt
    │   ├── grandpa_305230.txt
    │   ├── grandpa_42100.txt
    │   ├── harbor.txt
    │   ├── heavyweightspaceship.txt
    │   ├── justyna.txt
    │   ├── koksgalaxy.txt
    │   ├── lightweightspaceship.txt
    │   ├── middleweightspaceship.txt
    │   ├── multuminparvo.txt
    │   ├── mustardseed.txt
    │   ├── piheptomino.txt
    │   ├── quadrupleburloaferimeter.txt
    │   ├── rabbit.txt
    │   ├── ring64.txt
    │   ├── roseluck.txt
    │   ├── rpentomino.txt
    │   ├── simkin_gun.txt
    │   ├── spacebunnies.txt
    │   ├── spaceshipgrower.txt
    │   ├── switchbox.txt
    │   ├── switchengine.txt
    │   ├── tagalong.txt
    │   ├── timebomb.txt
    │   ├── twoglidermess.txt
    │   ├── unidimensionalinfinitegrowth.txt
    │   ├── vring64.txt
    │   ├── wickstretcher.txt
    │   ├── wilma.txt
    │   ├── wing.txt
    │   └── x66.txt

patterns

oscillators

name	type	notes
70p70	oscillator	looks like the sun
airforce	oscillator	like a tiny burloafiermeter, think of it as a "safe"
dinnertable	oscillator	our favorite old friend
harbor	oscillator	pretty
koksgalaxy	oscillator	another pretty
quadrupleburloaferimeter	oscillator	the classic safe
ring64	oscillator	pretty
switchbox	oscillator	pretty, flickers

methuselahs

name	type	notes
acorn	methuselah	expands, kicks out to the right side
brx46b	methuselah	very short-lived, doesn't do much
bunnies	methuselah	awesome, develops fast without expanding much, then explodes
centinal	methuselah	this is a big, expanding, perfectly-symmetrical pattern
century	methuselah	very short-lived, hard to do much with this
cheptomino	methuselah	very short-lived, relatively simple, but makes a few spaceships
dove	methuselah	surprisingly effective, big development in small area
eve	methuselah	ugly but effective
fred	methuselah	part of fred & wilma, good development in the center before spreading
grandpa_13629876	methuselah	takes some time to generate a decent ash field, left corner becomes important eventually
grandpa_305230	methuselah	takes some time, again a decent ash field, fades after 600 or so generations
grandpa_42100	methuselah	growth really accelerates with time
justyna	methuselah	good solid one
multum in parvo	methuselah	the worm
mustardseed	methuselah	growth increases with time, starts to really spread out
piheptomino	methuselah	not huge, not long-growing, but very small, effective for random placement with 8 or 10
rabbits	methuselah	interesting that we now have rabbits AND bunnies...
roseluck	methuselah	looks like it's going to die out, then gets a second wind, only lasts 400 gens or so, creates some spaceships
spaceshipgrower	methuselah	this is a good solid fast-developing pattern that throws out some gliders and is super tiny
switchengine	methuselah	solid, fast-growing, gradually-spreading pattern
timebomb	methuselah	nice efficient small pattern
twoglidermess	methuselah	perfect pattern. tiny, glider, mess, and it starts small and expands solidly with time
unidimensionalinfinitegrowth	methuselah	perhaps the simplest methuselah, dimension-wise, just a 1D string of cells... great for creating an ash field
wilma	methuselah	part of wilma & fred, square (looks like QR code), solid growth
wing	methuselah	very small, very fast-developing, not super effective but can rapidly change anything in its near vicinity

spaceships, guns, rakes

name	type	notes
backrake2	glider generator (moving - rake)	this is the set of 3 or 5 puffers, one leaves a wake that the others turn into gliders
bisectingpuffers	spaceship generator	sends medium spaceships out to the left
coespaceship	spaceship	not very big, leaves a little puff of smoke at the back
flotilla_14wss	spaceship	fishhook spaceship, great tool for crashes
gosper_gun	glider generator (static - gun)	ping pong game that generates gliders
heavyweightspaceship	spaceship	there's nothing "heavy" about this one... the light/heavy spaceships are both small and floppy.
lightweightspaceship	spaceship	...rename to consolidate
middleweightspaceship	spaceship	...rename to consolidate
simkin_gun	glider generator (static - gun)	generates gliders up and to the right (might want to rotate 180 to be consistent with other guns)
spacebunnies	spaceship generator	similar to bisecting puffer, this makes a puffer ship while doing some methuselah stuff and making gliders
tagalong	spaceship	like the wickstretcher without the wick. big, slow-moving, horizontal spaceship
x66	spaceship	nice symmetric spaceship moving horizontally

other

name	type	notes
crabstretcher	?	crab that stretches a long strand of squares behind it
block	still life	just a regular ol square
cthulhu	still life	not much of note
wickstretcher	?	this is the "tagalong" spaceship, except it's weaving a web, and there's a base station catching the web behind it.