updated version number

Artifacts/displacement.lua

@@ -15,9 +15,10 @@ gm.post_script_hook(gm.constants.stage_roll_next, function(self, other, result,
 	if not displacement.active then return end
 
 	validEnvs:clear()
-	for i = 1, 5 do -- go through 5 tiers of stages, we exclude tier 6 because we dont want to randomly go to risk of rain
+	for i = 1, 4 do -- go through 4 tiers of stages, we exclude tier 6 because we dont want to randomly go to risk of rain, and we exclude tier 5 stages because artifact of tempus can easily be cheesed if temple of the elders is chosen as one of the first stages (it also breaks the onstep code of the artifact's object for some reason? no clue why)
 		local envs = List.wrap(gm._mod_stage_get_pool_list(i)) -- get all environments in a tier
 		for _, env in ipairs(envs) do
+			print(Stage.wrap(env).identifier)
 			validEnvs:add(env) -- add each environment to validEnvs
 		end
 	end
@@ -28,7 +29,7 @@ gm.post_script_hook(gm.constants.stage_roll_next, function(self, other, result,
 	if args[1].value == 1 then -- if the upcoming stage is tier 1 >>
 		potentialEnvs:clear() -- >> clear the list of potential environments
 		-- >> restore the list to include all environments again
-		for i = 1, 5 do
+		for i = 1, 4 do
 			local envs = List.wrap(gm._mod_stage_get_pool_list(i))
 			for _, env in ipairs(envs) do
 				potentialEnvs:add(env)

Equipments/midas.lua

@@ -35,6 +35,6 @@ midas:onUse(function(actor, embryo)
 		if embryo then
 			reward = reward * 2
 		end
-		hud:add_gold_gml_Object_oHUD_Create_0(reward)
+		hud.gold = hud.gold + reward
 	end
 end)

Items/crypticSource.lua

@@ -1,4 +1,4 @@
-local sprite = Resources.sprite_load(NAMESPACE, "CrypticSource", path.combine(PATH, "Sprites/Items/crypticSource.png"), 1, 16, 16)
+local sprite = Resources.sprite_load(NAMESPACE, "CrypticSource", path.combine(PATH, "Sprites/Items/crypticSource.png"), 1, 18, 18)
 
 local crypticSource = Item.new(NAMESPACE, "crypticSource")
 crypticSource:set_sprite(sprite)

Items/watchMetronome.lua

@@ -1,4 +1,4 @@
-local sprite = Resources.sprite_load(NAMESPACE, "WatchMetronome", path.combine(PATH, "Sprites/Items/watchMetronome.png"), 1, 15, 12)
+local sprite = Resources.sprite_load(NAMESPACE, "WatchMetronome", path.combine(PATH, "Sprites/Items/watchMetronome.png"), 1, 17, 15)
 local bar_sprite = Resources.sprite_load(NAMESPACE, "MetronomeBar2", path.combine(PATH, "Sprites/Items/Effects/metronomeBar.png"), 1, 26, 5)
 --local bar_sprite_big = Resources.sprite_load(NAMESPACE, "MetronomeBarBig", path.combine(PATH, "Sprites/Items/Effects/metronomeBarBig.png"), 1, 2, 8)
 

Language/english.json

@@ -9,7 +9,7 @@
 			"nameUpper" : "EXECUTIONER",
 			"description" : "The <y>Executioner</c> is a mobile fighter who specializes in counting heads. Using Ion projectors, the Executioner fabricates illusions which cause foes to run away in fear, while also projecting an axe to take out the strongest enemies. Make sure to chain kills with <y>Ion Burst</c> and <y>Execution</c> to keep the damage pouring.",
 			"endQuote" : "..and so he left, bloodlust unfulfilled.",
-			"story": "<ul>Passenger Details:</c>\n<y>[Military Class]</c>\n\n<ul>Luggage and Equipment:</c>\nOfficer boarded with EXN Acting Officer carbonweave uniform, civilian-grade plated oversuit and an issued service pistol. At military checkpoint, passenger's armament was noted to have an additional under-barrel \nmodification- and was cleared after an agreement was made to store it in a secure container. The passenger also cleared one ION 204X series battery customized with propulsion orifices. As a safety measure, passenger's \ntechnological goods were temporarily fitted with electrical auto-nullifiers and returned to them.\n\n<b>[SECURITY RECALL]</c>\n\n<ul>[Note E1a]</c> Several reports of Passenger making entire security checkpoint crew uneasy. Light surveillance will be required until further notice.\n<ul>[Note E1b]</c> Passenger would often reply in sounds rather than speech before opting to use Universal Sign Language.\n<ul>[Event E1]</c> Contracted commando performs security check in Passenger's quarters.\n<ul>[Event E1a]</c> Contracted commando requests 24 hour private surveillance in hall leading to Passenger's quarters.\n<ul>[Event E2]</c> Passenger asked to move tables during mealtime after another Passenger sent a formal complaint to onboard security.",
+			"story": "<ul>Passenger Details:</c>\n<y>[Military Class]</c>\n\n<ul>Luggage and Equipment:</c>\nOfficer boarded with EXN Acting Officer carbonweave uniform, civilian-grade plated oversuit and an issued service pistol. At military checkpoint, passenger's armament was noted to have an additional under-barrel \nmodification- and was cleared after an agreement was made to store it in a secure container. The passenger also cleared one ION 204X series battery customized with propulsion orifices. As a safety measure, passenger's \ntechnological goods were temporarily fitted with electrical auto-nullifiers and returned to them.\n\n<b>[SECURITY RECALL]</c>\n<ul>[Note E1a]</c> Several reports of Passenger making entire security checkpoint crew uneasy. Light surveillance will be required until further notice.\n<ul>[Note E1b]</c> Passenger would often reply in sounds rather than speech before opting to use Universal Sign Language.\n<ul>[Event E1]</c> Contracted commando performs security check in Passenger's quarters.\n<ul>[Event E1a]</c> Contracted commando requests 24 hour private surveillance in hall leading to Passenger's quarters.\n<ul>[Event E2]</c> Passenger asked to move tables during mealtime after another Passenger sent a formal complaint to onboard security.",
 			"id" : "Travel ID: 4383354378334FF3D34D",
 			"departure" : "<y>Departure:</c>\nOld Alcatraz,\nRustborough,\nMars",
 			"arrival" : "<y>Destination:</c>\nStillwater Bay,\nNewdredge,\nEuropa"
@@ -19,10 +19,7 @@
 			"nameUpper" : "MULE",
 			"description" : "EVERY <y>MULE</c> UNIT IS ADEQUATELY EQUIPPED AND READY FOR DUTY. BUILT WITH HIGH QUALITY MATERIALS FOR MAXIMUM WORK PERFORMANCE. THIS MODEL INCLUDES THE <y>FORAGER SET OF TOOLS</c>, PERFECT FOR <y>HUNTING</c>, <y>EXPLORATION</c> AND OTHER DANGEROUS TASKS FOR THE COMMON USER. IN ORDER TO INITIALIZE PLEASE STATE A DIRECTIVE ON SYSTEM BOOT.",
 			"endQuote" : "..and so it left, pistons creaking, directive unstated.",
-			"story": "PSA: The MULE units are neither sentient nor pets. Calling them 'Molly' will not impact the MULE unit's programming.",
-			"id" : "",
-			"departure" : "",
-			"arrival" : ""
+			"story": "<ul>Warrantee Expiration: \n8/16/2041 \n\nInputted Note: \n(ID: #1244C4F4F5D494)</c> \nNOTICE: MULE - MODEL F \nI'd rather not get into hot water for “tampering with ship property”, but I recently booted up this MULE unit and took 'em for repairs. It was just lying there, so I took it that no one would really mind if I touched it up a little. Heard talks of personnel wanting to throw 'em away before takeoff, but I just couldn't let it happen to such fine craftmanship.. it's a sight for sore eyes, sure, but you've gotta admit, it's novelty! Multi-purpose units haven't been considered in a long time since the first quadruped model was a hit. Besides, we all know what these sorts of bots can get up to! With a chassis like this, I wouldn't doubt that this big guy's roughed some pretty gnarly terrain. It's a bit of a walking time capsule, wouldn't you say? \nAll needed footage attached below yadda yadda— Look, I'll level with ya. Just.. consider keepin' it around. Even for just a bit. Whether those rumors are true or not.. I think his owner would be happy, y'know.. knowing it's up 'n runnin' still. \nJust give 'em something to do. Give it one more chance. \n\n<b>[MAINTENANCE REPORT]</c> \n<ul>[Report M1]</c> On boot-up, MULE unit remained completely motionless until around 20 minutes later when given a verbal command to deploy its support drone. MULE unit demonstrated idle processing and protocols only after the command. \n<ul>[Report M1a]</c> Support drone's power bank was found to be degraded. No compatible replacements could be found, leaving it to only be recharged. Battery longevity not guaranteed. \n<ul>[Report M2]</c> MULE unit was to be familiarized with Contact Light passengers and staff via facial recognition after suddenly attempting to constrain a mechanic it failed to recognize. Most UES personnel are now logged in its memory. \n<ul>[Report M2a]</c> Remotely accessing MULE unit's memory reveals previous entries in its database dating back to 2036. Initial entries in its memory were found to be corrupted or expunged."
 		},
 		"nemesisCommando" : {
 			"name" : "Nemesis Commando",
@@ -43,7 +40,7 @@
 			"nameUpper": "TECHNICIAN",
 			"description": "The <y>Technician</c> is excellent at setting up and maintaining zones of enemy denial. <y>Forced Shutdown</c> can <y>forcibly lock down an area</c> when upgraded. <y>Upgrading</c> gadgets improves their effectiveness, but be careful when doing so in dangerous situations!",
 			"endQuote": "..and so he left, by switching the ship off and on again.",
-			"story": "<ul>Passenger Details:\n<g>[Employee Class]\n\n<ul>Employee Details:</c>\nEmployee contracted to work on-site for the full duration of the scheduled voyage of the UES Contact Light, to perform maintenance on machinery should technical issues arise aboard the ship. Employee qualified with 6 years of hands-on experience in software and hardware engineering.\n\n<ul>Luggage & Equipment:</c>\nEmployee boarded with a Durarend welding spacesuit rated with strong vacuum resistance, and additionally leather and cloth attire made for planetary wear. Employee notified that clothes may tear in the case of a vacuum event. Security flagged the sizable wrench they held for appearing impractical for use while potentially dangerous. Upon questioning, the employee indicated that it was \"custom-built ... for the toughest jobs.\" Following procedure, the wrench was moved to an automated lockbox in loading bay 1a. Remaining inspection of carry-ons revealed several standard-issue wrenches, 3 color-coded USBs, a 2047 model GeForm Laptop, tool boxes, and a welding tool. USBs were inspected on company-owned QPuting Disposable Computer installed with ReoVirus Detector v1.6.2. No traces of malware were detected and stored files are UPG format containing blueprints of various devices. Employee permitted to pass with no further difficulties.\n\n<b>[SECURITY RECALL]</c>\n<ul>[Event T1]</c> Employee forcibly removed from cabin during liftoff preparations when refusing to leave after conversating with ship pilot for multiple hours.\n<ul>[Event T2]</c> Employee observed stealing sodas from a vending machine.\n<ul>[Event T3]</c> Automated lockdown originating in loading bay 4a resolved by employee.\n<ul>[Event T4]</c> Escape pod B-08 status shifted from ERROR to ALERT after the employee was requested by ship personnel to troubleshoot. Security personnel instructed to investigate.\n<ul>[Event T1a] Employee additionally reported to have tampered with cabin control panel to make it \"easier to cruise.\" Scheduled launch delayed and employee instructed to revert any modifications made.",
+			"story": "<ul>Passenger Details:\n<g>[Employee Class]\n\n<ul>Employee Details:</c>\nEmployee contracted to work on-site for the full duration of the scheduled voyage of the UES Contact Light, to perform maintenance on machinery should technical issues arise aboard the ship. Employee qualified with 6 years of hands-on experience in software and hardware engineering.\n\n<ul>Luggage & Equipment:</c>\nEmployee boarded with a Durarend welding spacesuit rated with strong vacuum resistance, and additionally leather and cloth attire made for planetary wear. Employee notified that clothes may tear in the case of a vacuum event. Security flagged the sizable wrench they held for appearing impractical for use while potentially dangerous. Upon questioning, the employee indicated that it was \"custom-built ... for the toughest jobs.\" Following procedure, the wrench was moved to an automated lockbox in loading bay 1a. Remaining inspection of carry-ons revealed several standard-issue wrenches, 3 color-coded USBs, a 2047 model GeForm Laptop, tool boxes, and a welding tool. USBs were inspected on company-owned QPuting Disposable Computer installed with ReoVirus Detector v1.6.2. No traces of malware were detected and stored files are UPG format containing blueprints of various devices. Employee permitted to pass with no further difficulties.\n\n<b>[SECURITY RECALL]</c>\n<ul>[Event T1]</c> Employee forcibly removed from cabin during liftoff preparations when refusing to leave after conversating with ship pilot for multiple hours.\n<ul>[Event T2]</c> Employee observed stealing sodas from a vending machine.\n<ul>[Event T3]</c> Automated lockdown originating in loading bay 4a resolved by employee.\n<ul>[Event T4]</c> Escape pod B-08 status shifted from ERROR to ALERT after the employee was requested by ship personnel to troubleshoot. Security personnel instructed to investigate.\n<ul>[Event T1a]</c> Employee additionally reported to have tampered with cabin control panel to make it \"easier to cruise.\" Scheduled launch delayed and employee instructed to revert any modifications made.",
 			"id" : "Travel ID: 54E4F4C434F59474E454",
 			"departure" : "<y>Departure:</c>\nUES Shipping Dock 5,\nRedview,\nMars",
 			"arrival" : "<y>Destination:</c>\nUES Shipping Dock 0,\nRedview,\nMars"