Jump to content

Which class handles the rendering of a tooltip?


Tavi007

Recommended Posts

Hello,

 

I want to display some text in the same fashion as tooltips, which is why I'm searching for the corresponding vanilla class (I do not want to create a tooltip. I just want to display a text with the same background starting from a given (x,y)-position). However I was not able to find it so far and I'm hoping, that someone knows, where I have to look.

So far I searched in the package minecraft.client.gui or minecraft.client.renderer, but they are huge and I hope, that I don't have to check every file...

Link to comment
Share on other sites

I can't look into the code right now, but I think you can search the renderToolTip function inside a ContainerScreen and see what that function does. From there you should be able to figure out how to render your own tooltip. By the way, if you want to render it inside a screen, just use the renderToolTip or override it to do what you want it to do

Don't blame me if i always ask for your help. I just want to learn to be better :)

Link to comment
Share on other sites

That helped already a lot. Thank you!

 

I found the renderToolTip function in the Screen-class, but I'm using func_243308_b (which will call renderTooTip later on) instead, because all I really need is to define a list of ITextComponents.

Now I want to display my list all the time (when I'm ingame) and not only when I'm looking at a container, but Minecraft#currentScreen is null, when the player is not looking at an inventory. So how can I draw directly on the game screen like the hunger bar?

 

PS: I'm using RenderGameOverlayEvent, which should be the correct one, I think.

Edited by Tavi007
Link to comment
Share on other sites

I believe you should look at how the Hotbar works to find out how to render a Screen constantly. The first thing I can think of is to not make the Screen a ContainerScreen, because of course that will be bind to a Container, which is something as far as I understand you don't need

Don't blame me if i always ask for your help. I just want to learn to be better :)

Link to comment
Share on other sites

4 minutes ago, Tavi007 said:

PS: I'm using RenderGameOverlayEvent, which should be the correct one, I think.

It is correct yes, just don't subscribe to that event. Use the RenderGameOverlayEvent.Pre or Post. Take a look at the IngameGui class to see how vanilla draws hotbar, health and hunger bars etc...

Edited by Beethoven92

Check out the port of the BetterEnd fabric mod (WIP): https://www.curseforge.com/minecraft/mc-mods/betterend-forge-port

Link to comment
Share on other sites

Thanks for your answeres.

 

Reading all that half obfuscated code is hurting my brain. Is the code in IngameGui (or Screen) less obfuscated in the newer forge versions? Otherwise this will be a lot of pain...

 

Anyway please help me understanding the class. Im currently looking at the code, that renders scoreboards and tooltips. To render scoreboards the function AbstractGui#func_238467_a_ is used (see lines 674-688 in IngameGui), while for tooltips AbstractGui#func_238462_a_ is used (see lines 173-180 in Screen) + some RenderSystem stuff. In both cases I don't understand the AbstractGui functions, because they are completly obfuscated.

 

Quote

It is correct yes, just don't subscribe to that event. Use the RenderGameOverlayEvent.Pre or Post.

Why shouldn't I subscribe to the event? I though, that it is necessary, because otherwise my code would never be called.

 

By the way here is my repository (or rather my RenderEvent class)

https://github.com/Tavi007/ElementalCombat/blob/master/src/main/java/Tavi007/ElementalCombat/events/RenderEvents.java

Edited by Tavi007
Link to comment
Share on other sites

48 minutes ago, Tavi007 said:

Why shouldn't I subscribe to the event? I though, that it is necessary, because otherwise my code would never be called.

Thats why i said to subscribe to Post or Pre, it depends on what you want to achieve...usually you use the Post event to add elements to the hud while leaving vanilla stuff untouched.

So if i understand correctly you want to render some information on the screen in a fixed position, and you want them to render in the same graphic style as the tooltip in containers, right? Then apply the code that renders tooltips in your event handler...to do so look at how the tooltips are rendered in the method Screen#renderTooltip, as said before

Check out the port of the BetterEnd fabric mod (WIP): https://www.curseforge.com/minecraft/mc-mods/betterend-forge-port

Link to comment
Share on other sites

Quote

Thats why i said to subscribe to Post or Pre, it depends on what you want to achieve...usually you use the Post event to add elements to the hud while leaving vanilla stuff untouched.

Ah, I just missunderstood you. This does make much more sense.

 

Quote

So if i understand correctly you want to render some information on the screen in a fixed position, and you want them to render in the same graphic style as the tooltip in containers, right? Then apply the code that renders tooltips in your event handler...to do so look at how the tooltips are rendered in the method Screen#renderTooltip, as said before

So basically I'll have to copy and paste the code and adjust it for my case. Seems like a lot of trial and error, but if it works in the end, I'll be happy.

Link to comment
Share on other sites

Just now, Tavi007 said:

So basically I'll have to copy and paste the code and adjust it for my case. Seems like a lot of trial and error, but if it works in the end, I'll be happy.

Its a lot better if you actually try to understand the code before copying it, because you will avoid so many head aches when you have to modify it later

Check out the port of the BetterEnd fabric mod (WIP): https://www.curseforge.com/minecraft/mc-mods/betterend-forge-port

Link to comment
Share on other sites

2 hours ago, Tavi007 said:

Reading all that half obfuscated code is hurting my brain. Is the code in IngameGui (or Screen) less obfuscated in the newer forge versions? Otherwise this will be a lot of pain...

Local variables are never given "deobfuscated" names.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

Thanks to your help I got it working :)

