Jump to content

Recommended Posts

Posted

The design needs to be 265x265 pixel and has to be named emblem.bmp (24bit) or emblem.tga (32bit) and be located in your main Aion folder.

 

Your best shot at a good logo is to have a transparent background and saving the logo as a 32bit .tga file. The latest Photoshop versions changed the way they handle .tga files. So if you use Photoshop, your best bet is to create the logo, save the .psd and then load it with Gimp (a free program) and save the .tga from there. Or you can create it with Gimp from the start, but I still prefer Photoshop. If you do not have or can afford Photoshop, Gimp works very well for this.

 

Download Gimp for Free: http://www.gimp.org/

 

If you want to use an older version of Photoshop, you will have to create a transparent alpha channel to get the transparency to work in Aion.

 

 

 

**This tutorial will use Photoshop CS and Gimp, but it could be done in Gimp alone if you need a completely free option.**

 

 

Step 1

Start your guild emblem design at 256x256 pixels but at 300 resolution so that it is larger and easier to detail and edit. Make sure the new file has a transparent background and is RBG Color at 8 bit.

 

GuildEmblemStart.jpg

 

 

Step 2

Create your design (feel free to view my sample emblems following this tutorial)

**note that the design will be very small on the cloak and extreme detail will not convert well to the small cloak**

 

GuildEmblemFlameLarge.jpg

 

 

Step 3

Save your file as a .psd file and open it in Gimp

 

Step 4

Once opened in Gimp, Go to File > Save As >

 

name your emblem: emblem.tga and save it to your Aion folder

 

Save

 

GuildEmblemSave.jpg

 

Another window opens up if you have multiple layers, make sure the bottom layer is transparent if you don't want a box in your emblem.

 

GuildEmblemMerge.jpg

 

Another window opens up after that with an RLE Compresion checkbox.

UNCHECK IT!

 

GuildEmblemRLE.jpg

 

 

Congrats!

Your emblem is now saved!

 

For Photoshop Users:

 

Step 1

Open Photoshop and open the image file that you want to make transparent. You need to ensure your image is in RGB format. If you're unsure you can check the mode by selecting "Mode" from the "Image" dropdown menu at the top of Photoshop and ensure "RGB" has a check mark next to it.

 

Step 2

Fill your canvas will any color of your choosing. You can easily do this by selecting the "Fill" option from the "Edit" menu.

 

Step 3

Select the area of the image you want to erase. Use any selection tool you prefer, but many people find the magnetic lasso selection tool works well for larger projects and the magic wand is ideal in erasing solid color backgrounds. If you use the magic wand make sure to have your settings at a level 10 tolerance and check the anti-alias and contiguous options at the top of the screen.

 

Step 4

Reverse the selected area by choosing the "select inverse" option once you see the marching ants selection box around the background. Select the inverse by either right-clicking on the object and selecting the option from the menu that pops up or use the keyboard shortcut "Shift + Ctrl + I."

 

Step 5

Create a new layer by right-clicking on the selection and choosing "Layer via Copy" from the menu that opens. The newest layer will appear at the top of your "Layer" palette menu.

 

Step 6

Save the selected area by choosing "Save Selection" from the "Select" menu at the top of the screen. You don't need to specify a name for the saved selection, but make sure the "New Channel" option is selected.

 

Step 7

Change your view on the "Layer Palette" to "Channels" to view the alpha channels. Select the "Alpha 1" channel you created in Step 5 and adjust the brightness and contrast using the "Image>Adjustments>Brightness/Contrast" option.

 

Step 8

Remember that the lighter gray the alpha channel is, the more transparent the image will be. And the darker gray the alpha channel is, the more opaque the image will be. Continue to play with the image until you're satisfied with the results, and always save your work.

 

 

Credits:

