One Hundred Seconds Weapons - Revision history

HOST-GSKEBECHET: Updating per Gswiki:Style guide/Item scripts, fixing all broken formatting, removed section that appears to be a tutorial on how to use a lich script/command. Lich-focused articles must be separate articles and adhere to Gswiki:Policy.

2025-07-15T15:26:39Z

Updating per Gswiki:Style guide/Item scripts, fixing all broken formatting, removed section that appears to be a tutorial on how to use a lich script/command. Lich-focused articles must be separate articles and adhere to Gswiki:Policy.

Show changes

HOST-GSFAMINE: /* Properties */

2025-02-26T18:33:47Z

Properties

← Older revision		Revision as of 13:33, 26 February 2025
Line 34:		Line 34:
	Due to the nature of the script, it takes up both the script and the flare/defender item property slots, as well as the material slot. According to Wyrom the weapon will check that it is made of air each time it is used.		Due to the nature of the script, it takes up both the script and the flare/defender item property slots, as well as the material slot. According to Wyrom the weapon will check that it is made of air each time it is used.

	Once every 24 hours, the wielder can set the enchant and flare. Flares are fire, ice, electric, impact, acid, vacuum, plasma, steam, disintegration, and disruption. Enchant is between +1 to +100. All are determined by {{boldmono\|TIME}}, in Unix. The base enchant is +1, and when it resets it returns to +1. Effects last until 8am the next day.		Once every 24 hours, the wielder can set the enchant and flare. Flares are fire, ice, electric, impact, acid, vacuum, plasma, steam, disintegration, and disruption. Enchant is between +1 to +100. All are determined by {{boldmono\|TIME}}, in Unix. The base enchant is +1, and when it resets it returns to +1. Effects last until 8am the next day, however the weapon must be used before it will revert.

	Some other properties can be added to it as with normal weapons, including ensorcell, bless, creaturebane, weighting, etc. It cannot be enchanted, have ability flares added or changed, or be altered or lightened.		Some other properties can be added to it as with normal weapons, including ensorcell, bless, creaturebane, weighting, etc. It cannot be enchanted, have ability flares added or changed, or be altered or lightened.
Line 107:		Line 107:
	3rd person: A dark shadow quickly slithers from the hilt of [ATTACKER's] [ITEM] along the surface in a serpentine fashion. Upon reaching the tip, it abruptly snaps towards [TARGET] in a streak of cold darkness.		3rd person: A dark shadow quickly slithers from the hilt of [ATTACKER's] [ITEM] along the surface in a serpentine fashion. Upon reaching the tip, it abruptly snaps towards [TARGET] in a streak of cold darkness.
	Target: A dark shadow quickly slithers from the hilt of [ATTACKER's] [ITEM] along the surface in a serpentine fashion. Upon reaching the tip, it abruptly snaps towards you in a streak of cold darkness.		Target: A dark shadow quickly slithers from the hilt of [ATTACKER's] [ITEM] along the surface in a serpentine fashion. Upon reaching the tip, it abruptly snaps towards you in a streak of cold darkness.
	</pre>

	==Loresong==		==Loresong==
Line 123:		Line 122:
	It has some unknown (scripted) benefit.		It has some unknown (scripted) benefit.
	It has a permanently unlocked loresong by BardyMcBardBard.		It has a permanently unlocked loresong by BardyMcBardBard.

	</pre>

JUMBODOG: /* Steps to Sync */

2025-01-25T13:55:50Z

Steps to Sync

← Older revision		Revision as of 08:55, 25 January 2025
Line 167:		Line 167:
	3. ''Use the Base Script''		3. ''Use the Base Script''

	The following script will loop until the Unix timestamp matches the desired condition (e.g., ending in '''~~666~~'''):		The following script will loop until the Unix timestamp matches the desired condition (e.g., ending in '''00''' for a bonus of +100):
	<syntaxhighlight lang="ruby">		<syntaxhighlight lang="ruby">
	;e until Time.now.to_i % 100 == 99 do sleep 0 end; fput "clench my sword"; echo Time.now.to_i		;e until Time.now.to_i % 100 == 0 do sleep 0 end; fput "clench my sword"; echo Time.now.to_i
	</syntaxhighlight>		</syntaxhighlight>
	That will work if you're perfectly in sync or just a little bit ahead. However lets look at a couple of common examples:		That will work if you're perfectly in sync or just a little bit ahead. However lets look at a couple of common examples:

JUMBODOG: /* Steps to Sync */

2025-01-25T13:54:56Z

Steps to Sync