I read the code and got an idea, what each variable does and then confirmed my assumption by playing around with the value. This way I deobfuscated most of them myself. For anyone wondering here is the important code:

@SubscribeEvent
	public static void displayDefenseData(RenderGameOverlayEvent.Post event)
	{
		if(Configuration.enabled()) {
			// see Screen#renderToolTips in client.gui.screen
			Minecraft mc = Minecraft.getInstance();
			if(mc.player != null) {
				DefenseData defData = ElementalCombatAPI.getDefenseData(mc.player);
				if (!defData.isEmpty()) {
					HashMap<String, Integer> styleMap = defData.getStyleFactor();
					HashMap<String, Integer> elementMap = defData.getElementFactor();

					List<ITextComponent> list = new ArrayList<ITextComponent>();
					list.add(new StringTextComponent("Defense:"));
					list.addAll(toDisplayText(styleMap));
					list.addAll(toDisplayText(elementMap));

					if (!list.isEmpty()) {
						MatrixStack matrixStack = event.getMatrixStack();
						float scale = (float) Configuration.scale();
						matrixStack.scale(scale, scale, scale);

						List<? extends IReorderingProcessor> orderedList = Lists.transform(list, ITextComponent::func_241878_f);
						// computes the width of the widest line.
						int listWidth = 0;
						for(IReorderingProcessor ireorderingprocessor : orderedList) {
							int textWidth = mc.fontRenderer.func_243245_a(ireorderingprocessor);
							listWidth = Math.max(textWidth, listWidth);
						}

						// computes the height of the list
						int listHeight = 8;
						if (orderedList.size() > 1) {
							listHeight += 2 + (orderedList.size() - 1) * (mc.fontRenderer.FONT_HEIGHT+1);
						}

						// moves the coords so the text and box appear correct
						int posX = 12;
						int posY = 12;
						if(!Configuration.isTop()) {
							int screenHeight = event.getWindow().getScaledHeight();
							posY = Math.max(12, screenHeight - listHeight - 12);
						}
						if(!Configuration.isLeft()) {
							int screenWidth = event.getWindow().getScaledWidth();
							posX = Math.max(12, screenWidth - listWidth - 12);
						}

						// draw background box
						matrixStack.push();
						int l = -267386864;
						int i1 = 1347420415;
						int j1 = 1344798847;
						int k1 = 400;
						Tessellator tessellator = Tessellator.getInstance();
						BufferBuilder bufferbuilder = tessellator.getBuffer();
						bufferbuilder.begin(7, DefaultVertexFormats.POSITION_COLOR);
						Matrix4f matrix4f = matrixStack.getLast().getMatrix();
						func_238462_a_(matrix4f, bufferbuilder, posX - 3, posY - 4, posX + listWidth + 3, posY - 3, 400, -267386864, -267386864);
						func_238462_a_(matrix4f, bufferbuilder, posX - 3, posY + listHeight + 3, posX + listWidth + 3, posY + listHeight + 4, 400, -267386864, -267386864);
						func_238462_a_(matrix4f, bufferbuilder, posX - 3, posY - 3, posX + listWidth + 3, posY + listHeight + 3, 400, -267386864, -267386864);
						func_238462_a_(matrix4f, bufferbuilder, posX - 4, posY - 3, posX - 3, posY + listHeight + 3, 400, -267386864, -267386864);
						func_238462_a_(matrix4f, bufferbuilder, posX + listWidth + 3, posY - 3, posX + listWidth + 4, posY + listHeight + 3, 400, -267386864, -267386864);
						func_238462_a_(matrix4f, bufferbuilder, posX - 3, posY - 3 + 1, posX - 3 + 1, posY + listHeight + 3 - 1, 400, 1347420415, 1344798847);
						func_238462_a_(matrix4f, bufferbuilder, posX + listWidth + 2, posY - 3 + 1, posX + listWidth + 3, posY + listHeight + 3 - 1, 400, 1347420415, 1344798847);
						func_238462_a_(matrix4f, bufferbuilder, posX - 3, posY - 3, posX + listWidth + 3, posY - 3 + 1, 400, 1347420415, 1347420415);
						func_238462_a_(matrix4f, bufferbuilder, posX - 3, posY + listHeight + 2, posX + listWidth + 3, posY + listHeight + 3, 400, 1344798847, 1344798847);
						RenderSystem.enableDepthTest();
						RenderSystem.disableTexture();
						RenderSystem.enableBlend();
						RenderSystem.defaultBlendFunc();
						RenderSystem.shadeModel(7425);
						bufferbuilder.finishDrawing();
						WorldVertexBufferUploader.draw(bufferbuilder);
						RenderSystem.shadeModel(7424);
						RenderSystem.disableBlend();
						RenderSystem.enableTexture();
						IRenderTypeBuffer.Impl irendertypebuffer$impl = IRenderTypeBuffer.getImpl(Tessellator.getInstance().getBuffer());
						matrixStack.translate(0.0D, 0.0D, 400.0D);

						// write the list on top of the background
						for(int i = 0; i < orderedList.size(); ++i) {
							IReorderingProcessor ireorderingprocessor1 = orderedList.get(i);
							if (ireorderingprocessor1 != null) {
								mc.fontRenderer.func_238416_a_(ireorderingprocessor1, (float)posX, (float)posY, -1, Configuration.textShadow(), matrix4f, irendertypebuffer$impl, false, 0, 15728880);
							}
							// first line is caption. add a little bit space to the next line
							if (i == 0) {
								posY += 2;
							}
							//next line
							posY += 10;
						}
						irendertypebuffer$impl.finish();
						matrixStack.pop();
					}
				}
			}
		}
	}

 

Now I have one last thing, that is bugging me and I don't know what the cause of it is. When my defenseData gets rendered the toolbar gets slightly darker. I made some screenshots, that hopefully explains what I mean.

without defenseData:

withoutDefenseData.png.024f746c181d96fff550e813351f3d0e.png

with defenseData:
withDefenseData.png.bd69a22c50c47ad3627808fda2d48e9f.png

 

Do you know or have an idea, why this happens?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
    • When I came across the 'Exit Code: I got a 1 error in my Minecraft mods, so I decided to figure out what was wrong. First, I took a look at the logs. In the mods folder (usually where you'd find logs or crash reports), I found the latest.log file or the corresponding crash report. I read it through carefully, looking for any lines with errors or warnings. Then I checked the Minecraft Forge support site, where you can often find info on what causes errors and how to fix them. I then disabled half of my mods and tried running the game. If the error disappeared, it meant that the problem was with the disabled mod. I repeated this several times to find the problem mod.
    • I have no idea - switch to a pre-configured modpack and use it as working base    
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.