[KSP >= 1.3.0] TweakScale - Under Lisias' Management - 2.4.8.8 - 2024-1117

[Krazy1]

Hi @Lisias Having trouble with attachment nodes moving after changing variant. Simple test:

1. place coupla
2. attach FL-T200 on bottom
3. Tweak to 2.5m
4. remove tank... see top bottom nodes are correct... reattach 
5. Change tank to orange/ gray variant
6. remove tank... nodes moved inside tank

If I change the variant first and then resize it, it's OK.

KSP 1.12.5, TS 2.4.7.1 and lots of mods. If you can't reproduce, I'll provide more info.

[Lisias]

19 hours ago, Krazy1 said:

Hi @Lisias Having trouble with attachment nodes moving after changing variant. Simple test:

1. place coupla
2. attach FL-T200 on bottom
3. Tweak to 2.5m
4. remove tank... see top bottom nodes are correct... reattach 
5. Change tank to orange/ gray variant
6. remove tank... nodes moved inside tank

If I change the variant first and then resize it, it's OK.

KSP 1.12.5, TS 2.4.7.1 and lots of mods. If you can't reproduce, I'll provide more info.

I confirm the problem on my 1.12.5 Acceptance Test Bed. I'm not sure yet if this is a TweakScale bug, a KPS-Recall mishap or a new problem on KSP 1.12.x [it's insidious bug on TweakScale] but I will post my findings on the https://github.com/TweakScale/TweakScale/issues/307 .

Thanks for the report! Cheers!

— — 

(I felt a disturbance in the Force - as thousands of Parts suddenly had their attachment points reset after scaled…)

Edited July 28, 2023 by Lisias
it's a bug on TweakScale

[Darael]

Hi. I'm sure you're extremely busy, but I was wondering if you had a timescale on the "why we ditched CKAN" rant? It's been listed as "coming soon" for a while now, and while I can see from the B9 PWings situation that you are upset with how that was handled, the "on CKAN" section pointed to by TweakScale's alert popup says "the reasons can be found here" and pointing at… a placeholder page. Not exactly the most user-friendly experience, if you catch my drift.

[Krakatoa]

It seems really weird [snip]  to have a link to your "/blogs/rants" personal webpage on the pop up anyways. Why don't you just request removal for all your mods from CKAN and be done with it, if you've actually ditched it?

Edited August 2, 2023 by Snark
Redacted by moderator

[Poodmund]

https://ksp.lisias.net/blogs/rants/on-CKAN/b9-pwings-fork/part-2

Can you please remove my name from your loveing website.

[Lisias]

I'm on the uncomfortable need to explain again what I think should be obvious by this time:

CKAN IS NOT SUPPORTED BY ME ANYMORE,

I'm not going to diagnose, again, any problems related to it.

The reasons were explained previously on the following post:

and I quote myself:

On 7/4/2023 at 5:27 AM, Lisias said:

Unfortunately, yes. I do not support CKAN anymore.

This doesn't means you are on your own, TweakScale IS SUPPORTED, so any problems you get while using TS will be diagnosed and fixed.

But I will not handle problems created by CKAN itself, as that horrible breakage that happens when CKAN mess up things and renders TweakScale unusable (most of them are caused by KSP itself, but yet…). These problems are time consuming to diagnose and fix, and I'm barely have time to support my own add'ons these days, I need to adjust my workload somehow.

So, if TweakScale was working and then you ran CKAN and it stopped working, this is a CKAN issue and you should ask help to the CKAN guys. I can help if I have time available, but absolutely no promises I will ever be able to respond a post about.

If TweakScale is misbehaving, or is issuing Warnings or Errors about Parts, then this is something related to TweakScale and I will gladly help you on whatever I can to have your problem fixed.

As a Rule of Thumb