← Older revision		Revision as of 08:54, 25 January 2025
Line 169:		Line 169:
	The following script will loop until the Unix timestamp matches the desired condition (e.g., ending in '''666'''):		The following script will loop until the Unix timestamp matches the desired condition (e.g., ending in '''666'''):
	<syntaxhighlight lang="ruby">		<syntaxhighlight lang="ruby">
	;e until Time.now.to_i % ~~1000~~ == ~~666~~ do sleep 0 end; fput "clench my sword"; echo Time.now.to_i		;e until Time.now.to_i % 100 == 99 do sleep 0 end; fput "clench my sword"; echo Time.now.to_i
	</syntaxhighlight>		</syntaxhighlight>
	That will work if you're perfectly in sync or just a little bit ahead. However lets look at a couple of common examples:		That will work if you're perfectly in sync or just a little bit ahead. However lets look at a couple of common examples:

	====Ahead by .7====		====Ahead by .7====
	"If I'm ahead, when my clock is at ~~666~~, then its actually only ~~665~~. So I need to sleep for an amount slightly more than my delay." To keep things simple, its probably okay to sleep for a full second here, which will account for any inaccuracies as well. If you find that your system clock is moving around a lot of is inaccurate you'll probably want to do a full second to offset it.		"If I'm ahead, when my clock is at 100, then its actually only 99. So I need to sleep for an amount slightly more than my delay." To keep things simple, its probably okay to sleep for a full second here, which will account for any inaccuracies as well. If you find that your system clock is moving around a lot of is inaccurate you'll probably want to do a full second to offset it.
	<syntaxhighlight lang="ruby">		<syntaxhighlight lang="ruby">
	;e until Time.now.to_i % ~~1000~~ == ~~666~~ do sleep 1 end; fput "clench my sword"; echo Time.now.to_i		;e until Time.now.to_i % 100 == 0 do sleep 1 end; fput "clench my sword"; echo Time.now.to_i
	</syntaxhighlight>		</syntaxhighlight>


	====Behind by .3====		====Behind by .3====
	"If I'm behind, when my clock is at ~~666~~, then its already ~~only 667~~. So I need to take action before I hit my desired value." In this case we would adjust the above by subtracting an amount from our total. Because we have a whole second, its simplest to just go down by the full second, and clench when the local timer hits 1 prior to the desired value:		"If I'm behind, when my clock is at 99, then its already 100. So I need to take action before I hit my desired value." In this case we would adjust the above by subtracting an amount from our total. Because we have a whole second, its simplest to just go down by the full second, and clench when the local timer hits 1 prior to the desired value:
	<syntaxhighlight lang="ruby">		<syntaxhighlight lang="ruby">
	;e until Time.now.to_i % ~~1000~~ == ~~665~~ do sleep 0 end; fput "clench my sword"; echo Time.now.to_i		;e until Time.now.to_i % 100 == 99 do sleep 0 end; fput "clench my sword"; echo Time.now.to_i
	</syntaxhighlight>		</syntaxhighlight>

	====Behind by more than 1 full second====		====Behind by more than 1 full second====
	The short answer is "always round up" If you're behind by 1.3 seconds, then you would do % ~~1000~~ == ~~664~~. If you're ahead by 1.5 seconds then change the sleep value to 2.		The short answer is "always round up" If you're behind by 1.3 seconds, then you would do % 100 == 98. If you're ahead by 1.5 seconds then change the sleep value to 2.

JUMBODOG: /* Special Flare Types */

2025-01-25T13:53:14Z

Special Flare Types

← Older revision		Revision as of 08:53, 25 January 2025
Line 95:		Line 95:

	=== Special Flare Types ===		=== Special Flare Types ===
			Special flare types exist, and are considered easter eggs and not widely known. Good luck!
	These special flares are when the trailing digits are equal to this pattern. For example: 1682485666 or 1682666666
	{\| class="wikitable"
	\|+ Special Flare Types
	! Code !! Flare Type !! Description
	\|-
	\| 666 \|\| '''Death''' \|\| +66 enchant with death flares
	\|-
	\| 666666 \|\| '''Death''' \|\| +100 enchant with death flares. Lasts for 48 hours.
	\|}

	Due to the nature of time not syncing properly globally it is possible that a character with a temporal weapon may try to activate it to an enchant higher than that character can hold. If this occurs, the enchant of the item will recall as higher than what the character can hold, however the effective enchant (what is actually applied) will be capped at `<character level> x 2`. Please be cautious as this could cause complications in the event that the character gets disarmed.


	==Analyze==		==Analyze==

JUMBODOG at 13:45, 25 January 2025

2025-01-25T13:45:08Z

