Jump to content

Recommended Posts

Posted

Download 'CommandFunc.txt' from the Bottom of this post.

 

Open it, and find the Buttons you want to change the positions of. For this tutorial, I'll be changing the position of 'Attack'

It looks like this:

 

[CmdAttack]
Art=CommandAttack
Buttonpos=3,0

 

Buttonpos=3,0 Means that the Icon is in the position (3, 0) (X, Y)

Change that to what you want. If you don't know the positions, use this.

 

I've changed it to (1, 1)

 

[CmdAttack]
Art=CommandAttack
Buttonpos=1,1

 

Save the text document and open World Editor.

In the Import Manager, import the file, and change its path to

 

Units\CommandFunc.txt

 

 

Tut1.jpg

 

And you're done

 

Results :

 

Tut2.jpg

 

 

Changing the Tooltips and the Hotkeys of the command buttons

 

Download CommandStrings.txt from the bottom of this post.

 

When you open it you'll find a list of the commands, tooltips and hotkeys. For this tutorial, I'll be working with move.

 

[CmdMove]
Tip=|cffffcc00M|rove
Ubertip="Orders your units to move to the target area, while 
ignoring enemy units and attacks. Issuing a move order onto a 
target unit will cause your unit to follow the target."
Hotkey=M

 

Tip' is the Name of the command as it appears in Wc3.

'Ubertip' is the Tooltip.

'Hotkey' is.. the hotkey (Difficult to guess isn't it?)

 

Edit this as you wish.

 

[CmdMove]
Tip=|c0050BBFFR|c000080FFun|r
Ubertip="Commands your units to run to the target point as quickly as possible, and avoiding battle."
Hotkey=R

 

Save the text document and open World Editor.

In the Import Manager, import the file, and change its path to

 

Units\CommandStrings.txt

 

tut2-1.jpg

 

Result: (The hotkey works too.)

tut3.jpg

 

 

Questions and Answers:

Q: Can you Remove Icons completely?

A: No. Not as far as I know.

 

Credits : Romek.

 

CommandFunc.txt

CommandStrings.txt

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • TG Support: https://t.me/buyingproxysup | Channel: https://t.me/buyingproxycom Discord support: #buyingproxy | Server: Join the BuyingProxy Discord Server!  Create your free account here
    • I think you should check the video more carefully you missing something very important 😛      
    • Im responding to an anonymous account with 3 posts, almost no background, and practically zero useful information added to the discussion. On top of that, the topic title is misleading  calling it "Lucera Source Code" gives a completely different impression from what is actually being presented.   I didn’t say anything different. Therefore, I have no clue how his process produces the same desirable result.   And here you are creating drama. Your topic title clearly says "Lucera Source Code," which is not actually the case, or at least that’s how it looked when I first clicked on it, so I don’t think I was completely off. There’s also no significant information about your process like  what difficulties you faced, what tools you used, or anything else meaningful. Yet you still expect others to provide value based on what? I’m not talking about your project itself which, by the way, good job. I’m talking about the topic itself as a source of value for this forum, because right now it doesn’t really offer much in that regard. So regarding the semantics, yes, wording does matter.  
    • You are funny guy! 😄 😄 😄    I was working with Lucera long before “AI apps” became fashionable. This was not something I generated in one day with a prompt. It took me years of work, testing, debugging and fixing broken decompiled code.   Of course a decompiled source is not the original private repository with the original comments, history and developer structure. Nobody said it is the same Git repository. But saying it is only “guesses” is also wrong.   When you decompile, rebuild, fix thousands of compile/runtime issues, restore broken logic, reconnect scripts, fix bad casts, repair database calls, compile it again and run it in-game, at that point it is no longer just a guess.   It becomes a working reconstructed source base!   The important part is not whether it is byte-for-byte identical to the original private source. The important part is that I can now work directly inside the code, change core logic, rebuild scripts, fix bugs and continue development without being locked behind closed binaries.   Does it compile? Yes. Does it run in-game? Yes. Can I modify core systems directly? Yes. Can I continue development independently? Yes.   So call it reconstructed, decompiled, cleaned, restored or whatever name you prefer. The result is still the same: I have a working source environment that gives me control over the lucera2 project.   And that was exactly the goal!   🙂 
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..