Oh, I'm not missing anything. I was pretty much every day in the BV Staff room asking for possible compromises to help smooth things out for former PMDT devs. I was keeping discussions here and explaining our reasons because I believed a consensus could be reached.
Rather than having this discussion in a public forum, is there any way we can have a private discussion between the BV staff and former-PMDT members?
That way, we can have a reasonable discussion to clear up any misunderstandings without the peanut gallery chiming in.
I feel like that would be the best way to get this sorted out in a civil manner and reach a compromise where both parties are happy.
Rules have not been touched since November 25, 2013. Our decision literally means we're not adjusting the rules to add Project M as an exception to them, not the opposite.
Nobody is asking the admins to add Project M as an exception to the rules. We're saying content that is stolen (or leaked, or whatever you want to call it) should have no place here on the Vault regardless of who the original creator was.
It's hard to take this matter seriously with the amount of theatrics some people are pulling off. If you folks are that intent of making me the villain of a Saturday morning cartoon, I might just as well humor you and play my role.
Those "theatrics" are just people expressing their frustration at being stonewalled or ignored at every turn. "Civil discussion" goes both ways. If you want a polite discussion, you're gonna have to throw us a bone or two here.
Because if we asked the community to make administrative decisions, there'd be comments on the Vault, packs wouldn't require a full credits list, all Sonic recolors would be banned from the Vault ever and any popular user asking nicely could get executive decisions done with no regards for double-standards or long-term consequences. :v
Again, not the point.
The point is that most of the members here would be uncomfortable with allowing leaked/stolen works on the vault. It's wrong no matter how you slice it, and nearly everybody here seems to see that.
It's not a clear cut black vs white scenario. You could take an extreme example of people hacking into your dropbox. I could answer with authors that prevent people from posting valid hacks for selfish reasons.
The reason we're still going for that approach is because we've never had incidents like the former happen, but we've had creators that did the latter. I can sympathize with the desire not to get your work released before its due date, but considering how rarely that situation has popped up, and how less damaging it is compared to something like actual BV thefts, we might as well do it on a case-by-base basis if that ever happens. It still outweighs the need to check for permissions or the awful idea of giving users the ability to take down edits of their work.
We're making an exception for PMDT members to be immune from reuploads for a period of time. We're adding the possibility to take down duplicates to mitigate the "damage" of WIP files. I'm also discussing with L_L on an idea that could ease things up even further for PMDT members. Finally, you all seem to be grossly underestimating the power of having a civil discussion with users who re-uploaded your work. If you're just about to release your thing and get the duplicates replaced, I doubt anyone would care much about keeping the WIP on.
But that's as far as we're going to go. We're not going to make even more of an exceptional rule just for the former PMDT.
This is missing the point entirely -_-
Let me try again:
Mods that are obtained in a dishonest manner (i.e. without the creator releasing them first), should not be allowed on the vault. This would apply to everyone, not just the PMDT.
No modder would appreciate their unfinished work being posted if it were leaked/stolen. It utterly baffles me that submissions of stolen work would even be allowed here.
There's unfinished/unpolished content submitted on a daily basis. And there' are re-uploads too. I haven't checked if there are unfinished re-uploads, but I don't see why it wouldn't be allowed.
You don't find any moral qualms at all in uploading stolen work without one's consent? Nothing at all? Even if the creator asks you to wait and let them upload it when they're ready (or when it's finished)? What if someone hacked my dropbox and decided to upload all of my WIP stages? Would that be okay and allowed on the vault?
All we can offer you is some time to post anything you might have already finished, and the removal of duplicates afterwards. After that, you are free to take it up with the submitters if the situation happens for your own mods, although I would encourage you to be a tad more open-minded and cordial with them.
Can you please explain why it's okay to upload stolen work that's not even finished yet?
For example, I have an old copy of Mewtwo2000's Mute City. I stumbled upon it accidentally, and it's not something that was intended for the public yet. I'm more than capable of finishing it myself, but it would be "passable" in its current state. Would it be okay for me to upload the stage to the vault (with proper credit), against the original creator's wishes? I'd imagine the answer would be a resounding "no."
So why then, is it okay to upload stolen PM stuff?
Former P:M members are free to upload their own work. Starting on the 15th of February, other users will also be able to re-upload those (unedited) works if they are missing from the Vault, with proper credit.
I don't really understand this. Why are you giving us a deadline to upload stolen work? Some of the work isn't even done yet. Please, let the authors release their work if/when they're ready. This wouldn't fly if work was stolen from an individual modder, so I don't see why it's okay just because it was made by the (former) PMDT.
I only tried the "normal" version of the stage, but I can confirm that that there are errors in that one. MShadow1 has a misnamed bone so the model animation moves it to mshadow3's postition instead. MShadow 3 also extends slightly off of the main stage, so shadows appear in the air. Also, all of the shadows are just a tiny bit too low, so they caused flickering (at least on dolphin, not sure about the wii yet, but it probably flickers there too).
Figured I'd post this here since almsot nobody seems to know about it:
Open a stage .rel in Brawlbox. Then open up section[4] and look inside. Here you can find a bunch of constants that you can alter to change certain things about the stage. This is how we fixed a camera bug for Infinite Glacier in PM. It takes some experimentation to figure out what each constant does, but If you know around what value you're looking for, it's easier to find what you need.
Also, I've been using your quick inject program. It's SO much better than having to edit the autohotkey script every time I want to work on a different stage.
Still a LOT of refining to do. I'm also thinking of changing the layout since Smash 4 is already out in Japan and it's only a few weeks away from the US release.
I'll finish it eventually... I've been pretty busy with school and, ever since I joined the PMDT, pretty much all of my modding time has been focused on Project M
Little question about the debug mode if you don't mind me asking.
Will it activate when you "press L, R and D-Pad down" or when you "press both shield buttons and down taunt"? Just curious becouse I have different button layouts.
It's the same combo regardless of the button layout you have set.
Show Posts
