Posts from Expedition: general discussions. Auto-translated

Then it wouldn't be Sarnissa anymore...

Sarniss

I wouldn't join a squad like that; I don't trust him.

Perhaps it's time to talk about my plans regarding the experiment. I've rented a web server and am developing a web application specifically designed for running the experiment. Each participant will register a character, and that character will become an account that can be used to log in. There will be locations, and each location will be a chat room. I'm also trying to integrate everything I developed in my previous thread (I'm talking about the Shaman's Workshop). Right now, I'm facing a problem: I can't implement file uploads for character avatars because all the libraries conflict with the scripts responsible for authorization. How do you feel about this approach to running the experiment? Should I continue developing it?

chat room

If I understand you correctly, it won't be very convenient. The forum offers more opportunities for effectively formatting large posts, after all.
And overall, to be honest, it feels more "comfortable" to play in the Haven theme.
But if you use a similar engine to calculate battles, I'm all for it. The system with a calculator, a Paint-based map, and a random number generator is outdated and should be replaced with adequate applications that simplify the work for both GMs and players.

My games are outdated, just like me...

Added 6 minutes later
Regarding the matter at hand, I agree with Heroist. All of this is good and interesting, but the format of a forum topic (or topics) is better than a chat.

The chat is convenient for session-based games, where players gather together on a specific day and time to play. However, it doesn't work well with the expedition format.

Forget the chat. 95% of the experience is just arguing about builds and posting irrelevant stuff. It doesn't fit with the chat format.

I have no idea what kind of arguments you're talking about, but chatting and flooding the chat go very well together. I can confirm this from personal experience. Because of this, the GM later created two separate chats: one for chatting and another for game-related posts.

Well, a chat could be implemented in such a way that it functions as an asynchronous forum, where posts are updated in real-time.

Well, yes, calling it a "s**tstorm" is a bit of an exaggeration. It's more like obsessively optimizing build orders.

My games are outdated, just like me...

Nothing is outdated. Actually, I could use a fresh perspective during the development process. You have a lot of experience in this field.

Added 5 minutes later

Forget the chat. 95% of the experience is just arguing about builds and posting irrelevant content. It doesn't fit with the chat format.

For this, you can create a separate chat for casual conversations, and that's it. Or rather, I've already created a casual chat...

I agree about the cozy atmosphere with the Heroes community.

I also fully support Heroist's idea. A chat can be used for casual conversation (we actually created such chats in Skype for some expansions), and a chat is practically a must-have when communicating with the GM about battles, but it will be less suitable for in-game posts. And most importantly, it's the automatic battle calculation. The lack of such a system makes expeditions much more difficult for everyone, especially for the GM.

Sockets can be used to transmit not only text asynchronously... you can create a system that allows for a well-organized and engaging experience for each player. A system of threads. It's like a chat room, but with extended GM options. The GM can send the player not just text, but also options to choose from for a particular situation – you could create something like a quest format, for example. Or even images... The main thing is to save the history of this interaction in a database so that it doesn't get reset later.