How to Add HTML to Lioden Profile: Save, Then Test

To add HTML to a Lioden profile, open your Den, scroll to Edit Your Details, paste a site-supported HTML fragment into Territory Description, save it, and inspect the rendered den on desktop and mobile. Begin with one link or image. Do not paste a complete `<html>` page or JavaScript, and remove forum-display asterisks only after checking every tag, quote, and closing tag.

The decisive moment is after Save. Before that click, you have text in a box; afterward, Lioden has parsed it, removed or altered anything it will not accept, and asked the browser to fetch any external files. I finish props under stage light because shop light lies. The same timing changes the result here: judge the rendered den, never the code sitting in the editor.

Where do you paste HTML on a Lioden profile?

Put profile markup in the Territory Description field under Edit Your Details on your Den page. The Official Lioden Wiki’s Your Den guide locates den text, pictures, and custom CSS there, and recommends isolating a stylesheet link at the top or bottom so it is harder to damage while editing.

Lioden’s in-game editor reports a 65,535-character maximum for Territory Description. The public Your Den Wiki page does not repeat that number, and field limits can change with a site update, so follow the counter in Edit Your Details if it differs. The count includes markup, attributes, URLs, spaces, and visible copy. That is ample room for prose and box HTML; shorter fragments remain much easier to inspect when the parser changes something.

Use this first-pass sequence:

1. Open Den and find Edit Your Details.
2. Copy the entire existing Territory Description into a plain-text backup.
3. Add one small fragment, such as a link, at the end of the field.
4. Save, reload the Den, and inspect what actually rendered before adding the next piece.

A cave description is a separate field. Paste cave-specific code into that cave’s description rather than assuming the Territory Description will move or restyle cave content for you.

Which HTML will Lioden render?

Lioden renders selected fragment markup inside an existing game page; it does not give a player an unrestricted web document. A fragment might be an anchor, an image, a heading, or a styled paragraph. The surrounding document, scripts, navigation, and page structure still belong to Lioden.

The dominant bad instruction is to paste a complete page containing `<html>`, `<head>`, `<body>`, or `<script>` tags. Those elements belong to a document root or active program, while the Territory Description is a filtered content field. JavaScript, event attributes such as `onclick`, forms, iframes, and other active content should stay out of Lioden profile codes.

EasyPlesi’s Unofficial Lioden HTML Forum Help Thread, updated January 19, 2024, demonstrates basic formatting, headings, paragraphs, anchors, and images on Lioden. It is a practical guide, though it is not a versioned allow-list. The smallest useful fragment is the right test:

```html <a href="/territory.php?id=YOUR_LIODEN_ID">Visit my side account</a> ```

If the saved result becomes plain text, disappears, or loses an attribute, believe the rendered result. Standard HTML syntax does not overrule Lioden’s sanitizer.

Keep each test fragment valid on its own. One missing quote can turn the next attribute into part of a URL; one unclosed anchor can make everything beneath it clickable. Saving several untested fragments together hides which one failed and encourages the least useful repair: changing several lines at once.

How do you copy Lioden forum code safely?

Forum authors insert asterisks so Lioden will display tags instead of executing them in the instructional post. EasyPlesi’s guide, for example, prints an anchor as `<a href="PAGEURL">text</a>`. For use in an allowed profile field, that particular escaped example becomes:

```html <a href="PAGEURL">text</a> ```

Do not run a blind “delete every ``” replacement. An asterisk can be ordinary text or a CSS universal selector. Remove only the characters the creator identifies as forum escapes, commonly the `` immediately after `<` in an opening or closing tag. Then check paired quotes, nesting order, and the closing slash.

Code length also changes when it moves out of a forum. Lioden’s Trivia Answers Masterpost and Chris’s free-CSS thread both document a 20,000-character maximum for one forum post. A code sample may therefore be split across replies even though the Territory Description itself holds 65,535 characters. Reassemble parts in the creator’s stated order; reply order is not a dependency map.

How do you add links, images, and spoilers first?

Links make the best first test because they have one dependency: the destination. Use an anchor with a complete Lioden or HTTPS address, save, click it, and confirm where it lands. For an external destination, write link text that names the destination rather than “click here.”

Images add another failure point. The `src` must be a direct, permitted image URL, not an album, gallery, or webpage URL. Open the candidate URL in a clean tab. It should show the image itself, and its response should be an image file such as PNG, JPEG, GIF, or WebP.

```html <img src="DIRECT_IMAGE_URL" alt="Short description of the image" style="max-width:100%;height:auto;"> ```

The Official Lioden Wiki gives one firm platform dimension: a custom off-site profile tag image can be no larger than 150 × 150 pixels. That rule applies to the Tag field. The Wiki does not state the same 150-pixel ceiling for images placed inside Territory Description, so do not mislabel it as a universal banner limit. Responsive sizing still matters; `max-width:100%` keeps a large inline image from forcing horizontal scrolling.

For a Lioden HTML spoiler, use the site’s spoiler syntax shown in the forum guide:

```text [spoiler]Hidden text goes here.[/spoiler] ```

That is Lioden markup rather than an HTML `<spoiler>` element. The guide warns that spoilers can break inside tables. Test the spoiler alone, save it, and only then place more elaborate content inside it.

How is an external CSS layout different from inline HTML?

Inline HTML adds content inside Territory Description. External CSS restyles existing Lioden elements after the browser downloads a separate stylesheet. The Official Wiki shows the stylesheet link being pasted into Territory Description, but shared placement does not give the two methods equal reliability or maintenance.

• Inline anchors and text remain in the Lioden field. A hosted stylesheet can vanish when its owner deletes, renames, or restricts the file.
• An image fragment depends on its image host. A CSS layout may depend on the stylesheet host, fonts, background images, and Lioden’s current selectors.
• A small fragment usually affects its own content. CSS can alter navigation, tables, text contrast, and page width across the den.
• Inline markup needs inspection when Lioden’s sanitizer changes. CSS also needs revision when Lioden changes class names or page structure.

The dependency count is visible in the source. Chris’s free-use Assignment layout declares two asset URLs inside its CSS: one Google Fonts import and one background image. The stylesheet link itself makes three remote dependencies before counting the font files returned by Google. Its source also contains four distinct max-width breakpoints—620, 684, 768, and 993 pixels—so “works on mobile” is a set of deliberate rules, not a reassuring label.

Open a stylesheet URL before installing it. A usable link should expose CSS rather than a host login, preview page, or access-denied message. Search the source for `@import` and `url(...)`; each result names another file that can fail. Save the exact source URL with your backup because a gallery screenshot cannot restore a missing stylesheet.

GitHub can be a steadier code host than an anonymous paste, and GitHub Status publishes Pages history over a rolling 90-day uptime period. That period is an observation window, not a promise that a particular player repository or file path will remain available. Chris’s stylesheet header says the free-use permission can change and points users back to the creator’s rules. Keep the credit and the source link.

When should you test a Lioden layout on mobile?

Test immediately after every meaningful save, while you still know what changed. Load the actual Den at a narrow width, reload it rather than trusting an open tab, and follow every important link. Check the navigation, lion tables, description text, spoilers, and any button needed to use the page.

A layout can satisfy all four stylesheet breakpoints and still push a fixed-width child off-screen at a 375-pixel viewport. I finish props under stage light because shop light lies; the saved phone view is the equivalent performance condition. It exposes clipped navigation, tiny type, and boxes the desktop preview hid.

When something breaks, restore the backup first. Reintroduce the plain text, then links and images, then box markup, and load the CSS last. This order separates a malformed fragment from a failed external asset. If removing the stylesheet restores readability, leave it off while you audit its source rather than patching random selectors into the den.

What Lioden rules and costs apply to profile code?

Lioden’s current Code of Conduct expressly covers public den pages, shop and trade descriptions, lion biographies, forums, chat, and private messages. It also prohibits generative-AI text, images, videos, and code on Lioden, and separately prohibits scripts used to automate play. The Terms of Service bars infringing, deceptive, inappropriate, or unlawful linked content. Check the current Code before publishing; profile decoration does not create an exception.

Adding supported HTML or linking a stylesheet to Territory Description has a platform cost of 0 GB. A creator may charge for a commissioned layout, but that is a third-party service price. For comparison, Lioden’s official Oasis price sheet lists the Custom Decor Creation tool at 10 GB. That tool submits art as an in-game decor; it is unrelated to installing den HTML or CSS.

Treat creator instructions as part of the asset. Chris’s free layouts require retained credit and prohibit resale. If a template lacks a named creator, usage terms, readable source, or a rollback instruction, skip it. Twelve years making props to a date has made me partial to boring provenance: opening night is a poor time to discover who owns the sword.

What is the safest order for publishing Lioden den HTML?

Build the den in seven recoverable passes:

1. Back up the current Territory Description as plain text.
2. Test one supported HTML fragment and inspect the saved render.
3. Clean only identified forum-escape characters and validate tag pairs.
4. Add direct links, direct image URLs, descriptive alt text, and spoilers separately.
5. Audit any external CSS for permission, dependencies, and responsive breakpoints.
6. Save and inspect the den on desktop and a real phone.
7. Keep the last working copy beside the creator’s source URL so rollback takes one paste.

I used to build architectural models at 1:200, where the whole building could fit on a desk and one misplaced millimetre still changed the elevation. A Lioden layout deserves the same discipline. Make one change, view it at the scale where it will be used, and preserve the version that worked.

Frequently asked questions

Where can I find Lioden HTML layouts?

Look in Lioden’s HTML Help and Layout & CSS Sales boards, where creator threads state permissions, credits, installation steps, and update history. The Official Lioden Wiki’s Your Den page explains where the code goes. Prefer a layout with readable source, a named creator, mobile rules, and a stable file host.

Are free Lioden HTML templates safe to use?

A free template is safe only after you read its source and creator terms. Reject JavaScript, forms, iframes, hidden redirects, unknown image hosts, and unreadable shortened URLs. Count every external dependency, keep required credit, save your current description, and test the template after Lioden sanitizes it. “Free” describes price, not risk.

How does Lioden CSS work?

Lioden CSS works through a hosted stylesheet linked from Territory Description. The browser downloads that file and applies its selectors to Lioden’s existing page elements. It can restyle much more than inline profile HTML, yet it can also fail when the host, file path, external assets, or Lioden’s page structure changes.

How can I make a spoiler in Lioden HTML?

Use Lioden’s bracket syntax: `[spoiler]hidden text[/spoiler]`. The current community HTML guide uses that form rather than a `<spoiler>` tag and warns that spoilers can misbehave inside tables. Save a plain spoiler first, verify that it opens and closes, then add formatted content inside without disturbing the brackets.

Can I add a cave layout with HTML?

Yes, cave descriptions support Lioden customization, but each cave has its own description field. Install cave-specific markup there and follow the layout creator’s placement instructions. A Territory Description stylesheet may affect shared page elements, yet it does not automatically place cave text or guarantee that den box code will fit a cave.

Which tags does the current Territory Description editor allow?

Lioden does not publish a complete, versioned tag allow-list on its Your Den Wiki page. The current community guide demonstrates basic formatting, headings, paragraphs, anchors, and images; spoilers use bracket markup. Test one fragment in Territory Description and inspect the saved output, because Lioden’s sanitizer is the final authority on tags and attributes.