BoltBait

JPG is a "lossy" format, even at 100%. There really is no way to do what you want. Why are you forced to export in JPG format?

Well, CodeLab can offer suggestion for everything that was valid as of the last successful compile. So, it is still quite useful. I think you've just stumbled upon an interesting paradox with "out" variables.

Well, in the second example, of adding "int c2;" you can build. In the case of adding a function: void XYCoords(int ix, int iy, out double x, out double y) { x = (double)ix; y = (double)iy; x = zoomScale * (x - centerX); y = zoomScale * (y - centerY); } There's not much that you can do about it except don't type "out" both times, compile, then put them in. Type it in like this: void XYCoords(int ix, int iy, double x, double y) { } Build, then type "out" before both out variables. It works then. Pain in the butt, I know. As I said in a previous post, this situation is a paradox for CodeLab and I'm not sure we could correct something like that.

This can happen if the code hasn't compiled yet. Just press the compile button (F6) after defining the variable.

There was a build error. It was that the out parameter "x" must be set before returning. Paradox.

It may be more complicated than that. When I entered his example, the autocomplete box didn't list "x" in it.

That reproduces for me. Looks like the parameters of the function are not being parsed properly.

I can not get this to fail as you describe. Can you show me the script you're editing and where your cursor is when you type "x ="?

This.

The easiest way is to use File > New and choose clipboard in the list of effects, click Add ... and go from there.

When pasting something that has transparency in it, always paste to a new layer. That is, use Ctrl-Shift-V instead of Ctrl-V.

Check your File > Open Recent menu?

Oh? Why's that? Because of this... My latest shadow plugin crashes previous versions of Paint.NET because of the bug and he runs the Store version.

Paint.NET is not a batch editing tool. Sorry. But, if you open all 45 images, you can lighten one image, then switch to the next image and open the Adjustments > Brightness/Contrast effect and it will have the same settings as before... so that will save you a little time.

At 255 your opacity is set to completely solid... for every other software on the planet. That's why you need to ask at a forum dedicated to the game in question. Obviously, they're using something other than normal opacity to determine how solid their textures are. We don't know what that is... and until we know, we can't help you.

Different games use different methods to modify opacity. Which one do they use?

I recommend asking on a message board dedicated to modding the game in question. This is not a Paint.NET question... until you know exactly what needs to be done.

This is 2 separate issues. Make sure you've selected the proper menu: This works differently than Photoshop. All layers of an image in Paint.NET are the same size. Therefore, if you crop one layer ALL layers are cropped. Hope this helps, BoltBait

CodeLab v5.4 has been released to support this version of Paint.NET. https://forums.getpaint.net/topic/880-codelab-v54-for-advanced-users-released-may-21-2020/?do=findComment&comment=571501 Enjoy. 😎

CodeLab 5.4 Released This is only for Paint.NET 4.2.11+! Small (but important) update today... Changes: ▪ Improved suggested variable names (toe_head2001) ▪ Improvemens in Autocomplete and Intellisense (toe_head2001) ▪ Generate Type Definitions on F12. You can now see definitions inside of libraries. (toe_head2001) ▪ Remember scroll positions (and other things) when switching tabs (toe_head2001) ▪ Rewrite File New Template for up to 2 Scratch Surfaces, also bug fixes and better code (BoltBait) Grab the CodeLab DLL here: https://www.boltbait.com/pdn/CodeLab/ File New Template Improvements: When I completely rewrote the File New Templates in CodeLab 5.0, I was under the assumption that it was OK to use the DST surface as a scratch surface during the calculation of your final results. This is OK under some very narrow circumstances, but generally this should be avoided. (This could cause your effects to have different results when previewing your effect and when clicking OK to finalize your image.) In this release, I have removed this capability and replaced it with a second scratch surface called AUX. So, now you have access to the source surface (SRC) which is your layer before any changes are made, a working surface (WRK) to use as a scratch surface if necessary, a second working surface (AUX) to use if necessary, and of course the destination surface (DST) where you store your final calculated pixels. In previous versions, the blend modes had the top and bottom layers swapped--that's fixed in this build. The code generated should also be easier to understand. (This is the last update before toe_head2001 rewrites the entire compiler section.)

Nope. Sorry. To be fair, Paint.NET did try and warn you that you hadn't saved yet... next time go a little slower, read the messages, click the appropriate buttons... (Yeah, happens to me once in a while too...)

No, sorry, that's just the way Paint.NET works.

When in Paint.NET, pressing Ctrl-N to open a new document, it defaults to the size of the image on the clipboard. Maybe that's what's going on here.

If you're running the store version, you need to put them in a different place: C:\Users\xxxxxx\Documents\paint.net User Files\Effects Hope this helps, BoltBait

Don't do that. I used to think it was ok. Now, I don't. Currently CodeLab allows you do design plugins this way using the File > New templates... I will be correcting this for the next release. Do not use DST as another scratch surface. Stuff doesn't work right when you do this.