If it is not too much to ask, could you all kindly alleviate the affliction. Or as an alternative allow a duplicate account (of course I'd tell you the name and such)?

EDIT:
ALRIGHT SOLVED, SUSPENSION REMOVED, TOPIC CAN BE CLOSED

/humor

Post has been edited 1 time(s), last time on Jun 28 2011, 4:24 am by TiKels.

Alignment issue. D;

To fix it, the skin author should apply the background-images directly to the TDs rather than their contained DIVs. The background-position on the TDs should be [anything] bottom, and the background-repeat oughta be repeat-x. The DIVs' height (currently set to 59px) should also become min-height.

These changes will fix it in FF3.6.17. I have not tested in any other browsers.

When you're looking at which people voted for what in polls (hovering over the box with a question mark to the right of the choice), the people who voted for the first choice can only be seen if you put your mouse at the very bottom of the box. The second box works normally; you can put your mouse anywhere over it and see who voted for that choice. I've only noticed this problem in polls with two choices; I don't know how it is for other polls.

Need a name color warning that you can only change the name color once with the item...

Now my name is to dark I think...

anyway, wohoo I got name color...

Anyone know if the mineral tax system truncates, rounds evenly, or rounds up? Basically, I wanna know if I send 21 minerals, will I pay 2 minerals tax (round up), or 1 mineral (rounds down/truncates). This can be tested by sending someone 21 minerals and 31 minerals, because if 21 rounds up, the tax always rounds up, and if 31 has a tax of 1, it truncates, while a 2 mineral tax means it rounds evenly.

It already does say that on the item's info: http://www.staredit.net/?p=store&area=viewitem&item=10

who reads that?
The info has to be shown at ... where you type in the color...

I agree. When I entered my color, the realization that it can't be changed afterward was payneful.

Sorry...

For how expensive the name color is, it better be customizable afterward. Even shoutbox color can be changed infinitely after purchase.

It wont be changeable after purchasing.

I'll see if I can add info about the 1 time use on the store page.

NO U DON'T.
Done it already.


There's now a warning reminding the user when he is using the item (about to enter the color).

SEN doesn't like Korean(?), or at least certain characters in [img=] tags. Same is probably true for [img][/img].



vs.

Are you sure that is not because it is a bmp and takes forever to load?

I first tried it with another .bmp that was the same exact picture renamed.

Also, this is broken

Warning: require(scripts/response/response.php) [function.require]: failed to open stream: No such file or directory in /home/starlite/public_html/index.php on line 475

Fatal error: require() [function.require]: Failed opening required 'scripts/response/response.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/starlite/public_html/index.php on line 475
When trying to join a clan

The signature bug STILL EXISTS FROM 2 YEARS AGO WHEN I BITCHED ABOUT IT THEN.

Here's the code, minus the pictures.




As you can see, it also bugs outside of signatures, but the links are to very different URLs. We already know it's because of too much BBcode around the URL, but this wouldn't be a problem in any other forum. Only SEN. I did fix it myself by moving around the color tags, but I shouldn't have to. IIRC we even were informed of the problem, just nobody got around to fixing it...

lol.. I was on FB chat the other day and talking to someone I know IRL and I said my back was payneful. I shuddered. Also, my Inbox is still fubar. Priority fix's dont work. And I'm not going to buy new space because I'm close to having a name colour.

The links work in your signature, just not in the post.

EDIT:
Testing without font tags:



Testing without color tags:



Yay, too many BBCodeessssss

Post has been edited 2 time(s), last time on Aug 1 2011, 7:29 pm by DevliN.

Hey multi-quote isn't broken on Chrome, just confirmed on Chrome 12