Althezier

Yeah, about the text in msgstringtable.txt I already knew, but thanks for the info. About the reason to delete it, it's simple, there's no reason for it to exist, I won't be using it either. If I could just remove it I would, I mean, it's just about the details lol

Thank you both for the answers, I think I can work with that already!

Hey all! What is the best approach to do what the title says? Example: Suppose there's a command @dosomething, and by default nobody can use it. Now, there's an item called AnItem that when equipped allow me to use the @dosomething command. Again, it ALLOWS me to use the command, it doesn't automatically activate it.

Hey everyone! Does anybody know how to change the part in red of the image below? I want to completely remove it, if possible. I did some research, found a bg_login.tga inside the data.grf, but modifying it didn't work at all. EDIT: I just realized that most of it was an overlap of other parts. However a part of my question still remains, is there a way to remove it? I mean, the functionality plus the cursor change when hovering the area of the dropdown arrow?

That does make sense. Thanks for helping out @Slammer! And if anyone has anything else to share, please do.

I mean, that's exactly my idea. I wanted to set up a server that is pre-renewal, but still with new features like those you described. The thing is, I always get confused about why people, who wants to run a pre-renewal server, look for older clients. Is there any advantage?

Consider my question with a Pre-Renewal server in mind. What is the actual difference between using the latest available client (for all the new features / UI / etc) plus pre-renewal enabled in the server VS a recommended client (older version) plus pre-renewal enabled in the server?

Hi! Thanks for taking some time here and explaining the whole idea, I'll definitely take a loot at it later!! I'll come with a reply after I try.

I know that, but it's not it. The shadows behind the shelf and next to the mirror, I want them to be there. The problem is that exporting and importing the lightmap, those shadows get messed up (like the pics I posted above).

I don't know, I had already tried doing that, but haven't noticed the bug.

Hey, thanks for replying! So, I wanted to remove only the part where I showed in the first post. Is it possible to remove those and keep the others walls shadows? Like these: By exporting and importing I noticed there is a glitch, even without even touching the file in an editor. I export the lightmap, which is like the above, but when I import it's like this: Another example, after importing and before importing: This happens in both 586 and 620 versions of BrowEdit, any idea of how to fix it? Or maybe there is no fix and I can't have shadows on the walls =(

Yea, I thought so. I was hoping there was another way though, but thanks anyway. Exporting, editing and importing does work. EDIT: I was wrong. When I export a lightmap and import it, even after editing, it has a glitch with the walls shadows, they are bugged. Tried in both 586 and 620 versions of BrowEdit. I really don't know what to do anymore.

Hi! I'm running into something that I can't seem to work around this time, to explain it, check the picture below: I wanted to cast shadows at these objects, but I wanted them to stop at the edge, not going further where the yellow arrows points. I wanted the shadows to stop by the red line. Any ideas? Thanks!

Thanks! Downloading this one, I hope it works :3

I didn't test with any other kRO data.grf. Does it really matter the year of the data.grf, apart from the new maps resources? I'm gonna download a 2017 version if that's the problem. I need to use BrowEdit for just a few tweaks in a map or two, and they are old maps. But hey, thanks for testing it out and telling me this data is not working.