Bringing the original JS feel back #129
Comments
|
Some suggestions:
Keep in mind I am brainstorming and some of these may not be practical. Based on my experience with the CTM error in the base pack, I agree that we either need much better communication with the base pack maintainer or we need to fork a version of the base pack and make it our own. |
|
The problem with the base pack at this point as has been brought up is that it really isn't JS anymore. It's Jim Stone's take on the original JS pack. I have every single version of the pack on my PC in a folder and going back and looking some of it is the same but there are some things that just don't fit. Now bear in mind I understand things evolve, but It should really be called Jim Stone at this point as he has changed it so much. I think going back to the last version John Smith created and using that as a jumping off point would be best and I do think we should create our own base to use. Not saying we have to use those exact textures but yeah. I do like the customizer idea and a web app that would help with ore textures would be fantastic. I unfortunately don't know how to do web pages. |
|
I don't really think Legacy has changed that much from the original stuff. It's pretty much just adding textures for the new stuff, some look good, some look less good. We can replace that stuff if we want. No need to throw the baby out with the bathwater. Could you give some specifics about the stuff you're unhappy about? I do understand the impulse to want to get people excited about the pack again and do a big reboot thing, though. |
|
The problem is, we still don't have a customiser script available that meets our needs. For example, changing the stone texture means changing all of the ores along with it. Back when I ran the jslegacy.com site, we did have a customiser which was functional, but it was hard to manage and didn't have all the features that we would have liked, and when the site went down, that was that. |
|
@Glowstrontium If you still have the script, I may be able to rework it and find hosting. |
|
I was typing a response and just noticed the bar on the right was getting quite tiny so I decided to start over. This may sound like a small thing but the flowers in the base pack bug me a bit now. Some of them are alright, but I liked the simplicity of the original flowers and would like to go in that direction with them. That's just one example of something though. I remember at one point Morvelira was using our pack and I liked watching someone play in a world that looked like the one I liked to play in. I want people to feel as excited as I do about this pack. I also get frustrated with my own limitations sometimes as well. I wish I had the money to hire a team of people to work on everything because I would if I could. :) |
|
I also have felt a bit on my own here until recently. I can totally understand people drifting away from the game and such. I guess I am weird. Even when I don't feel like playing it makes me happy to work on this pack. |
|
I don't have any free time due to my studies, but let me know if you need any help with things on my end. As for the old customizer, it run off one one I coded a while back. If you wanted to set that up, and just to see what it looked like, here is the old data folder. [link] |
|
@goldbattle Thanks for this. I'll take a look. I am very familiar with php, but the limiting factor for me is time. |
|
We do have another version of the customizer which is more advanced than the first version along with being universal but I'm the same with Gold that have little time to work on things. It's PHP based and If any of you guys want to help out to get it finished I would have happy to add you the repo and chat on something to get you up to speed on how it works etc... If anything I would prefer to see that version being used rather than the older one due to what is supported now which would benefit JSTR. |
|
@artdude543 Please add me. I'd like to take a crack at it. |
|
Okay, will need to PM you something before hand tho. Can't remember if I added you on anything. I think I have you on Curse Voice. |
|
Can't get to CV right now. If you are a twitterer, I'm ScottKillenMC. |
|
Just checked...We follow each other on Twitter, so maybe DM me there? |
|
Done ;) |
|
While we're discussing radical ideas, does the name Technician's Remix seem a little dated to you guys? Don't get me wrong, I do like the name, but I think it might give people the wrong idea. It 's evocative of the old Technic/Tekkit days when tech was THE thing, but modded Minecraft is so much more expansive now. Tech is just one of many aspects people enjoy. Not that I have an alternative or anything, it's just a thought. |
|
Well that's exactly where the mod support started (http://forums.technicpack.net/topic/28411-32x-johnsmith-technictekkit/). Changing the name of and Legacy has been considered in the past due to the potential confusion, but nothing came of it. Maybe going forward, it might be better to just scrap the JSTR alternatives and base the mod support on the Legacy pack. A customiser or an "addon" pack would still be needed for those who prefer the smooth stone texture.etc, and because I haven't been involved around here for a long time, I don't know what the userbase's opinions would be on that. |
|
Well, we did launch the Legacy overwrite patch, which I've pretty much maintained myself. It has a pretty small number of downloads, but that is to be expected considering it's not on the FTB launcher, and a lot of people probably don't know it exists. Plus downloading another pack is an extra step a lot of people wont bother with. I'm guessing most of the users are very used to the JSTR look at this point. I prefer the Legacy style personally, while other texturers have seem to have strong attachment to the JSTR look. |
|
I personally prefer the smother stone look. It looks too busy to me to use the other one. On the subject of name perhaps a change would be good as I agree the pack is about more than just tech at this point. I will have to ponder that one as it should grab attention but not be too trendy as it would age badly then |
|
Maybe something like "John Smith Plus", or "John Smith: Expanded"? |
|
JS Modmix perhaps? as a logo using the John Smith font with John Smith for modded in a smallish font underneath. That's just what I came up with off the top of my head. The less wordy the main title is the better and it rolls off the tongue pretty well. |
|
So for more of an ancient or Medieval sound how about: John Smith Compendium or John Smith Synoptic. Also John Smith: Exhaustive Remix 😀 |
|
Giving is some more thought: What about "Compendium: A JohnSmith Remix"? It would be called Compendium, but the logo and official title would work in its JohnSmith roots. |
|
or, perhaps: Compendium: JohnSmith Evolved |
|
I like the Compendium idea. Not sure about distancing the John Smith brand, so to speak. We're still sticking pretty close to the JS style, and not really branching out like for example Conquest did. I'm leaning toward John Smith Compendium, with a tagline like "a texture pack for modded Minecraft" to clarify. |
|
On a side note, I've noticed more and more mods are being released as 1.8, so perhaps it's time to make the JSTR-1.8.x repository? I also like the title with Compendium, personally I feel "Compendium: A JohnSmith Remix" flows off the tongue the smoothest. |
|
I don' think 1.8 Is ever going to be a big thing. I think all the major mods are waiting for 1.9, but I suppose we can. Since it won't have to support all the big ones. Also I like Compendium: A JohnSmith Remix as well. I want a little distance as the body of work here is only based on the base pack. John Smith never did any of the mod textures except the ones we recycled. |
|
@Greenhawk837 Understood. If you ever do put it up again, I'd like to be a contributor. Some of the textures I committed today would look good in 64x |
|
If it's for modded textures then I think It would be a good idea to set up a repo again, but for the base pack I'm going to leave that off Github. |
|
Yeah, modded textures. |
|
Just set up a repo and invited you to it |
|
So, for the relaunch we should think about how we present this pack. We need some new, pretty screenshots. I would also like to see the Legacy pack presented side by side with the regular pack as a standalone. Maybe it's a waste of hosting to keep two packs that's 95% the same content, but I would really like to see how it would do in that scenario. I'm fine with updating the Legacy pack for a smaller audience, but making it more visible and accessible could get more people on board with the pack in general. Compendium: Legacy Edition and Compendium: Remix Edition. Something like that. |
|
Depending on the functionality of the customiser, all we'd have to do is have the changed files separate and it'll merge/zip then together. The same function would allow users to pick and choose what mods they want/need when downloading. |
|
A customizer is great and all, but most users will just be downloading the universal pack. A lot of people also use the FTB launcher to discover and download resource packs. I just think it would be cool if the Legacy pack could reach that audience. |
|
Hadn't thought of those examples, yeah guess we would wind up hosting two versions then, 4 technically if we consider the 64x versions as well. |
|
Jimstonecraft was reluctant to have the Vanilla Legacy pack on the JSTR site as he was and possibly still is the only one maintaining that pack. I think we should have a repo for the main base pack for the modded version to make everything more streamlined. |
|
You mean putting all the vanilla textures in a repo instead of just the overwrites we have now? Would be good to not be dependent on a third party. |
|
The "JSTR" base (that includes the smooth stone and my metal block textures.etc), as well as the others that happen to be the same. Basically what is in the Curseforge download. |
|
Is there any particular reason why we can't put the base in the main repository but name it's mod "Minecraft" It would make it easier to reference in the future when making more textures that fit the theme, or does it have something to do with distribution rights |
|
The technology we use to assemble the pack will determine the shape of the repositories. The repo looks like it does now (with each mod in its own directory) because the soartex patcher was once used to patch the base pack. Now, if that will no longer be the case and if we will be assembling just a few downloads, I would like to suggest the following downloads:
Each would have a separate repository. If we revert to the flattened folder structure, I could write a platform independent (Windows, OSX, Linux) build script that would assemble both packs (and possibly even upload them to curseforge fort anyone with the curseforge information) I would like to suggest that we decide on some procedures by which a group of someones has the authority to determine stylistic direction. Perhaps as an incentive, this group gets to split the curseforge points from downloads. (This adds up to something valuable very quickly.) Also some procedures (such as requiring updates to the Legacy repo whenever ores and the like are contributed) would be good moving forward. |
|
That's the idea most likely. If they are in separate repos, there would probably need to be one for each version and it'd start getting cluttered around here. |
|
I would like to be part of the group in charge of stylistic direction. I think I have a good idea for when something fits the look of the pack vs something that doesn't. I don't need any curseforge points to do it I just want to see the pack thrive and stay cohesive. 😃 |
|
👍 |
|
In regards to the repo and the building side of things; I'd like to propose some changes. I think it might better also to have a Slack or Discord so we can have better conversations / talks about the changes you would like to make. As Soartex is handling most of the building and compiling (Due to our old script) we could port you guys over to the new one which supports more things and auto uploading capabilities to anything you want. Of course this is up to you guys, but just giving my cents from the server / compiling sides. |
|
I think this is a great idea! |
|
So I created a Slack Team, just need to invite you guys. You can email me your email address (Email on my profile here) Or post them depending on your privacy with them. Discord could be an option also / or using Discord for the main app. Depending on your guys preferences? |
|
@artdude543 My email is public here: github@scottkillen.com |
|
I'm planning to keep the vanilla 64x packs updated, so I could easily downsize textures for the 32x pack and keep it updated if needed |
|
@Greenhawk837 Can I get a d/l of 64x JSTR so I can put together the first few modded textures I have for 64x? I won't redistribute. |
|
@artdude543 mine is lesdmark@hotmail.com |
|
@lesdmark I just invited you. |
|
I personally don't feel I'm active enough with the group to be on the slack team. I'm going to try to be more active in the future, although sometimes it's a little difficult for me since I have more of an analytical mind than a creative one, but I do try. I'm going to take some screenshots for the pack later this morning. Going to upload them to our template repo. |
|
Just so everybody knows, the current js-legacy static site runs on github pages. As for the 1.8.x repo, I have created a new repository, and you should all have push access to it. I am a bit busy with my studies, but I will try to help where I can. I setup JSTR back on github so that it could be self sustaining and the contributors could change it to whatever they want it to be. On the money side of things, the credits we get through the curseforge is what allows for the domain to be bought each year. The orginal thought would be a central portal that both the vanilla pack, and modded pack could be accessed through, hence the "js-legacy.net" and not the "jstr.net" site. |
|
👍 |
|
Does anyone know if jenkins could potentially be set up to autobuild the texture packs for us? If so then we'd at least have something for a git commit build, or is a different option better? One of our main problems seems to be a lack of updating the pack on the site. |
|
We should have some kind of automated updating for sure. |
Guy's what is it that we could do to bring the pack back to it's original feel better. If we need to redo our own base to work off of and call it JS Reloaded or Revival or whatnot then I think that is what needs to be done. I hate the way minecraft even looks without the pack anymore but there are definitely some textures in the pack that don't fit. I want to get some excitement generated around the pack again. Maybe get some streamers or youtubers using it again.
The text was updated successfully, but these errors were encountered: