Siloed - Revision history

Adamcolton: /* Hidden */

2016-06-17T14:15:50Z

Hidden

← Older revision		Revision as of 14:15, 17 June 2016
Line 55:		Line 55:
	* Systems: silo components that react to inputs		* Systems: silo components that react to inputs
	* Tables: needs more thought... take data in, perform an action. Mostly for key pads, take in a sequence and either produce a signal or route a signal. But the concept could be broadly applicable.		* Tables: needs more thought... take data in, perform an action. Mostly for key pads, take in a sequence and either produce a signal or route a signal. But the concept could be broadly applicable.
			* Time Velocity: changes the speed of the count down clock. In easier games, it can be used to buy more time. In more difficult games it will accelerate the clock. In very hard games, the clock can start in an accelerated state.

	=== Information ===		=== Information ===

Adamcolton: /* Algorithm */

2016-06-02T15:44:48Z

Algorithm

← Older revision		Revision as of 15:44, 2 June 2016
Line 101:		Line 101:

	=== Convolution ===		=== Convolution ===
	A direct connection in a state is turned into an indirect connection via a component. This may mean adding a component, using the output of a component that's not being used or extending a component.		A direct connection in a state is turned into an indirect connection via a component. This may mean adding a component, using the output of a component that's not being used or extending a component. It should be biased towards reusing components.

	=== Obfuscation ===		=== Obfuscation ===
Line 109:		Line 109:

	When a new code sheet is added, it is wired directly to a terminal, During convolution, it may be indirected.		When a new code sheet is added, it is wired directly to a terminal, During convolution, it may be indirected.

			=== Keypad ===
			Adding a keypad is both a convolution and obfuscation. To add a keypad, we convolute a signal through the keypad and add that to a keycode data sheet. Keycode datasheets are different form code sheets. Code sheets convert a code to a label, key code sheets list a keypad ID and code and list the ID that maps to.

	=== Red Herrings ===		=== Red Herrings ===

Adamcolton: /* Algorithm */

2016-06-02T15:40:29Z

Algorithm

← Older revision		Revision as of 15:40, 2 June 2016
Line 109:		Line 109:

	When a new code sheet is added, it is wired directly to a terminal, During convolution, it may be indirected.		When a new code sheet is added, it is wired directly to a terminal, During convolution, it may be indirected.

			=== Red Herrings ===
			Adds an input or output to component or adds a new component with useless inputs and outputs.

			=== Finalize ===
			During initialization, every player was assigned a win panel and a terminal. During finalization, the rest of the component panels are assigned. We go through the states and count up the number of actions that must be performed on each panel. Then we distribute the panels so that each player has approximately the same number of actions to perform.

	== Versions ==		== Versions ==

Adamcolton: /* Components */

2016-06-02T15:31:05Z

Components

← Older revision		Revision as of 15:31, 2 June 2016
Line 24:		Line 24:
	Components route signals. During convolution, all components can be powered and locked. This adds an indicator interface. All components have a direction, so unless otherwise noted, each component has a mux/demux bool. For instance a mux keypad has many inputs but a single output, where a demux keypad has many outputs to a single input.		Components route signals. During convolution, all components can be powered and locked. This adds an indicator interface. All components have a direction, so unless otherwise noted, each component has a mux/demux bool. For instance a mux keypad has many inputs but a single output, where a demux keypad has many outputs to a single input.

	* Keypads		* Keypads: Special one to many, automatically requires a data sheet to indicate what code does what thing
	** Symbol: A grid of symbols		** Symbol: A grid of symbols
	** Labels: A column of labels, each with a button and indicator		** Labels: A column of labels, each with a button and indicator

Adamcolton: /* Panels */

2016-06-02T15:29:49Z

Panels

← Older revision		Revision as of 15:29, 2 June 2016
Line 21:		Line 21:
	Every panel will have a label and possibly and indicator. Each user will have some fixed number of panel. In the main view, they can see an icon for each panel (though not the state or label of the panels). Clicking on a panels zooms in on that panel and places a set of 5 buttons to the left - zoom out and arrow keys to move between panels without zooming.		Every panel will have a label and possibly and indicator. Each user will have some fixed number of panel. In the main view, they can see an icon for each panel (though not the state or label of the panels). Clicking on a panels zooms in on that panel and places a set of 5 buttons to the left - zoom out and arrow keys to move between panels without zooming.

	=== ~~Input and Routing~~ ===		=== Components ===
	~~These~~ can ~~act as~~ inputs, ~~but anything that can~~ input ~~can also route~~.		Components route signals. During convolution, all components can be powered and locked. This adds an indicator interface. All components have a direction, so unless otherwise noted, each component has a mux/demux bool. For instance a mux keypad has many inputs but a single output, where a demux keypad has many outputs to a single input.

	* Keypads		* Keypads
	** Symbol: A grid of symbols		** Symbol: A grid of symbols
Line 30:		Line 31:
	** Groups: a boarder around a set of controls		** Groups: a boarder around a set of controls
	** Buttons		** Buttons
	** ~~Switches: toggles between two states~~		* One to many:
	** ~~Knob~~: ~~Has~~ 3-7 ~~states~~ arrayed over a 120° arc.		** switch 2 outputs
	* Plug board: labeled sockets with a fixed number of wires.		** knob: 3-7 arrayed over 120° arc
	** Socket Types		* Plug board: many to many, labeled sockets with a fixed number of wires
	*** Power Source		** Black: two plugs, general purpose
	*** Signal Source		** Green: two plugs, needed for "high voltage"
	*** Other Panels		** Blue: two plugs, needed for "high frequency" signals
	** Wire Types
	*** Black: two plugs, general purpose
	*** Green: two plugs, needed for "high voltage"
	*** Blue: two plugs, needed for "high frequency" signals

	Any of these can act as either an input or a router. Wiring something like "+12V" to "Close Doors" is like pushing a "Close Doors" button. But knobs and switches can also easily route, and entering the right sequence in a keypad could also route, generate or some combinations (entering "1234" in a certain keypad could produce a signal as output, produce a signal and route it to a specific place, or route a signal from one place to another place).		Any of these can act as either an input or a router. Wiring something like "+12V" to "Close Doors" is like pushing a "Close Doors" button. But knobs and switches can also easily route, and entering the right sequence in a keypad could also route, generate or some combinations (entering "1234" in a certain keypad could produce a signal as output, produce a signal and route it to a specific place, or route a signal from one place to another place).

Adamcolton: /* Versions */

2016-06-02T15:21:12Z

Versions

← Older revision		Revision as of 15:21, 2 June 2016
Line 116:		Line 116:

	=== 1.0 ===		=== 1.0 ===
	* Signals		The goal of 1.0 is the most basic playable, that will already require a lot of work. Users, game setup, drawing panels and panel navigation. To have a minimally playable game (though it may not be that much fun), the only two component types will be indicators and knobs.
	* ID labels
	* LEDs
	* Knobs		=== 2.0 ===
			The obfuscation version. Add terminals, codes and data signals.

			=== 3.0 ===
			Keypads, switches.

			=== 4.0 ===
			Oscilloscopes. This requires the obfuscation model to be reworked a little because a player can discover what type of signal it is by looking at it on an oscilloscope. They can deduce things like "this is data, so send it to a terminal" without explicit labeling.

	[[Category:STGames]]		[[Category:STGames]]
	[[Category:Code]]		[[Category:Code]]

Adamcolton at 15:13, 2 June 2016

2016-06-02T15:13:22Z

@@ Line 1: / Line 1: @@
 Very much based off the Bomb game we played at Bells, just want to explore the concept in a different direction.
 == Terminology ==
@@ Line 7: / Line 9: @@
 * Code: a string of random, chars
 * Cipher: One or more glyphs that must be looked up in the correct cipher table to be interpreted
-* ID: a meaningful string of chars ("Gimble-12", "+12v" or "Cancel")
+* ID: a meaningful string of chars ("Gimble-12", "+12v" or "Cancel"), every connection in the game has an ID
-* Label: Either a code, cipher or ID displayed to the user
+* Label: Either a code, cipher or ID displayed to the user, the inputs and outputs of every component is labeled.
 * Sequence: User input to a keypad
 * LED: A small light. They can be red, green, blue or yellow. They can be on, off or blinking.
@@ Line 78: / Line 80: @@
 And, a single instruction can reference another procedure.
 == Versions ==

Adamcolton at 14:40, 2 June 2016

2016-06-02T14:40:41Z

← Older revision		Revision as of 14:40, 2 June 2016
Line 39:		Line 39:
	*** Green: two plugs, needed for "high voltage"		*** Green: two plugs, needed for "high voltage"
	*** Blue: two plugs, needed for "high frequency" signals		*** Blue: two plugs, needed for "high frequency" signals
	*** Yellow: Three plugs, one in, two out
	*** Purple: Three plugs, two in, one out

	Any of these can act as either an input or a router. Wiring something like "+12V" to "Close Doors" is like pushing a "Close Doors" button. But knobs and switches can also easily route, and entering the right sequence in a keypad could also route, generate or some combinations (entering "1234" in a certain keypad could produce a signal as output, produce a signal and route it to a specific place, or route a signal from one place to another place).		Any of these can act as either an input or a router. Wiring something like "+12V" to "Close Doors" is like pushing a "Close Doors" button. But knobs and switches can also easily route, and entering the right sequence in a keypad could also route, generate or some combinations (entering "1234" in a certain keypad could produce a signal as output, produce a signal and route it to a specific place, or route a signal from one place to another place).
Line 80:		Line 78:

	And, a single instruction can reference another procedure.		And, a single instruction can reference another procedure.

			== Versions ==

			=== 1.0 ===
			* Signals
			* ID labels
			* LEDs
			* Knobs

	[[Category:STGames]]		[[Category:STGames]]
	[[Category:Code]]		[[Category:Code]]

Adamcolton at 20:06, 5 November 2015

2015-11-05T20:06:09Z

← Older revision		Revision as of 20:06, 5 November 2015
Line 80:		Line 80:

	And, a single instruction can reference another procedure.		And, a single instruction can reference another procedure.
			[[Category:STGames]]
			[[Category:Code]]

Adamcolton at 20:05, 5 November 2015

2015-11-05T20:05:24Z

← Older revision		Revision as of 20:05, 5 November 2015
Line 1:		Line 1:
			Very much based off the Bomb game we played at Bells, just want to explore the concept in a different direction.

	== Terminology ==		== Terminology ==
	* Char: a recognizable character (ascii 32-126)		* Char: a recognizable character (ascii 32-126)