Welcome to Evennia Discussions!

[Griatch]

👋 Welcome to the Evennia Discussions!

This is a central point for the Evennia community to communicate. Here you can ask questions, introduce yourself, talk about your Evennia project, discuss and interact with other users and developers! This complements the official Evennia support channel on Discord. When you make a post, the chat channel will be notified.

• If you find clear issues/bugs, don't report them here but in the issue tracker.
• See Code of Conduct for ways to behave. Basically, keep it civil.
• To get started, go and introduce yourself in the Introductions category!
• https://www.evennia.com is the central Evennia homepage.
• Evennia Discord support channel to chat in our very active community.
• https://www.evennia.com/docs/latest holds the Evennia docs.
• (The old Forum / mailing-list on Google groups is closed and acts as an archive of even older discussions).

Using Markdown

Discussions uses Markdown syntax with github extensions.

• Markdown basic syntax
• HTML tags allowed in text

Click here to expand the post with some Markdown usage examples.

Basic syntax

• Italic text : _Italic text_
• Bold text: **Bold text**
• Strikethrough text: ~~Strikethrough text~~
• verbatim text: `verbatim text`
• clickable link: [clickable link](https://www.evennia.com)
• Line separator: ----
• Emojis are created by :smile: 😄 . Starting to write : will present a popup with the available emojis as you type.
• : ![image text](https://url/to/image.png). You can also drag&drop or click the bottom of the editor.

Headings

#  level 1 heading (biggest)
##  level 2 heading
### level 3 heading
#### level 4 heading
##### level 5 heading (smallest)

Lists

- List item one
- List item two 

• List item one
• List item two

1. Numbered item one
2. Numbered item two

1. Numbered item one
2. Numbered item two

Verbatim multi-line text and Code blocks:

```
This is verbatim, multi-line text that retains 
the exact formatting
as you wrote ...                  ...  it!
```

This is verbatim, multi-line text that retains 
the exact formatting
as you wrote ...                  ...  it!

For code syntax highlighting, the language must be specified. Here is a list of supported syntax-highlighting languages.

```python
def hello_world(x, y):
    print(x, y)
```

def hello_world(x, y):
    print(x, y)

```html
<div class="nice">
   This is a nice text.
</div>
```

<div class="nice">
   This is a nice text.
</div>

Clickable, expanded section

The <details> HTML tag can be used for 'spoilers', hiding extra info and so on. This whole markdown-example section was created in this way.

Here is an example question with a hidden answer!
<details>
<summary>Click here to get the answer!</summary>
The answer is that you clicked correctly!
</details>

Here is an example question with a hidden answer!

Click here to get the answer!

The answer is that you clicked correctly!

[Griatch]

Discussions are still in beta and is missing some features, for example:

• Posting a discussion message does not appear to trigger a webhook yet, so we can't notify the IRC/Discord channels at this point. Update: This was added now!
• The categories does not appear to be possible to sort arbitrarily - they only sort alphabetically

But still, seems to be working fine so far.

[kovitikus]

@Griatch you said to let you know of any feedback on the Discussions thing, so that you can pass it along to Github.

I don't see any support for adding a spoiler to the post. I'm fully aware that the Discussions is basically markdown and that has no native support for spoilers, so there's a good possibility that they will just dismiss this suggestion outright.

Why would a spoiler be useful?

Well, let's say I'm making a post about coding challenges that a noob can try out. I want them to figure it out for themselves and then post their solution to the thread for other people to see how different people made different solutions. Maybe I even want to post my own solution to the challenge. Well, it'd help if the solutions were able to be hidden until clicked on. This way folk who want to go at the challenge without "cheating" won't accidentally glance at a solution and be influenced.

[Griatch]

Markdown also supports HTML tags and you can use the <details> tag for this:

Question: 
How do I do this or that? 
<details>
<summary>
Click here for the answer!
</summary>
The answer is ...
</details>

---

Question:
How do I do this or that?

Click here for the answer!

The answer is ...

[Griatch]

I have expanded the first post with some more info about this.

[kovitikus]

@Griatch This may be one of those select posts worth pinning, if this is meant to be the first thing people read when they start out here. The markdown is a great addition! Thanks. 💯

[Griatch]

Already added this, yes. And this post is already pinned 😉

[kovitikus]

Here's another suggestion for you @Griatch.

I can't seem to restrict who can create a discussion in certain categories, nor can I restrict who can respond to a specific discussion.

Seems that locking a discussion will prevent anyone from being able to respond, except for either collaborators or repo owner, depending on your settings. So I suppose this is a way to lock down a discussion so that only specific folk can respond to, although it seems really crude and doesn't allow much nuance. It still doesn't address category restrictions.

---

I created a development blog of my own on Hecate and it would be nice if I could restrict others from creating a new discussion in that category, but still allow replies on each individual discussion. This way I could get feedback from other folk, but I don't have rogue individuals posting in the category outside of its purpose.

[Griatch]

More fine-grained permissions have already been requested by others to github it seems. Github seems positive to implementing it, but when is unknown. I seems like it would support something like this in that case.