Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lightning Trait Changed, Models Generated and General Cleanup #12

Open
wants to merge 6 commits into
base: 1.16.x
Choose a base branch
from

Conversation

XxInvictus
Copy link

Log of changes:

Updated the lightning weapons to call down lightning instead of just doing lightning damage
Updated the model generator Python script and generated all models
Cleaned up a few unnecessary files (including those updated by newer variants or are just no longer required)
Moved the logo file to mod.toml friendly location and updated the Git readme to reference this logo for the title
renamed battlehammer_* textures back to hammer_* after finding out that SpartanWeaponry updated the name but not the resource name
To Do:

Create new Lightning weapon textures
Fix Tooltips, currently the item name and trait is being shown as a resource location
Fix Model generators, currently this is believed to be held back by the IaF bug raised in Issue #4214 in IaF repo
Potentially create Recipe generators, still a little unsure how to do this with items created using SpartanWeaponry API

Kovak and others added 3 commits August 2, 2021 09:48
Log of changes:
- Updated the lightning weapons to call down lightning instead of just doing lightning damage
- Updated the model generator Python script and generated all models
- Cleaned up a few unnecessary files (including those updated by newer variants or are just no longer required)
- Moved the logo file to mod.toml friendly location and updated the Git readme to reference this logo for the title
- renamed battlehammer_* textures back to hammer_* after finding out that SpartanWeaponry updated the name but not the resource name

To Do:
- Create new Lightning weapon textures
- Fix Tooltips, currently the item name and trait is being shown as a resource location
- Fix Model generators, currently this is believed to be held back by the IaF bug raised in Issue #4214 in IaF repo
- Potentially create Recipe generators, still a little unsure how to do this with items created using SpartanWeaponry API
Log of changes:
- deobf of SpartanWeaponry disabled, not required as only public API is used
- Fix item registry
- Rename textures/item to textures/items to be in correct location for models
- standard item, witherbone handle and witherbone pole models are not created by Python script, manually created

See previous commit 9e72edb for "To Do" list
Log of Changes:
- Cleanup in main registry file, moved the colours which are static between all materials to within the Util script and removed the parameters
- Created a Python Lang file generator and created a new Lang file in json format following the weapon naming conventions from IaF
Log of Changes:
- Small change in lang generator and file, change lightning trait description to in-line with IaF wording. Not sure if I should remove the glowing effect, it's not part of IaF it was just a personal touch.
- Fix bow models and generator, there was an item/items mis-naming
@XxInvictus
Copy link
Author

Just because it's been a bit since an update, there are a few things

  1. I have asked Javaraptor if he would be willing to do the lightning weapon textures and he has said he would have a look, just have to wait for him to have time
  2. ObliviousSpartan has expressed that he has addressed the issues with a few items being created in the SpartanWeaponry namespace and the changes will be in the next release, no ETA on when that will be though
  3. IaF has not even acknowledged my bug report for the ClientProxy exception, but that is not critical to release, it just affects generators

@gaesyeah
Copy link

gaesyeah commented Oct 16, 2021

@XxInvictus @Kovak Please look at this: #16

-> There are the lightning weapon textures, made by Samlegamer.

@Kovak
Copy link
Contributor

Kovak commented Oct 21, 2021

hey guys sorry I've been a bit busy with work,

where are we at on this one? is it ready for me to take a look?

@gaesyeah
Copy link

gaesyeah commented Nov 4, 2021

Hi @Kovak, its fine!
The "MK particle editor" is looking good? I loved the idea.


Aparently its not far to become good enough to a public release, but unfortunately @XxInvictus has not been active on github for a while, so i dont know if this great port is dead or not.

And there is another port: minhtet-htoon/SaF2021#1 (unnoficial). But the dev unfortunately dont have time to finish the work

@XxInvictus
Copy link
Author

XxInvictus commented Nov 5, 2021

It is a mix of my work got busier and also the updates stagnated on things outside of my control.

The status hasn't changed since I last updated, below is a summary.

To get it working "good enough" all that is missing is Textures for lightning gear, reached out to Javaraptor a couple of times and he did have interest but was busy.

The other two items there is no change:

  • ObliviousSpartan had said that he had fixed the issue with weapons being created in the SpartanWeaponry namespace when spawned via the API and it was to be included on next update, but an update hasn't been seen to SpartanWeaponry since April. Regardless, the files as they currently sit should be setup in a way that it will still work, it's just not ideal from my perspective in which I would like the code to be consistent throughout
  • IaF still has not acknowledged the bug I raised in their git, but this only affects the plan to auto-gen resources. For now they are manually created and will work as is.

@gaesyeah
Copy link

gaesyeah commented Nov 6, 2021

Hi @XxInvictus . Of course.

I would love to use this mod in 1.16.5. Maybe i can help with something:

#16 (There are all the lightning weapon textures, made by Samlegamer)

And i talked a bit with ObliviousSpartan(DM in CurseForge) about other things a few days ago, i can send a new message about this problem.

@XxInvictus
Copy link
Author

Understandable that textures exist but Javaraptor would be ideal, as he is the one that not only did the textures for SpartanFire originally but he is also the one that does textures for IAF

