-
Posts
2,653 -
Joined
-
Last visited
-
Days Won
168
Content Type
Profiles
Articles
Forums
Events
Posts posted by Henk
-
-
Please make the title of your post [Buycraft Issue]*name*
In game name:
Proof of Purchase:
Description of Issue:
Date/Time of Purchase:
Items/Rank Bought:
Screenshots (Optional):
Any other important information:
Proof of purchase includes: PayPal Receipts, Transaction ID, and The Confirmation Email you received
Credit to akaElite for providing the template
-
Every now and then
We cycle thru sponge, network and bukkit, and each application takes about a month in total. The open period, the under review period, and the period after the application is done before I open another one. I don’t like chaining applications together and always have one open for a set of servers- mostly because we don’t need it, but also because if they are ”always” open i think players will easily overlook them too. If there is only ”one state” of applications, compared to if now when there’s a second state which is this kind of ”inbetween period”
-
I didn’t think I would be saying this, but I agree with swimsam.
Modded is an unstable place, and we can’t just restrict any item that has a risk of becoming corrupt and crashing the server. Heck, any block or item can become corrupt.
And for the record, it’s not always huge 300ish tesseracts machines that become corrupt.
And I don’t think it would be practical or even work if we per say would have a rule against placing more than X blocks of item Y.
Because while it is kind of sad, most players don’t pay much attentions to the rules and mostly just assume it’s common sense stuff- which for the majority it is.
So having something - excuse me - absurd like this in the rules would mean it would get missed by so many.
It’s as if instead changed our current restrictedItems plugin to no longer remove banned items that appear in your inventory and also tell you about it. But instead you would be punished for owning it, it wouldn’t be practical and the players would hate it.
And if the only purpose of doing this would be to prolong the wipe cycle to something like 8-9 montjs instead of 6, then I would also disagree with that. I think 6 months is a perfectly fine lenght of time for a wipe, as by that time we actually have players almost begging for a wipe. Not because of any instability, but more so because they feel ”done” and want to start over.
Sure, what you are suggesting could technically work if we would make a custom plugin limit you to certain amounts of blocks. Like we have for chunkloaders, but it’s far from perfect and has a few ways of getting around it. And people would try to get around it. It is also a lot more effort than it’s worth- as i mentioned earlier, just overall decreasing wouldn’t do a whole lot to prevent this issue. Sure, less would mean slightly less crahses, but usually the issue isn’t - for example, the tesseract - the tesseracts fault. It doesn’t have to be anyone’s fault, or anyTHING’s fault.
-
Welcome
-
-
Disabled, tell anyone who bought these kits to contact bruny or me and we'll get them a coupon code to buy something else
- Zethrindor and BombX
-
1
-
1
-
Transferred, the rank was on sf3, not network
-
-
I'm not sure I understand what you mean, you do have the sponsor+ rank
And all of the commands on buycraft are marked as " processed " meaning, they were successful
-
Reactivated
-
Reactivated
-
Transferred
-
Transferred
-
Ranks have no affect on it, probably just a weird coincidence. The chunkloaders are affected though if the server is running slowly. So hopefully next time you test they will be working just fine again
-
Reactivated
-
transferred
-
Should work now
-
Transferred
-
-
transferred
-
try now?
-
transferred
-
with the username iiheartless?
I deleted all the data and reactivated it, try now
-
[TEMPLATE] Buycraft Issue
in Technical Support
Posted
Example: