Quote from saneatali »
Thinking Man's Troll
Creature - Troll Advisor
: The next time ~ would die this turn, instead put it on top of its owner's library.
3/3
Good catch. But does it have to say “The next time...”? Couldn’t it just say “If Card Name would die this turn, instead...”?
3
There will be two:
One for "these are the basic tags and how they work"
Another for "This is actually everything you can do"
I'm trying to make them as "backwards compatible" as possible, but there will definitely be some that have to change in order to best serve stronger function. For instance, [hr]black[/hr] is what we have here, but [hr] (that's it, no closing tag, etc) will work easier for the average user. We can then add width, color, size, dashed/dotted/solid, etc, to make it a real customizable line for those of us who really want to control the look and feel.
4
The board software stores all posts in s9e/xml, so I would have to write a heft extension to sanitize the input and then convert it into the proper xml/s9e. Such would definitely take some time, and would definitely take a back seat to the myriad of other things we're wanting. That said, tag/property filtering is something that I want to add to the front end CMS eventually, so it's entirely possible that when it's worked out I can port it over. So hopefully down the road perhaps.
Before that, I'm fully willing to add ALL the various tags and parameters that we need. My goal is to have the basic usage as straight forward as possible, so the average user can use them intuitively, and also have them fully customizable for the more advanced user.
Our new [BOX] tag is a good example:
And I'm absolutely willing to add more optional/defaulted parameters as we need.
For [DECK]s, currently they use css columns to allow the browser to do the column breaking. That's not set in stone, and needs some more testing, but so far it's been rather good. Adding a COLUMNS parameter to specify the number of columns is doable. My only concern would be how to handle it with Mobile. I've been painstakingly careful that nothing anywhere ever makes a mobile screen have to scroll sideways. It might just have to force it back to 2 columns regardless at a certain screen size.
6
The staff and I are are creating a new home for our community. Moreso, we will have the freedom to innovate and create.
It will take time to get there (a lot more than the 40 days I have, so we'll be launching feature-light), but we will end up with something that truly does the community justice
15
We hope that you follow us to the new home we are currently building.
It's only 40 days away, so it won't have everything we've planned, but we will never stop building and improving it.
3
1
Here's what I've come up with:
The problem lies with "Gigantosaur" somewhere.
I've deleted and remade the card, and that seems to work fine for any new decks.
But it's caused some unknown issue to be persistent in your deck.
For your deck, if we remove Gigantosaur, we can update and save everything just fine.
If we re-add Gigantosaur, even the new version, it will save any decklist card changes, BUT it'll error out and not save any of the discussion/writeup updates.
I think at this point, the only thing we can do is to remake the deck.
That's definitely not ideal, but I don't see anyway to fix it as is.
If you open up two tabs, you can hopefully copy-paste everything over.
I apologize for this issue.
I'm honestly perplexed as to how it's still erroring.
I think Gigantosaur is just cursed.
1
You can also save and upload images attached to a post for use.
This is what I almost always do.
The test forum is a wonderful place to upload your images without clogging up real posts.
1
It's been labeled as one of the largest ad network redirect attacks anyone has seen.
Not only is it not just our site, it's across a multitude of ad networks.
Please be assured, our ad team is doing everything they can to kill the bad ads as soon as they arise.
1
I'll prod the developers to take another look.
(Also, irony: I didn't get a notification for this post. Apologies for the delay in response)
2
Here's some placeholders to work with in the interem.