• if you managed to reach the Main Menu and only there TweakScale starts to yell, it's a problem related to TweakScale. Please report and I fill fix it.
• if TweakScale yells before you reach Main Menu, then this is 99.95% of the time a problem unrelated to TweakScale, and I suggest you reach first the CKAN guys for triage - if they diagnose a problem on TweakScale itself (there're still that 0.05% of chance), I will fix it.

Cheers!

Additional information can be found here:

Thank you for your understanding.

Edited August 2, 2023 by Lisias
tyops and better formatting

[Wyleg]

This does not answer any of the questions above tbh.

[Lisias]

1 hour ago, Wyleg said:

This does not answer any of the questions above tbh.

This thread is about support for TweakScale. If you want something else, you will need to find it somewhere else.

[Wyleg]

Ok, let me rephrase the question that bothers me.

 

Why TweakScale shows a message on loading KSP which says that CKAN is not supported and the suggested link to get more details on that leads nowhere?

[Lisias]

26 minutes ago, Wyleg said:

Ok, let me rephrase the question that bothers me.

Why TweakScale shows a message on loading KSP which says that CKAN is not supported and the suggested link to get more details on that leads nowhere?

Because CKAN is not supported! I will not support CKAN anymore, I will not diagnose problems related to CKAN anymore. I can't be more clear than that.

The link is sending you to "nowhere" because I was told that issues unrelated to this Forum should remain out of this Forum. All the possible discussion about this issue already happened here, and the thread was closed on a clear indication that this subject is finished on this Forum.

Do you want to further discuss this problem on a GitHub Discussion? It appears to a more adequate place, instead on insisting on cluttering this thread with issues related to CKAN.

Or perhaps Reddit?

Edited August 2, 2023 by Lisias

[Wyleg]

29 minutes ago, Lisias said:

The link is sending you to "nowhere" because I was told that issues unrelated to this Forum should remain out of this Forum. All the possible discussion about this issue already happened here, and the thread was closed on a clear indication that this subject is finished on this Forum.

To be clear, I thought that the link leads nowhere because I thought it still features the "coming soon" we are talking about, but now, as you quietly filled the page without acknowledging anyone that the issue is no more, this problem seems to be fixed.

Once again, this was an issue related to TS, as it was TS that produces the message with the now fixed link, I can't think of more adequate place to discuss a TweakScale related issue rather than here.

The question why TweakScale users has to deal with the piece of unwanted "you vs CKAN" drama every time they boot up KSP , when you can just delist your mod from CKAN and solve the problem with support for everyone once and for all, is still left unanswered. But I see that you will avoid answering that no matter what, so i bug out. Peace.

Edited August 2, 2023 by Wyleg

[Lisias]

8 hours ago, Wyleg said:

To be clear, I thought that the link leads nowhere because I thought it still features the "coming soon" we are talking about, but now, as you quietly filled the page without acknowledging anyone that the issue is no more, this problem seems to be fixed.

A questioning that happened 19 hours ago at the moment of this posting (what means that I responded pretty quickly, IMHO). And, again, a subject unrelated to this Forum (I was adverted by Moderation once by doing something similar) and so, without the formal or implied need to be announced here.

Additionally, none of your following posts mentioned this problem:

10 hours ago, Wyleg said:

This does not answer any of the questions above tbh.

and

8 hours ago, Wyleg said:

Ok, let me rephrase the question that bothers me.

Why TweakScale shows a message on loading KSP which says that CKAN is not supported and the suggested link to get more details on that leads nowhere?

So I didn't found a reason to mention it to you neither.

If you want an answer for a specific question, you need to formulate that specific question otherwise people will not answer it!!!

 

8 hours ago, Wyleg said:

Once again, this was an issue related to TS, as it was TS that produces the message with the now fixed link, I can't think of more adequate place to discuss a TweakScale related issue rather than here.

The questioning about the reason for not supporting CKAN anymore, I agree (besides this being already answered ad nauseaum). Whatever issues you would find on unrelated sites about unrelated subjects for this Forum, I disagree.

 

8 hours ago, Wyleg said:

The question why TweakScale users has to deal with the piece of unwanted "you vs CKAN" drama every time they boot up KSP , when you can just delist your mod from CKAN and solve the problem with support for everyone once and for all, is still left unanswered. But I see that you will avoid answering that no matter what, so i bug out. Peace.

TweakScale was being distributed on CKAN before I started to maintain it, and users had questioned me more than once if I was going to pull out it from CKAN, asking me not to do it. I don't have problems with what CKAN was meant to do, I have very serious problems with what CKAN's maintainers were doing instead.

(and, again, if you want specific answers, you need to do proper questionings)

And, I want to be perfectly clear, I'm not the only one.

May the Road rise with you.

 

— — POST EDIT — — 

And just to make something perfectly clear: I WAS A FIERCE CKAN SUPPORTER in the past:

On 7/29/2019 at 1:21 PM, Lisias said:

CKAN makes a beautiful job on archiving every Add'On they are allowed on the Archive.org. I don't care too much about the installer (I don't use it), but this is the reason I make a point on supporting CKAN how I can: they are preserving the Add'Ons to be available in the future, no matter what.  The link is https://archive.org/download/TweakScale-v2.4.3.1 and yeah, it's fine too. I just checked.

Besides acknowledging its flaws pretty early:

Quote

I'm not sure CKAN is for everybody. At least until now. CKAN lacks that "Chain of Thrust", so updated mods still can break thinks and, worse, corrupting save games. Some mechanisms to rollback also the save-game changes due the update are needed.

It took some serious 4 to 5 years [snip]  until I finally got fed up. I really hope this would tell something about what happened here.

Edited August 2, 2023 by Snark
Redacted by moderator

[Snark]

Some content has been redacted and/or removed.  Please avoid accusations and personal remarks.  Thank you.

[Lisias]

NOTAM

TweakScale 2.5.0.60 **BETA** is on the wild, and available on github only.

Some changes, fixes and refactorings were made since the last one, and since the change log is getting somewhat extensive, i will just link issue #42 where I'm tracking the Beta releases. And there's also the CHANGE LOG.

Known Issues: The engine's plumes are not being scaled correctly…  SmokeScreen and Waterfall, however, may work fine.

HOWEVER… The Beta is still a very new codebase, and unexpected things may still happen. Use it with caution.

People in need to migrate from older Craft files and Savegames where the ScaleTypes for some parts had changed over time, as well people that uses All Tweak and got themselves some new TweakScale patching for parts that didn't had them before, will need to install TweakScale Beta 2.5.0.60 to salvage them. Load and Save, and you are done.

Savegames and craft files will be backwards compatible to the current mainstream, 2.4.7.x series.

Keeping 2.5.0.x BETA for ongoing gaming, however, may be hazardous. As I said, it's a ongoing development branch and some implementation decisions may fireback unexpectedly. Unless you are willing to help me on beta testing the thing (and, so, no playing your valuable savegames on it), I recommend to roll back to the current Release 2.4.7.x after converting your assets.

What I expect to be the new 2.4.7.3 release is, right now, work in progress.   I will play with 2.5.0.60 for some time myself before pushing 2.4.7.3, as I want to be sure about some structural changes I made due a (yet another) problem I recently diagnosed on KSP.

Cheers.

— — POST EDIT 2023-0805 (one day later) — — 

I just realised I had uploaded the wrong binaries into GitHub. (sigh). Just fixed it.

Edited August 5, 2023 by Lisias
POST EDIT

[The epic chicken]

hello there, when loading up the game i'm getting this error message, i'm not too sure what's causing it though

https://ibb.co/QFZ2h4k

https://www.mediafire.com/file/qb6w51c5kd0q2k7/KSP.log/file

https://www.mediafire.com/file/fp55l7lkewuayor/Player.log/file

thanks

Edited August 4, 2023 by The epic chicken

[Lisias]

3 hours ago, The epic chicken said:

hello there, when loading up the game i'm getting this error message, i'm not too sure what's causing it though

https://ibb.co/QFZ2h4k

Yeah, you got a Houston. Sorry for that.

What's happening is that some 3rd partied had wrote less than ideal patches in the past, but it also happens when you install something wrongly. And in your case, you have both!

For example, the "WirbelwindFlakTurret" is installed both on "SM_Armory/Parts" and on "Parts" what's clearly an error.

[LOG 22:11:53.647] Applying update 999_KSP-Recall/patches/attached-on-editor/@PART[*]:HAS[!MODULE[ProceduralPart],!MODULE[WingProcedural],!MODULE[ModuleAsteroid],!MODULE[ModuleComet],!MODULE[KerbalEVA]]:LAST[KSPRECALL-ATTACHED-ON-EDITOR]:NEEDS[TweakScale] to Parts/FlakTurret/FlakTurret.cfg/PART[WirbelwindFlakTurret]
[LOG 22:11:53.929] Applying update 999_KSP-Recall/patches/attached-on-editor/@PART[*]:HAS[!MODULE[ProceduralPart],!MODULE[WingProcedural],!MODULE[ModuleAsteroid],!MODULE[ModuleComet],!MODULE[KerbalEVA]]:LAST[KSPRECALL-ATTACHED-ON-EDITOR]:NEEDS[TweakScale] to SM_Armory/Parts/Config/FlakTurret.cfg/PART[WirbelwindFlakTurret]

Delete the "Parts" directory on your GameData and most of the problems will go away.

The other problems you will fix by saving this file on your GameData (I suggest saving it on a folder called GameData/__LOCAL/TweakScale/WorkArounds to make easier to keep track of it):

https://raw.githubusercontent.com/TweakScale/TweakScale/master/Extras/TweakScale/Workarounds/SMI_AddOns.cfg

I think that these two measures should fix your rig, but if I left something lingering, publish a new KSP.log and I will inspect it!

Cheers!

[Lisias]

ANNOUNCE

Release 2.4.7.3 is available for downloading, with the following changes:

• Backport the Unity's Update Life Cycle fix from Aviation Lights #4
  • Hopefully preventing some excrementsstorm on users running KSP on Hybrid CPUs (P-Cores, E-Cores, that crap).
• Closes Issues:
  • #308 Insidious NRE on changing scenes
  • #307 Attachment Points are not being scaled (or being reset) after changing the Variant

 

Know Issues

• There's a long standing issue on TweakScale about scaling ModuleEnginesFX's plumes - some engines' plumes is just not scaled, while others scaled pretty badly. It's something that never worked right on TweakScale, and it will only be really fixed on TweakScale 2.5 (when this thing goes gold)
  • The best workaround (and also the reason I'm dragging my feet on this) is to use SmokeScreen or Waterfall.
    • For SmokeScreen, you need:
      • SmokeScreen itself.
      • Real Plumes (to enable SmokeScreen on Stock parts)
        • Additional Part Sets and Add'Ons may need specialised support not included on Real Plumes.
    • For Waterfall, you need:
      • Waterfall itself.
      • StockWaterfallEffects (to enable SmokeScreen on Stock parts)
        • Additional Part Sets and Add'Ons may need specialised support not included on Real Plumes.
  • See Issue #27

Disclaimer

By last, but not the least...

Spoiler

No Module Manager was harmed during the development of TweakScale.

 

This Release will be published using the following Schedule:

• GitHub, reaching first manual installers and users of KSP-AVC. Right now.
• CurseForge. Right Now.
• SpaceDock. Right Now.

Edited August 12, 2023 by Lisias
All your Distribution Channels are belong to us!

[Astra Infinitum]

On 8/4/2023 at 1:12 AM, Lisias said:

NOTAM

TweakScale 2.5.0.60 **BETA** is on the wild, and available on github only.

Some changes, fixes and refactorings were made since the last one, and since the change log is getting somewhat extensive, i will just link issue #42 where I'm tracking the Beta releases. And there's also the CHANGE LOG.

Known Issues: The engine's plumes are not being scaled correctly…  SmokeScreen and Waterfall, however, may work fine.

HOWEVER… The Beta is still a very new codebase, and unexpected things may still happen. Use it with caution.

People in need to migrate from older Craft files and Savegames where the ScaleTypes for some parts had changed over time, as well people that uses All Tweak and got themselves some new TweakScale patching for parts that didn't had them before, will need to install TweakScale Beta 2.5.0.60 to salvage them. Load and Save, and you are done.

Savegames and craft files will be backwards compatible to the current mainstream, 2.4.7.x series.

Keeping 2.5.0.x BETA for ongoing gaming, however, may be hazardous. As I said, it's a ongoing development branch and some implementation decisions may fireback unexpectedly. Unless you are willing to help me on beta testing the thing (and, so, no playing your valuable savegames on it), I recommend to roll back to the current Release 2.4.7.x after converting your assets.

What I expect to be the new 2.4.7.3 release is, right now, work in progress.   I will play with 2.5.0.60 for some time myself before pushing 2.4.7.3, as I want to be sure about some structural changes I made due a (yet another) problem I recently diagnosed on KSP.

Cheers.

— — POST EDIT 2023-0805 (one day later) — — 

I just realised I had uploaded the wrong binaries into GitHub. (sigh). Just fixed it.

Did you ever get around to checking out the issue with SAF Fairings? I totally forgot about sending you the config i was using. I will do it shortly

[The epic chicken]

20 hours ago, Lisias said:

Yeah, you got a Houston. Sorry for that.

What's happening is that some 3rd partied had wrote less than ideal patches in the past, but it also happens when you install something wrongly. And in your case, you have both!

For example, the "WirbelwindFlakTurret" is installed both on "SM_Armory/Parts" and on "Parts" what's clearly an error.

[LOG 22:11:53.647] Applying update 999_KSP-Recall/patches/attached-on-editor/@PART[*]:HAS[!MODULE[ProceduralPart],!MODULE[WingProcedural],!MODULE[ModuleAsteroid],!MODULE[ModuleComet],!MODULE[KerbalEVA]]:LAST[KSPRECALL-ATTACHED-ON-EDITOR]:NEEDS[TweakScale] to Parts/FlakTurret/FlakTurret.cfg/PART[WirbelwindFlakTurret]
[LOG 22:11:53.929] Applying update 999_KSP-Recall/patches/attached-on-editor/@PART[*]:HAS[!MODULE[ProceduralPart],!MODULE[WingProcedural],!MODULE[ModuleAsteroid],!MODULE[ModuleComet],!MODULE[KerbalEVA]]:LAST[KSPRECALL-ATTACHED-ON-EDITOR]:NEEDS[TweakScale] to SM_Armory/Parts/Config/FlakTurret.cfg/PART[WirbelwindFlakTurret]

Delete the "Parts" directory on your GameData and most of the problems will go away.

The other problems you will fix by saving this file on your GameData (I suggest saving it on a folder called GameData/__LOCAL/TweakScale/WorkArounds to make easier to keep track of it):

https://raw.githubusercontent.com/TweakScale/TweakScale/master/Extras/TweakScale/Workarounds/SMI_AddOns.cfg

I think that these two measures should fix your rig, but if I left something lingering, publish a new KSP.log and I will inspect it!

Cheers!

Hello, I got another Houston, I've removed the duplicate install, I wasn't wasn't able to figure out how to download the workaround file 

I've attached the ksp log and a screenshot 

https://www.mediafire.com/file/vpwfhlbws1m05cm/ksp_log.zip/file

https://ibb.co/Tt0HVLy

Could you help me find the cause for the error

Thanks

[Lisias]

6 hours ago, Astra Infinitum said:

Did you ever get around to checking out the issue with SAF Fairings? I totally forgot about sending you the config i was using. I will do it shortly

Dude, I need to confess… I don't even remember the issue. Sorry. 

Do you remember if I created a github issue for it somewhere? Probably on one of the Companions...

 

1 hour ago, The epic chicken said:

Hello, I got another Houston, I've removed the duplicate install, I wasn't wasn't able to figure out how to download the workaround file 

First and for all, take a deep breath. I ask you to remember that we all make mistakes, and this includes me - most of the Warnings from TweakScale I had cooked not only due the support requests, but because I did the mistake myself more than once.

That said, what happened is that you installed SM_AFVs twice, with one copy inside the other!

You did something like:

KSP
	[GameData]
		[SM_AFVs]
			[Parts]
				Part1.cfg
				yada yada yada
			[Patches]
				yada yada yada
			[SM_AFVs]
				[Parts]
					Part1.cfg
					yada yada yada
				[Patches]
					yada yada yada

So everything related to SM_AFVs is duplicated on your rig, including the TweakScale patches!  

I suggest you to completely remove the folder SM_AFVs from your GameData and then reinstall SM_AFVs from scratch - only once, this time! 

Cheers!

Edited August 5, 2023 by Lisias
Hit 'save" too soon.

[The epic chicken]

9 hours ago, Lisias said:

Dude, I need to confess… I don't even remember the issue. Sorry. 

Do you remember if I created a github issue for it somewhere? Probably on one of the Companions...

 

First and for all, take a deep breath. I ask you to remember that we all make mistakes, and this includes me - most of the Warnings from TweakScale I had cooked not only due the support requests, but because I did the mistake myself more than once.

That said, what happened is that you installed SM_AFVs twice, with one copy inside the other!

You did something like:

KSP
	[GameData]
		[SM_AFVs]
			[Parts]
				Part1.cfg
				yada yada yada
			[Patches]
				yada yada yada
			[SM_AFVs]
				[Parts]
					Part1.cfg
					yada yada yada
				[Patches]
					yada yada yada

So everything related to SM_AFVs is duplicated on your rig, including the TweakScale patches!  

I suggest you to completely remove the folder SM_AFVs from your GameData and then reinstall SM_AFVs from scratch - only once, this time! 

Cheers!

Ah, I'll try removing the duplicate one then

[The epic chicken]

I seem to have fixed my game, I'm not getting any errors anymore, thank you for helping me with fixing the errors

 

[Project2004]

I have been trying to fix this issue for a bit now, however I can't find the root of the issue.

https://drive.google.com/file/d/1-9a8ZUiDNEzBWR_qDzy0cHlN63vAnuIO/view?usp=drive_link

Could anybody help me with this?

Thanks.

[Lisias]

7 hours ago, Project2004 said:

I have been trying to fix this issue for a bit now, however I can't find the root of the issue.

https://drive.google.com/file/d/1-9a8ZUiDNEzBWR_qDzy0cHlN63vAnuIO/view?usp=drive_link

Could anybody help me with this?

Thanks.

Without a description of the problem, it's usually hard to diagnose something. But you got luck this time, the problem is pretty obvious and a old "friend":

[ERR 23:19:04.786] AssemblyLoader: Exception loading 'ScrapYard_ContractConfigurator': System.Reflection.ReflectionTypeLoadException: Exception of typ
  at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool)
  at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0
  at AssemblyLoader.LoadAssemblies () [0x000e6] in <4b449f2841f84227adfaad3149c8fdba>:0

Additional information about this exception:

 System.IO.FileNotFoundException: Could not load file or assembly 'ContractConfigurator, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one
File name: 'ContractConfigurator, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'

 System.IO.FileNotFoundException: Could not load file or assembly 'ContractConfigurator, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one
File name: 'ContractConfigurator, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'

There's a DLL on ScrapYard that needs Contract Configurator (surprisingly  the DLL is called ScrapYard_ContractConfigurator). Buy you don't have Contract Configurator installed, and so this situation triggered a nasty and insidious bug on KSP on a thingy called "Assembly Loader/Resolver" (just the thing that we need in order to have our DLLs loaded and made its Assembly assessible…). From this point, everything else that needs to load a DLL or needs to use a thing called "Reflection" start to bork relentlessly, and TweakScale and the Companions make heavy use of that.

You have two options to solve this problem:

1. Install Contract Configurator
2. Manually delete the file D:\Steam\steamapps\common\Kerbal Space Program\GameData\ScrapYard\Plugins\ScrapYard_ContractConfigurator.dll from your game.

By doing any of these, you will get your rig fixed.

Cheers!

P.S.: In time, this is a problem on CKAN, not TweakScale. I could help you this time because I have some free time now in the morning, but when I'm busy, I will prioritise TweakScale issues by obvious reasons.

[LOG 23:19:22.047] [KSPe.Light.TweakScale] Version 2.5.2.0 /L for TweakScale. **UNSUPPORTED** due CKAN
[LOG 23:19:22.079] [TweakScale] Version 2.4.7.3 /L

As a rule of thumb, if the thing was working, then you ran CKAN, and it stopped working, it's a CKAN issue, and you should ask for help on CKAN thread as there's something obviously wrong on CKAN or in its database (as they are installing things without the needed dependencies, breaking the game due that Assembly Loader/Resolver crap).

[Poodmund]

Well... if ScrapYard requires Contract Configurator as a dependency (which the above issue would suggest) then it would have been helpful if Zerokerbal could have stated as such on the NetKAN metadata when they last updated it in January.  [snip]

https://github.com/KSP-CKAN/NetKAN/commit/e058d3de5db4c7215dc3dee4bae12720bd7cc9d2

Edited August 24, 2023 by Snark
Redacted by moderator