I don't see myself disabling nested quotes, but there are probably some better defaults. Maybe by default "Reply" doesn't grab any of the nested quotes and there's a "Full Reply" button that does. Or maybe there's a "Toggle Advanced Mode" user-option that adds buttons beyond "Reply" and "Edit".I believe that would be a much more viable option. Or maybe a "reply" button that only quotes the new text, minus the quotes, and a "quote" button, which grabs it all. Whatever you choose, I believe it's a great idea to make it a separate option.
LegendBegins is a Moderator. They assist users and keep the forum running smoothly. They have power across all forums.
LegendBegins Moderator
STATUS: Really excited for the new feature we've been cooking... 3 mos ago
- Last Seen: Online
- Joined: 12 yrs ago
- Posts: 7197 (1.58 / day)
- VMs: 1
-
Username history
- LegendBegins 12 yrs ago
-
Latest 10 profile visitors:
-
Most recent →
TruckKun,
Tyler Night,
Gadg8eer,
WrongEndoftheRainbow,
Majoraa,
Ashifa ASMR YT,
tadcfnaf,
xVampire3go,
GreatBorealis,
Vampiretwilight
Status
Recent Statuses
3 mos ago
Current
Really excited for the new feature we've been cooking...
8
likes
10 mos ago
I just try to keep my maturity low enough that my account age is the only indicator that I should be on this site.
2
likes
10 mos ago
Clearly a man can't sleep without getting woken up by an explosion of spambots.
11
likes
1 yr ago
Rules of the Guild include not discussing bans. roleplayerguild.com/topics/…
2
likes
1 yr ago
Guild should be back to normal! Hope you all took the opportunity to touch some grass ;)
12
likes
Bio
User has no bio, yet
Most Recent Posts
At some point, will the nesting quotes be disabled?
There's one feature we wonder if you're planning (for moderators)... The ability to change post authors. It would be very convenient for RPs when the one who posted the first IC/OoC/CS post leaves for some reason or other, as it means the remaining players can keep the RP running in the same thread.I agree with this. It would be quite helpful.
> Right now the avatar system is a dirty hack. But I just couldn't justify the weak cost/reward ratio of implementing an upload system when there are so many other things I can be working on.
>
> I do want to migrate to an image-upload system that actually does image scaling/resizing.
I don't disagree with that decision. It will just be simpler when avatars aren't required to be sized 150 x 150.
> Is there any chance that the Guild will support higher resolution, and possibly auto-size it down at some point?
My apologies, I failed to clarify. Higher resolution of profile pictures*.
Is there any chance that the Guild will support higher resolution, and possibly auto-size it down at some point?
> Lots of goblins down these rabbit holes. Been feasting on them to stay alive.
>
> Also passed by Jon Krakauer's corpse.
You are assuring that you're taking enough time off, right? The last thing any of us need is for you to burn yourself out.
> I'm awaiting the decision
We'll move back when it is logical and convenient to do so.
>
> Yeah, the logic of the dice roll itself is simple, but people generally want a dice system that's backed by the database.
>
> For example, you shouldn't be able to just edit your post and re-roll a new number. You also shouldn't be able to roll three dice for three events and then re-order the events according to favorable rolls. In other words, people want a verifiable, irrevocable ledger of rolls. I could easily support such a thing as a first-class component of the forum.
>
> The website escapes me at the moment, but the guys in the Tabletop Roleplaying forum sometimes use a webservice for this purpose that is a good example of what I mean by this.
>
> It's not a technical challenge so much as it's an open-ended one. I'm in a position to create a really good forum dice-roller that integrates with our roleplaying system, but since I don't use dice, I'm not sure what kind of UI people want. I could use some help coming up with some rough mockups.
True. You could always have the server return an uneditable string that says "rollerName rolled valueOfDie," which could therefore not be easily manipulated, because it cannot be edited, deleted, or moved.
>
> Yeah, that was an idea under consideration even a year ago.
>
> I like the general idea of it, but it's non-trivial from both a system standpoint and from a UX standpoint. That sort of change would require a ripple of changes across the system, and it needs to be nailed correctly the first time since it's not easy to change such a big generalization of the tab system.
>
> I made mockups of some ideas for custom tabs, but a lot of people in IRC pointed out that it complicated what was an otherwise simple system.
>
> It's not something I'm comfortable inventing by myself. I would need help from people that strongly support that kind of feature since it's them I'm doing it for, after all. For comparison, creating the "IC"/"OOC" tabs was a rather uncontroversial/obvious upgrade.
>
> Same thing with the dice system. I'd like to come up with a few ideas and pitch them to those interested in on-forum support for dice.
>
> Edit: Reply to your edit, I agree. When I introduce BBCode again, I'm going to change the quoting mechanism to use BBCode quotes which retain info like which post you're replying to and who wrote it.
Forgive my inexperience in JavaScript, but (correct me if I'm wrong) as an object oriented programming language, wouldn't a dice-roller be as simple as creating a rolling method, reading user input for the number of dice, and perhaps the number of sides, and returning a random value between one and the maximum, and have the server display that value either on the post, or wherever you choose to place it? Even a rough prototype could roll a single die, and return the sentence "The rolled die value is: valueOfDie" to the post box, and while that could be easily manipulated, it's a start.
>
> - Yeah, BBCode is coming back. I'm trying to do it right this time from the start rather than relegating BBCode to a hotfix shadow-world between real BBCode and what become known as QQCode. As QQCode became more and more entrenched over time, my attempts at patching it were breaking too many posts since everyone got used to its idiosyncrasies.
> - I agree - the current state of formatting isn't that great. Markdown isn't a rich formatting syntax that people generally expect from forums. But I chose it for the v0.1 relaunch because:
> 1. It's bare-bones. Markdown-formatted text is still readable even if I dropped support for it overnight. It's something I can build on top of because it's mostly non-intrusive and doesn't really clash with anything.
> 2. I found a good editor + Markdown parser + preview button + javascript library package that let me cobble together something that worked so I could focus on rewriting the other components of the forum. For example, I use this: <http://www.codingdrama.com/bootstrap-markdown/>.
>
> I recognize that maybe no formatting (rather, just line-break formatting) might have been better for the relaunch though. :(
>
> I look forward to extending the editor with BBCode and other features that assist post organization. Someone mentioned <https://www.iwakuroleplay.com/> recently as a forum with some cool formatting features like tabs that people seem to like. I like that!
>
> I also want to retro-patch posts to honor line-breaks which should be doable without breaking anything (well, just lines).
> - Regarding client-side Markdown rendering, it's not pretty. It may help to know that the render is triggered by an "appear" event on each post that unfortunately doesn't trigger until you start scrolling. Often you land in a topic and just see a wall of text as the first post until you move the page.
>
> I really want to move rendering back onto the server, but the naive solution (rendering posts on the fly when the server is generating the response) just wasn't performant enough for cases when you're looking at large posts. Since performance was my primary goal of the rewrite, I decided to offload the solution to the client until I can give it some thought and engineer a real solution. I don't really have the stomach for quick fixes anymore!
>
> Anyways, you're right on. Post formatting is a sorry situation at the moment. I'm trying to dedicate most of my time this first week of the relaunch to things like system errors.
>
> I've also started working on a real notification system. But perhaps post formatting would've been a better goal!
Regarding the tabs, have you considered allowing the thread creator, or a designated thread administrator to add or delete tabs connected to the Roleplay?
Edit: Nesting posts may become an issue if they become overstacked, and I know that many roleplays prefer the quote system, because the players know who the post is referring to, without needing every post before that. Perhaps a feature to toggle nesting quotes could be considered?
© 2007-2026