AionSource.com

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

    • Since technical talk offends people, I believe I should return back to writting my Lineage 2 lore stories. Here's the next one:   Once upon a time, there was a boy and a small adorable wolf.    The boy really loved the wolf but as the wolf grow older and bigger, it became agressive and would bite the boy. One day the boy and the wolf decided to go to the city to buy potions. The road was long and hilly so the boy moved all his adena to the wolf bags to help his legs and reach the city easier.   When they reached the city, the boy tried to take the adena out of the wolf's bags. But the wolf would not ! He bit the boy and said "You will not get this adena back, this is my adena". The boy got angry. He decided to go to the pet master and ask for help.    "Pet master, pet master ! My wolf is big, bad and angry and it won't obey me. I want my adena back and it bites me. "   The pet master looked at the big angry wolf, then looked at the boy and said. "I have a solution for your problem young one. I have magic. Dark magic. I can turn your big bad elder wolf into a younger puppy for free, all you have to do is spell the magic chants. Nothing more, no wolf modifying wands, just your say".   The boy thought about it for a bit, and decided that he indeed wanted to turn things back. But when he was about to spell the magic words, guards arrived at the pet master.    The city guard captain said "Is this the big bad angry wolf that bites people and doesn't give back his adena ? We will kill this wolf !"    For a moment the boy hesitated but he said "This wolf is big bad and angry, but I love this wolf and I dont want it to die ! Please don't kill the big bad angry wolf." But the boy was not fast enough. The guards jumped the wolf and started slashing on him with their swords. The boy didn't know what to do, so in it its final moments right as the wolf was about to die, it spelled the magic words. "Pet master, make my wolf young and adorable again !"   But he was not fast enough. The wolf got slashed and killed by the guards just one moment before the boy could finish his last word.    But as the words came out of his mouth, with the wolf's dead body on the floor, a younger wolf manifested out of thin air. The magic was real. The guards got scared and run away. Now the boy was left with a dead old bad angry wolf and next to him an alive younger version.    The boys joy was even bigger when it opened the new wolfs bags and his adena was finally there. He took the adena and went back to buy potions in the city.   Twenty four hours later, the boy couldn't believe how his fortune would change ...   (No AI was used to write this story)
    • This is like 2017 MaxCheaters. i love it.
    • NEW SEASON GRAND OPENING FROM - 30 OCTOBER 2026, FRIDAY, 20:00 +2 GMT !
    • My bug report was a proper submission. I shouldn't have shown the exploit, I will accept that. Let's end it here. 
    • To Finish this, because it's need a explanation   1. “I come to your forum” — It's the L2JMobius forum, not mine. I'm a contributor, not the owner or the maintainer responsible for deciding which fixes get committed.   2. “Which is why I left” — That's not an accurate account of what happened. You may have left voluntarily once, but you were also banned from the Discord server three times after repeatedly returning and causing the same disruptions. Those are not the same thing.   3. “You personally reply and reject that it works” — I asked how a negative withdrawal could be performed and later requested a demonstration of the claimed exploit. At no point did I reject the patch or claim the vulnerability was impossible. Asking for evidence is not the same as rejecting someone's work.   4. “You leave it unpatched for days” — I don't make that decision. Whether and when a patch gets committed is entirely up to the project maintainer, not me.   5. “You challenge me to post a video” — Yes, I asked you to demonstrate the exploit. You interpreted that as a rejection of your work, which it wasn't. Requesting proof of a claimed exploit is a perfectly reasonable part of technical discussion.   6. “Asshole-ness is a mutually contracted disease” — You're responsible for your own behavior, just as I'm responsible for mine. Disagreeing with you or questioning your claims doesn't justify personal insults. If you believe I've treated you unfairly, address what I actually said rather than making my behavior an excuse for yours.   And one question remains unanswered: why did you publicly disclose the exploitationmethod before the fix was released, after previously saying you wanted to avoid harming the project?   The vulnerability was real, the fix was accepted, and the commit was published. I have no problem acknowledging any of that.   My disagreement has never been about whether the bug deserved to be fixed. It's about how you've handled the discussion and repeatedly misrepresented my role in it.     I have nothing against you personally. My issue is with the way you conduct yourself in these discussions.   And no, you're not obligated to prove anything to me. However, when you make a technical claim, the burden of proof is on you. You cannot reasonably expect others to accept your claims without sufficient evidence.   Questioning a claim is not the same as rejecting it, nor is it a personal attack.   This isn’t about fanaticism; it’s about pushing back against the completely senseless attacks constantly leveled at the project as a whole.   It’s always the same thing: they badmouth it, claiming the project is worthless—yet the very same people criticizing it are the first in line to download a leaked version.   Enough is enough. This discussion has dragged on far too long over something that ought to be straightforward; if you’re going to submit a bug report, you should at least do it properly.
  • 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..