 | | Re: Move along, nothing happening here... —Shiri Dori
|
| | | (...) <set:4558 This should link to a metroliner> <set:375 What do you see here?> (The above should link to 375) (...) <set:King_Leo's_Castle> <part:1x1 A brick> I think I get this now... the DB finds the first thing after "<set:" And makes the link (...) (25 years ago, 7-Mar-00, to lugnet.off-topic.test)
|
| | | |
| | | | | Re: Move along, nothing happening here... —Richard Franks
|
| | | | | (...) Yep :) Exactly! I wonder if this works: <<part:3005>> Can you be cunning: <set:6277 <set6285>> {How} [long] _before_ other FTX stuff is parsed too? :) Richard (25 years ago, 7-Mar-00, to lugnet.off-topic.test)
|
| | | | | |
| | | | | | | Re: Move along, nothing happening here... —Shiri Dori
|
| | | | | | OK, I'm having fun now... <set:6090 My favorite castle> (...) I think this might work better: <set:6091 <set:6094> > ;-) So let's see... <set:falcon+fortress Black Falcon Fortress?> <set:fortress+-falcon Wonder what this'll do> -Shiri (25 years ago, 7-Mar-00, to lugnet.off-topic.test)
|
| | | | | | |
| | | | | Re: Move along, nothing happening here... —Todd Lehman
|
| | | | (...) Yup -- that's about 99% right! What happens is this: <set:xxxx yyyyyyyy> It considers "set:xxxx" to be a URI with a fictitious protocol called "set". Thus, it considers "xxxx" to be a URL. Then it considers "yyyyyyyy" (optional) to be (...) (25 years ago, 7-Mar-00, to lugnet.off-topic.test)
|
| | | | |