← Older revision		Revision as of 08:45, 25 January 2025
Line 160:		Line 160:
	\|<!-- Third Person View -->		\|<!-- Third Person View -->
	\|}		\|}

			== Using the Atomic Clock to Sync Actions ==

			Synchronizing actions with precise timing can improve gameplay by ensuring timing-dependent mechanics are executed accurately. Using [time.is](https://time.is/), you can determine your clock's offset and adjust your script accordingly.

			=== Steps to Sync ===

			1. ''Check Your Clock Offset''
			Visit [time.is](https://time.is/) to determine how far ahead or behind your system clock is compared to the official atomic time. Note the offset (e.g., '''0.8 seconds behind''' or '''0.7 seconds ahead''').

			2. ''Figure out how long you need to wait in what direction''
			Think of it as:
			If I'm behind, when my clock thinks it's 99, it's already 100. Which means I need to clench before I hit 100.
			If I'm ahead... when my clock is at 100, it's actually only 99.... so i need to sleep for 1 second, then clench.


			3. ''Use the Base Script''

			The following script will loop until the Unix timestamp matches the desired condition (e.g., ending in '''666'''):
			<syntaxhighlight lang="ruby">
			;e until Time.now.to_i % 1000 == 666 do sleep 0 end; fput "clench my sword"; echo Time.now.to_i
			</syntaxhighlight>
			That will work if you're perfectly in sync or just a little bit ahead. However lets look at a couple of common examples:

			====Ahead by .7====
			"If I'm ahead, when my clock is at 666, then its actually only 665. So I need to sleep for an amount slightly more than my delay." To keep things simple, its probably okay to sleep for a full second here, which will account for any inaccuracies as well. If you find that your system clock is moving around a lot of is inaccurate you'll probably want to do a full second to offset it.
			<syntaxhighlight lang="ruby">
			;e until Time.now.to_i % 1000 == 666 do sleep 1 end; fput "clench my sword"; echo Time.now.to_i
			</syntaxhighlight>


			====Behind by .3====
			"If I'm behind, when my clock is at 666, then its already only 667. So I need to take action before I hit my desired value." In this case we would adjust the above by subtracting an amount from our total. Because we have a whole second, its simplest to just go down by the full second, and clench when the local timer hits 1 prior to the desired value:
			<syntaxhighlight lang="ruby">
			;e until Time.now.to_i % 1000 == 665 do sleep 0 end; fput "clench my sword"; echo Time.now.to_i
			</syntaxhighlight>

			====Behind by more than 1 full second====
			The short answer is "always round up" If you're behind by 1.3 seconds, then you would do % 1000 == 664. If you're ahead by 1.5 seconds then change the sleep value to 2.

JUMBODOG: /* Example */

2025-01-25T11:29:57Z

Example

← Older revision		Revision as of 06:29, 25 January 2025
Line 58:		Line 58:
	- '''YY''' = Enchant <br/>		- '''YY''' = Enchant <br/>

	Concrete Example:		Concrete Example:<br/>
	- '''Timestamp:''' 1682485299		- '''Timestamp:''' 1682485299<br/>
	- '''Flare:''' Ice		- '''Flare:''' Ice<br/>
	- '''Enchant Level:''' +99		- '''Enchant Level:''' +99<br/>
	- '''Description:''' A temporal warpike encased in ice with +99 enchant.		- '''Description:''' A temporal warpike encased in ice with +99 enchant.<br/>

	---		---

JUMBODOG: /* Example */

2025-01-25T11:29:37Z

Example

← Older revision		Revision as of 06:29, 25 January 2025
Line 54:		Line 54:

	=== Example ===		=== Example ===
	Given the Unix timestamp: '''1682485XYY'''		Given the Unix timestamp: '''1682485XYY''' <br/>
	- '''X''' = Flare Type		- '''X''' = Flare Type <br/>
	- '''YY''' = Enchant		- '''YY''' = Enchant <br/>

	Concrete Example:		Concrete Example:

JUMBODOG at 11:28, 25 January 2025

2025-01-25T11:28:30Z

← Older revision		Revision as of 06:28, 25 January 2025
Line 105:		Line 105:
	\|}		\|}

			Due to the nature of time not syncing properly globally it is possible that a character with a temporal weapon may try to activate it to an enchant higher than that character can hold. If this occurs, the enchant of the item will recall as higher than what the character can hold, however the effective enchant (what is actually applied) will be capped at `<character level> x 2`. Please be cautious as this could cause complications in the event that the character gets disarmed.

JUMBODOG at 11:25, 25 January 2025

2025-01-25T11:25:27Z

Show changes