@gaesyeah
Copy link

gaesyeah commented Nov 6, 2021

Yeah, i understand. But is something wrong to use these textures?(they look really good. Take a look at the lighting dragonsteel ones) I mean, if the main problem is that you dont have the textures and JavaRaptor is busy to make them, why not to use these?

I think it's unfair considering your and Kovak hardwork to make this port becomes real, and a lot of people (also Samlegamer) wants this mod in 1.16.5...I really understand your point but if this reason "can make the port not happen", for me it doesn't make sense.

@denispionicul
Copy link

Yeah i agree, you can use the textures made by samlegamer as a replacement till JavaRaptor does it

@gaesyeah
Copy link

gaesyeah commented Nov 7, 2021

Exactly. And I know that Xxinvictus wants this to be perfect, but its has been almost 4 months...And after all this is a open source minecraft project, please, let the community help you a bit!

@XxInvictus
Copy link
Author

Exactly, it's an open source project, there is nothing stopping either of you contributing. As I said, I have work to focus on. I was just listing where it was up to and the preferred outcome.

@Kovak
Copy link
Contributor

Kovak commented Nov 28, 2021

So it looks like the biggest thing we're waiting on is that update from Spartan Weaponry. We'll definitely make use of Samlegamer's textures.

Renamed and included Lightning weapon textures provided by Samlegamer
@XxInvictus
Copy link
Author

I honestly don't like the odds of Spartan Weaponry being updated with the new API for 1.16.5 I 100% expect ObliviousSpartan will go direct to next updates being 1.17, 1.18 or even 1.19

In the meantime I am going to make the changes now that will allow it to be used, it is just hacky because it means Spartan Fire will be supplying textures in the SpartanWeaponry namespace

@XxInvictus
Copy link
Author

Damn, I was hoping to just include add the other namespace items under the spartanweaponry namespace within spartanfire but that is breaking everything in spartanweaponry's original namespace, all tooltips, names, everything... So that is a negatory...

@XxInvictus
Copy link
Author

The way I see it there are three options:

  1. (The Best Outcome) ObliviousSpartan updates SpartanWeaponry one final time for 1.16.5 with the necessary changes
  2. (The OK Outcome) I remove all references to the broken items and we release an interim version missing all of the below items
  3. (The Messy Outcome) The broken items are created in the SpartanWeaponry namespace within SpartanFire which means all items are included but a LARGE amount will have any number of combination of broken names, tooltips and/or descriptions in both SpartanFire AND SpartanWeaponry items

Broken Items:

  • Boomerang
  • Heavy Crossbow
  • Javelin
  • Throwing Knife
  • Tomahawk

@Samlegamer
Copy link

in fact the following objects should be put in the asset models of spartanweaponry, the others should be put in spartanfire.
sf

1 similar comment
@Samlegamer
Copy link

in fact the following objects should be put in the asset models of spartanweaponry, the others should be put in spartanfire.
sf

@XxInvictus
Copy link
Author

Honestly I just split everything rather than being selective because it was easier to visualise what was outstanding. The ideal situation is it get's updated and they are all in SpartanFire and is really what I am holding out for because it is just too much of a nightmare to have split resources.

@XxInvictus
Copy link
Author

Still no update from Oblivious in my issue over on his repository for SpartanWeaponryApi. I wish I had a direct line but I have not been able to find a contact for him anywhere :(

@Samlegamer
Copy link

I believe that for the moment there is no other choice.

@XxInvictus
Copy link
Author

XxInvictus commented Feb 19, 2022

ObliviousSpartan — 02/16/2022
Hey there. Sorry for not responding to your query on Github. I have been busy with real life, but I have has some time to work on Spartan Weaponry on 1.16.5.
I would've released a fix earlier, but for some stupid reason I wasn't using any form of versioning (a local Git repository) to allow me to revert/branch any changes for the major update I'm working on for the 1.16.5 version. Oops. I've fixed that now so hopefully it will be a bit quicker to release bugfixes without it interfering with doing major mod updates too.
If I don't have time for the mod anymore, I will make it open source, maybe even earlier while I'm still developing it.
I'm currently just dealing with finalizing any changes with the mod for the version 2.2.0 update and balancing the new weapon (Scythe) and the return of my old experimental weapon (Parrying Dagger) too.
Once that's sorted, onwards and upwards straight to 1.18.1!

@Samlegamer
Copy link

The latest rc-2 update fixes the problem

@Samlegamer
Copy link

Scythe Textures :

scythe_dragonbone
scythe_dragonbone_fire
scythe_dragonbone_ice
scythe_dragonbone_lightning

@XxInvictus
Copy link
Author

Apparently Oblivious has updated Spartan Weaponry, unfortunately I am not playing at the moment so I don't have the infrastructure to test on but I am happy if someone wants to branch off mine and finish this off! 😊

1 similar comment
@XxInvictus
Copy link
Author

Apparently Oblivious has updated Spartan Weaponry, unfortunately I am not playing at the moment so I don't have the infrastructure to test on but I am happy if someone wants to branch off mine and finish this off! 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants