Tintin - Revision history

Ketsueki: Stitching void rooms within a grid.

2020-05-11T08:33:56Z

Stitching void rooms within a grid.

← Older revision		Revision as of 08:33, 11 May 2020
Line 237:		Line 237:
	===Eureka===		===Eureka===

	Eureka is recent enough to have an OK coverage on the [https://flexiblesurvival.com/mapping official map]. However as you can see from glancing at it, there will need to be a judicious use of void (but not hidden) rooms to make the scaling match~~. At least in this case it's not AS bad; just tedious since you have to do it often~~.		Eureka is recent enough to have an OK coverage on the [https://flexiblesurvival.com/mapping official map]. However as you can see from glancing at it, there will need to be a judicious use of void (but not hidden) rooms to make the scaling match.

	#map insert (directionback) void		#map insert (directionback) void

			The actual bad part comes with inserting void rooms to join spans.

			#map leave
			#map return
			(Note the room number)
			... Go around the gap
			#map dig ((direction of gap)) ((actual room number))
			#map insert ((direction of gap)) void
			(Note the *void*room number)
			((direction of gap; this moves you to the side that's missing a - (has a space instead) ))
			#map dig ((Direction towards that new voidroom)) ((voidroom number))

	===Off the Map===		===Off the Map===

Ketsueki: Eureka and #map insert Direction void

2020-05-11T07:59:02Z

Eureka and #map insert Direction void

← Older revision		Revision as of 07:59, 11 May 2020
Line 234:		Line 234:
	...		...
	#map goto VNUMBACK (that VNUM of where you actually are on the MUCK / MUD)		#map goto VNUMBACK (that VNUM of where you actually are on the MUCK / MUD)

			===Eureka===

			Eureka is recent enough to have an OK coverage on the [https://flexiblesurvival.com/mapping official map]. However as you can see from glancing at it, there will need to be a judicious use of void (but not hidden) rooms to make the scaling match. At least in this case it's not AS bad; just tedious since you have to do it often.

			#map insert (directionback) void

	===Off the Map===		===Off the Map===

Ketsueki: Mapping instructions

2020-05-03T01:24:27Z

Mapping instructions

Show changes

Ketsueki: Also mention the OpenWeatherMap key

2020-05-01T09:32:02Z

Also mention the OpenWeatherMap key

← Older revision		Revision as of 09:32, 1 May 2020
Line 94:		Line 94:
	}		}
	}		}

			If you want near-realtime weather, please sign up for [https://home.openweathermap.org/users/sign_up An OpenWeatherMap account] and make sure you retain and fill out the '''api_key''' with your account key. (NOT a login/password, but an account token that looks a bit like HEX00341AFEAAA0358 but longer, and probably actually all hex.)

	If you're using WSL this gets more complicated. "/mnt/c/Users/WindowsAccountName/My Documents/Flexible Survival Logs" might work for most. If it doesn't, talk to whomever maintains the PC. Tab-completion is really helpful here... mkdir /mnt/c/User (TAB) and then hit tab a couple more times to get a good guess at user account and My Documents locations to start in.		If you're using WSL this gets more complicated. "/mnt/c/Users/WindowsAccountName/My Documents/Flexible Survival Logs" might work for most. If it doesn't, talk to whomever maintains the PC. Tab-completion is really helpful here... mkdir /mnt/c/User (TAB) and then hit tab a couple more times to get a good guess at user account and My Documents locations to start in.

Ketsueki: Missed a set of extra []

2020-05-01T09:24:39Z

Missed a set of extra []

← Older revision		Revision as of 09:24, 1 May 2020
Line 122:		Line 122:
	==History==		==History==

	[[https://en.wikipedia.org/wiki/TinTin%2B%2B TinTin++]] is the result of almost 30 years of development by a series of programmers. While an absolute dinosaur of a computer from the era of it's origin in the mid 1990s probably couldn't run it today, just about anything from the last 20 years probably can.		[https://en.wikipedia.org/wiki/TinTin%2B%2B TinTin++] is the result of almost 30 years of development by a series of programmers. While an absolute dinosaur of a computer from the era of it's origin in the mid 1990s probably couldn't run it today, just about anything from the last 20 years probably can.

	Several older versions of this wiki page exist (updated during 2013 and 2015) with the final version of that series updated on [https://wiki.flexiblesurvival.com/index.php?title=Tintin&oldid=310992 2015-08-25T14:09:09] you might find Anden's examples useful if interested in battle tactics, though they're written assuming python2 (which is no longer supported); while Inutt's code repository uses some perl5 helpers that could be replaced or omitted entirely without breaking the basic multipane functionality. (They help produce the formatted status window and optionally near realtime weather.)		Several older versions of this wiki page exist (updated during 2013 and 2015) with the final version of that series updated on [https://wiki.flexiblesurvival.com/index.php?title=Tintin&oldid=310992 2015-08-25T14:09:09] you might find Anden's examples useful if interested in battle tactics, though they're written assuming python2 (which is no longer supported); while Inutt's code repository uses some perl5 helpers that could be replaced or omitted entirely without breaking the basic multipane functionality. (They help produce the formatted status window and optionally near realtime weather.)

	Inutt, one of the coding wizards for FS, has a nice setup for TinTin that's published on their [https://gitlab.com/inutt/flexible-survival-ui GitLab] page. Ketsueki made some small contributions (currently a pull request) to make it more suitable for users with different terminal sizes. Though it does expect a computer screen capable of displaying at least 120 columns of characters across (in that case a split of about 29 for the map and status area, and thus 90 or so for the main text area is recommended). If you're on a 1080p+ monitor, using a normal Graphical User Interface (E.G. Windows, OS X, anything else that runs a web browser) and using a full-screen "terminal" program of any sort (find one you like for your OS) you probably do have that many columns.		Inutt, one of the coding wizards for FS, has a nice setup for TinTin that's published on their [https://gitlab.com/inutt/flexible-survival-ui GitLab] page. Ketsueki made some small contributions (currently a pull request) to make it more suitable for users with different terminal sizes. Though it does expect a computer screen capable of displaying at least 120 columns of characters across (in that case a split of about 29 for the map and status area, and thus 90 or so for the main text area is recommended). If you're on a 1080p+ monitor, using a normal Graphical User Interface (E.G. Windows, OS X, anything else that runs a web browser) and using a full-screen "terminal" program of any sort (find one you like for your OS) you probably do have that many columns.

Ketsueki: Describe how to Install, Update, and Use Inutt's tested and updated TinTin++ within Tmux

2020-05-01T09:21:11Z

Describe how to Install, Update, and Use Inutt's tested and updated TinTin++ within Tmux

Show changes

Anden at 21:09, 25 August 2015

2015-08-25T21:09:09Z

← Older revision		Revision as of 21:09, 25 August 2015
Line 983:		Line 983:

	config script:<br>		config script:<br>
	</pre>		<pre>
	#! /usr/bin/env python		#! /usr/bin/env python
	global __DBNAME__		global __DBNAME__

Anden at 21:06, 25 August 2015

2015-08-25T21:06:57Z

← Older revision		Revision as of 21:06, 25 August 2015
Line 114:		Line 114:
	#send ooc Skade !daily %5		#send ooc Skade !daily %5
	}		}
	~~#alias {^dailys %5} {#send ooc Anwen !daily %5; #send ooc Hope !daily %5; #send ooc Aluthal !mission %5; #send ooc Skade !daily %5}~~

	#alias {^pets} {use bump;use grind;use Totemic deer}		#alias {^pets} {use bump;use grind;use Totemic deer}

Anden at 21:06, 25 August 2015

2015-08-25T21:06:01Z

Show changes

Anden at 19:45, 8 March 2013

2013-03-08T19:45:52Z

← Older revision		Revision as of 19:45, 8 March 2013
Line 119:		Line 119:

	You can see the kind of arrangement I use here: [http://tinypic.com/view.php?pic=smsmcj&s=6]		You can see the kind of arrangement I use here: [http://tinypic.com/view.php?pic=smsmcj&s=6]


			Simple botmode triggers:
			<pre>
			#act {^<Botmode> Your bot mode is now enabled} {#var boton 1}
			#act {^<Botmode> Your bot mode is now disabled} {#var boton 0}

			#act {<InGame> The fight is over %5} {#if {"$boton" == "1"} {search web}}
			#act {<InGame> You ran into a puzzle} {#if {"$boton" == "1"} {search web}}
			#act {<InGame> Your battle ended unexpectedly!} {#if {"$boton" == "1"} {search web}}
			#act {<InGame> The fight is over and you lost!} {#if {"$boton" == "1"} {search web}}
			</pre>