Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/30/2021 in all areas

  1. lol username

    Atlantis website items/lore

    hey remember that lego atlantis site with the items you could find and stuff found an old screenshot and wanted to revisit it/see what the item descriptions were luckily the BMP has it archived: http://biomediaproject.com/bmp/files/LEGO/gms/download/Atlantis/ but actually getting ingame didn't seem to quite work, and a partially-complete wiki claims the remaining 10 items are part of the quest for the golden king game: https://legoatlantis.fandom.com/wiki/The_Atlantis_Adventure#The_Treasure_Chest but all most of the data is exposed in pngs/xmls so I figured I might as well make it all more accessible here RevolverTreas Billy the Squid's Gun One of the fabled guns used by Billy the Squid himself! This gun has seen its fair share of warfare and is certain to help its wielder through the tightest of undersea scuffles. But beware; there are most certainly others in search of its enchanted power! WheelTreas Wheel of the Deep A ship without a wheel is like a pirate without a peg leg. Researchers speculate that it once belonged to the Flying Dutchman. Is this why the Flying Dutchman is doomed to roam the ocean waters for eternity? HookTreas Captain Hook's Hook As the right hand of one of the most despicable pirates to have ever sailed the seven seas, Captain Hook’s hook saw a lot of destruction and havoc in its life. At the time of the Captain’s eventual death, so feared was his legacy that his crew declared the hook cursed and sank it to the bottom of the ocean. RingTreas Poseidon's Ring Poseidon himself wore this ring during his rule of Atlantis. Made from blinding diamonds and pure gold, this piece of jewelry had fantastic powers, from controlling tidal waves to winning a fickle bride to be. MaskTreas Mask of the Ancients The ancients of Atlantis wore this all-powerful mask during major rituals. Like a seashell, it echoes the beats of the drum and the shouts of the civilization from so long ago. While it has been out of use for centuries, it still radiates the power it used to hold. WrenchTreas Trench Wrench Lost in the deep ocean trenches of the sea, this wrench once played an integral role in the industrial revolution of Atlantis. It was used to build everything from their famed seahorse chariots to H2O-tanks for exploring the lands above water. It is surely a very useful tool to have on hand! IdolTreas King Midas Jr. Gold Micro Fig Even the crushing depths of the ocean are incapable of suppressing the beauty and lure held by the legendary Golden mini-fig of King Midas Jr. Countless ships intent upon capturing the opulent statue found their ultimate doom amongst the treacherous waves that protect its watery burial ground. EvilskullTreas Evil Skull There's something not quite right with this skull. It might be the mischievous smirk, its puckered brows or the depths of its glowing red eyes. Perhaps it's hiding knowledge of the treasures of Atlantis or readying a terrible curse. Either way, it seems best not to mess with it. HelmetTreas Lost Diver’s Helmet An explorer must have lost this helmet during a struggle with one of the guardians of Atlantis. Though dented, rusted, and dirty, the helmet should serve as a relic of bravery…and as a warning to those who seek out the treasures of Atlantis. TridentTreas Poseidon’s Trident Poseidon’s great Trident was by his side during his reign over Atlantis. He often used it to rule with an iron, albeit watery, fist; as well as to pick fish out from between his teeth. Perhaps this versatility is one of the reasons Poseidon’s Trident is so sought-after. CrablegTreas Temple Crab Leg This missing appendage seems to be a relic left behind from one of the Atlantis temple's sentinel crabs. Although it's covered with seaweed and been battered by the ocean water, its pointed claw can still impale the thickest of steel or make the tastiest of meals. WandTreas Sea Witch's Wand While nobody knows if this wand was used to cast spells on humans or grant wishes to mermaids, it still sparkles likes its brand new. Magic is definitely hidden within its star-shaped tip, but only a real Sea Witch can to activate it. ScepterTreas Mermaid Scepter Since the mysterious disappearance of the Mythic Merpeople, many have sought the fabled Mermaid Scepter. Said to grant any who wield it the ability to breathe underwater, this powerful apparatus is one of the most sought after treasures of the deep! SugarskullTreas Skull of a Thousand Wishes With its mysterious grin and eyes, this gemmed skull seems to hold all the powers of the sea! If rescued from its murky grave, perhaps its bejeweled brain could help fulfill the dreams of its keeper! HarpoonbaseTreas Harpoon Though battered and dirty, this harpoon was once the mighty weapon of choice for treasure hunters trying to survive against the terrifying beasts of the deep. Its casing may be rusted, but with a little polish and elbow grease, this could once again be a wicked weapon. HarpoonhookTreas Harpoon's Hook Lost during a fierce battle between the Atlantis warriors and treasure hunters attempting to steal from the Temple of Atlantis, the harpoon hook lay hidden by rocks and seaweed on the ocean floor. Though it was heavily damaged in a chaotic fight, it would still make an excellent trophy for those sharp enough to find it. CrystalTreas Lost Power Crystal This Lost Crystal pulsates purple with power and is believed to grant its holder super-human strength. Once located in abundance along the ocean depths, scientists theorize that Atlantis warriors were sent to battle with pendants of these very crystals slung from their necks. PropellerTreas Old Explorer's Ship Propeller This propeller was attached to a fearsome pirate ship that once terrorized the seven seas! A curse cast by a sorceress to punish the crew’s dastardly deeds caused it to detach from the vessel and sink into the inky deep. TreasureTreas Treasure Island Treasure It’s every Captain’s dream to find a treasure chest full of gemeralds! Now that it has been uncovered, what will they be spent on? A pocketful of these gleaming beauties is enough to buy a magnificent ship, and the chest itself would make any sailor a splendid trophy. MessagebottleTreas Message in a Bottle It’s a container. It’s junk. It’s a secret message that somebody wants passed on! This weathered bottle must have been drifting in the open sea for an extended period of time. Isn’t it time its message is announced to the world? ok so that's the first 20 of 30, they have pngs defined outside of the main flash files the other 10 have their images inside one of the swfs, so I ripped em SwordTreas Captain’s Sword Once adorned with hundreds of gemeralds and able to cut through steel like jellyfish, this Captain’s pirate sword was lost during an epic battle between pirates and the creatures of the deep. It now lies hidden amidst the muck at the bottom of the sea. SharkTreas Shark Helmet The ancients of Atlantis wore these helmets as a disguise while hunting sharks. No one knows if these actually fooled the sharks, but they sure came in handy as protective gear while playing sea-sports. JoneslockerTreas Davy Jones' Locker The mystery of Davy Jones’ locker has haunted the sea for centuries. No sailor has come back from seeking the truth, but when explorers finally uncovered the legendary locker, any lost souls had seemingly been transformed into nothing but dirty socks and gym shorts. HornscepterTreas Shark Tooth Scepter This ancient weapon was long used by undersea warriors like the Shark Men of Atlantis. It is adorned with a razor-sharp shark tooth, and has been known to snap tridents in two. HatTreas Captain's Hat Somewhere out there a Captain is without his hat. It’s a little bit dirty and battered, but with the right solvent, it’s bound to compliment any pirate’s outfit perfectly. GobletTreas Golden Goblet Legend has it that whomever drinks out of the golden goblet gains eternal youth. Abandoned in the depths of the ocean, it's become one of the most sought after treasures of Atlantis lore. Who knows if its magic is still intact? GemeraldsTreas Gemeralds of the Sea emeralds are not only said to change colors depending on their owner’s mood, but also to reflect one’s soul. Because of this, they are the most sought after of all crystals and make excellent lie detectors for the sailor’s lucky enough to own them! (yes that seems to be a typo at the start of the description...?) EyepatchTreas Captain's Eye Patch While its appearance may be ordinary, for ages this Eye Patch has remained tangled in seaweed, absorbing the secrets of the deep. By now, the power and mystery held within its aged threads could assist in even the most difficult of quests. DiamondTreas Diamond of the Deep According to ancient maritime legend, this extraordinary jewel is not only flawless, but also the size of ninety ordinary diamonds! Keep your eyes peeled, its radiance is supposedly visible from the surface of the sea. BagTreas Old Explorer's Leather Bag Though it seems just an ordinary leather bag, this satchel belonged to one of the greatest ocean adventurers of all time. Packed full with priceless deep-sea research, what aquatic beast could have possibly forced the explorer to leave it behind? there's then what appear to be two unused treasures, FlippersTreas and LegobottleTreas, no text for them exists though:
    2 points
  2. trigger_segfault

    In-depth Look at the CFG Syntax

    Sounds good! I've actually already gotten an assembly patch working to fix this, though I've only done tests with the Masterpiece executable, (and very few tests at that)... and it's in Python (which I need to port to some more-accessible language). As long as the Improvement Pack's order is "sound1,sound1,sound2,sound2,...", then it shouldn't cause problems whether the user has the patch applied or not. And on an unrelated note... Dependencies So all dependencies have an "AlwaysCheck:" prefix in Lego.cfg, it turns out there actually is another prefix that can be used: "HitOnceStay:" - This is the only prefix the game actually checks for in the Dependencies block. This states that once the requirements are met. The player never needs to meet the requirements again. The only exception is for objects that need a place to teleport in. (i.e. Vehicles cannot be teleported if there's no power/or Power Station) Dependencies { HitOnceStay:Hoverboard Pilot:0,ToolStation:1,TeleportPad:0,PowerStation:0 AlwaysCheck:SmallDigger Pilot:0,ToolStation:1,TeleportPad:0,PowerStation:0 ; any prefix besides "HitOnceStay" can be used in-place of "AlwaysCheck" ; just make sure to include the ':' FooBarBaz12:SmallTruck Pilot:0,ToolStation:1,TeleportPad:0,PowerStation:0 } Example Using the example for HitOnceStay above, this shows that removing the LV1 ToolStation will still allow the Hover Scout to teleport in, while the Small Digger cannot.
    2 points
  3. trigger_segfault

    In-depth Look at the CFG Syntax

    I'm looking through the LegoRR.exe assembly for how exactly it reads Lego.cfg, and other cfg-like files (.ol Object Lists, .ptl Mission AI, etc.). The basic syntax already makes sense, but knowing the boundaries helps a lot with weird edge cases. There's already been some fun finds. Base CFG Syntax: Back to Extended Syntax Basics The most interesting aspect is that there seems to be almost no concept of lines. All whitespace characters (tabs, spaces, line feeds, carriage returns, and ';' comments) are treated the same, they all separate tokens (i.e. keys, values, block names, and block braces {}). There is one exception, and that is the newline character '\n', which is required to end ';' line comments. All properties (whether the beginning of a property block {}, or a property key value pair) consume exactly 2 tokens from the config file. A property block's "value" is actually the '{' character, while the '}' character is a special case that's consumed but not assigned anywhere. Because every property consumes 2 tokens, missing a property value/key/etc., or adding one too many can throw off the entire file. Double-slash `//` comments are NOT supported... yet they still appear in Lego.cfg if you search for `// ROCK FOG`. And look! This creates 3 tokens which would throw off the file... except it doesn't, because they appear in pairs every time when defining `FogColourRGB` and `HighFogColourRGB`. This essentially removes the `HighFogColourRGB` property, because the parser ends up treating it as a property value and not a key like so: { FogColourRGB = 110:110:155, // = ROCK, FOG = HighFogColourRGB, 155:155:110 = //, ROCK = FOG } Special Characters ';' - Comments, you see them everywhere. Not much more to add to this, other than the fact that these do not need to be separated by real whitespace. If a value has a ';' in it, it will immediately end (although this is never done in Lego.cfg). As an example, this would be 100% valid: `CreditsTextFile Credits.txt;comment`. '{' '}' - On the other hand, block open/close braces must be separated by whitespace, otherwise they will be considered part of the block name, property key, or property value. e.g. `BlockName{` will not count as an opening brace. A token can start with, end with, or have '{' '}' characters anywhere in the middle, as long as the token is at least 2 characters long, it will be treated like a name, and not as a block brace. '*' - The asterisk is used as a wildcard in block/property key names (at the root level only), and is used as a method for defining base information that can easily be overridden. Most notably, this is seen with the root `Lego* {}` block name. If you look at the bottom of Lego.cfg, you'll see the `LegoRR {}` block "; Settings for the final version", Rock Raiders uses the executable name (LegoRR.exe) -> `LegoRR::Block::Path::To::PropertyKey` when looking up configuration values. If you want to change the executable name, make sure the name starts with Lego, and then you can define custom config settings depending in the full name of the exe when launched. Which brings us to the next character(s): "::" - You'll see this syntax with Levels::LevelName, and Textures::Rock|Ice|Lava,. Internally, Lego Rock Raiders uses this to lookup any property or block key. It uses the same syntax as C++'s namespaces. I'm not quite sure how the usage of "::" is done with property keys, as is seen with `Stream_Objective_Levels::Level01 @Sounds\Streamed\Objectiv\MisObj01` and such, it's possible the handling for this is hardcoded. You cannot use double-quotes to include spaces in key names or values. Spaces can only be used for certain non-file-path text by inserting '_' underscore characters. Common Lego.cfg Syntaxes: Common Keywords and Literals Keywords: TRUE, FALSE, YES, NO, ON, OFF, NULL Integer: 25, -100, +32 Float: 0.1, -2.5, +1.0, 60.0f RGB: 255:0:13 (the `#.#f` float syntax is only seen with the 2 `PolyRange` properties. This is, again, a C/C++ syntax) Common Value Delimiters Very often, a single property key will require multiple points of information to fill in its value. There are 3 common characters used to separate this information, however these are only used for certain properties. Many will use multiple delimiters to signal different things. And many blocks will have comments stating how to format said property value. Delimiters: ':' ',' '|' Commen Key/Value Prefixes Three special prefix characters are seen on many property key and value names. These are as-always, used on a case-by-case basis: '@' (values) - Presumably specifies to stream a sound property value (rather than loading it in memory all at once). This prefix is also utilized in the ToolTips section to denote an image name instead of text (however this is never actually used in Lego.cfg, only commented on). '*' (values) - Seen on a handlful of Sounds\ path property values. Purpose is unknown. '!' (keys) - Seen on a handfull of SFX/SND/etc. property keys. Purpose isn't fully understood, but it seems this is used to denote that a property is an "expensive" resource, that can be ignored/excluded when using an appropriate `-reduceX` command line argument. Format Characters (sprintf) A few property values have dynamic information that needs to be replaced at runtime. These property values expect special "%_" format character patterns. More than anything else, messing up these property values can and will crash the game (immediately upon usage). This is because a program will pass in N values to replace N format characters, any difference in number will imbalance the program's execution stack, and immediately start causing all kinds of unexpected behavior until a crash is inevitable. See the printf reference for all existing format characters, however "%d" and "%%" are only ever seen in Lego.cfg. You can change up and replace "%d" with a different format specifier in-some-cases, but beware that it's a bit more complicated than just keeping the same number of format specifiers. "%%" - An escape to insert in a real '%' percent sign. This does not consume one of those N values passed by the program, it is simply the only way to specify a percent sign without causing formatting to occur. "%d" - Insert a signed integer (whole number that can be negative or positive). All Format Usages: Making Use of this Information: Syntax Highlighting for VSCode (WIP) This syntax highlighting is based on information that was only known before going into the assembly, a lot of the edge cases listed above aren't added in yet, but your average cfg file should be as readable as ever. The extension development is available on GitHub, (along with the rest of this research). It's not in any finished state, or on the VSCode Marketplace, but it can be installed by dropping the containing folder, vscode-lrr, into `C:\Users\<YOU>\.vscode\extensions\`. Fixing the ROCK FOG Comments Comparison of changing `HighFogColourRGB` to `255:0:0` without removing the `// ROCK FOG` comments, and with removing them: Changing the "LegoRR" Root Block Name As explained in the section describing '*' block name wildcard characters, the root namespace at the bottom of Lego.cfg is looked up based on the name of the game executable. When put into practice, here's an example of 3 game variations added to a single Lego.cfg file (ignore the fact that I created duplicate WAD files to match the exe names). The following executable-name-specific properties are defined: LegoRR::Main::PowerCrystalRGB 255:000:000 ; RED Energy Crystals for "LegoRR.exe" LegoSL::Main::PowerCrystalRGB 000:255:255 ; CYAN Energy Crystals for "LegoSL.exe" LegoSS::Main::PowerCrystalRGB 000:000:255 ; BLUE Energy Crystals for "LegoSS.exe"
    1 point
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.