Jump to content

Recommended Posts

Posted

Final Image

 

As always, this is the final image that we’ll be creating:

watertext11b.jpg

 

Step 1

 

Create a new document (600X600px).

 

Paste in this great Texture

watertext1.jpg

 

Step 2

 

We want a near black background, but with a subtle texture.

 

To achieve this, go to blending options for your texture layer and apply a black color overlay

watertext2a.jpg

 

Step 3

 

Create a new layer called ‘radial gradient’ and drag out a white-transparent radial gradient from the center of your canvas.

 

Then change this layer’s blend mode to ‘overlay’ and reduce it’s opacity to 50%. This should create a subtle lighting effect over your texture:

watertext3a.jpg

watertext3b.jpg

 

Step 4

 

Use your text tool to type out a large letter ‘P’ in the center of your canvas.

 

I used ChunkFive, 372pt, white for my text:

watertext4.jpg

 

Step 5

 

We will only be using this letter as an outline, so we don’t want it too imposing/obvious.

 

I reduce it’s opacity to 10% just to use as a guide for my main piece:

watertext5.jpg

 

Step 6

 

Now I want to start adding water to my composition.

 

I prefer to arrange all of my water images before I start applying them, so I’m careful to extract all relevant images and organize them correctly before I start adding them to my final piece.

 

I’ll show you how to extract water properly using the color-range option:

watertext6a.jpg

watertext6b.jpg

 

Step 7

 

Now it’s time to extract the water!

 

Go to select>color range. The default setting should be to select ‘sampled colors’ and the fuzziness setting should also be fine as it is. You can see these settings below:

 

Then press OK, and copy/paste your selection back into your original document.

 

I like to duplicate my water layer, and then merge the duplicate down with the original. This simply gives it more impact and makes it a little bolder:

watertext7a.jpg

watertext7b.jpg

 

Step 8

 

Now repeat this technique to extract the following photos:

 

water photo 1.

1104884_droplets_1.jpg

water photo 2.

1180590_lemon.jpg

water photo 3.

884261__2.jpg

water photo 4.

1131843_water_in_the_glass.jpg

water photo 5.

978587_splash_in_the_vodka1.jpg

 

Once you have successfully extracted each photo of water, paste your result into your original document, labeling each ‘water 1′ water 2′ etc… Remember with each to duplicate/merge down in order to make the water really stand out.

 

The great thing about doing things this way is that you now have all the water you need for your composition in a clear, organized set of layers. All you need to do is copy one of these images when you wish to use it on your composition, and hide the visibility of the original layer.

watertext8.jpg

 

Step 9

 

Now we want to use all of these extracted images of water to outline our letter P.

 

The images below show how I build up my outline. To fit all the images in, simply resize them, erase them where needed, and perhaps most importantly use your warp tool (edit>transform>warp) to fit the water to the letter correctly:

watertext9a.jpg

watertext9c.jpg

 

Step 10

 

Now select your original letter P layer. Reduce it’s opacity from 10% to 6%. Then go to filter>blur>gaussian blur and apply a 15px gaussian blur. This should create a very subtle definition for your letter, rather than removing it completely.

watertext10.jpg

 

Step 11

Now create a top adjustment layer (gradient map). Create a gradient ranging from 0971a2 to 3aa4d6.

 

Finally, reduce this adjustment layer’s opacity to 50% and change it’s blend mode to ‘overlay’. This should give a nice underwater effect:

watertext11a.jpg

watertext11b.jpg

 

About the Author: Tom

 

earning more about design and interacting with the community. On a more interesting note he can also play guitar hero drunk with his teeth.

Posted

thats easy :a

not anyone know to make so i post :P

 

 

and cuz u stole my avatar i will kick your ass xD from forum

 

/kick DejaVu

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

    • Added the protection module to the demo.   DDoS Guard Pro v2.0 is a system protection module for PlayMMO CMS designed to reduce the load on the website during HTTP floods, bot activity, suspicious frequent requests, and attacks on individual pages or API methods. Unlike simple global limiters, DDoS Guard Pro v2.0 supports flexible rules based on routes and HTTP methods. This allows you to block the entire site in a targeted manner, rather than blocking the entire site equally. You can set up protection for specific areas of the site, such as login, registration, APIs, administration, forms, and other sensitive areas. What is the purpose of the module? DDoS Guard Pro v2.0 helps protect your site from basic L7 attacks at the HTTP request level. The module is useful when your site receives: frequent requests from a single IP address; HTTP page floods; login or registration form flooding; automatic requests from bots; URL scanning; frequent API requests; suspicious activity spikes; load on individual CMS methods or pages. The module helps to reduce the load on PHP and CMS by limiting suspicious activity before it starts to create a serious load on the site. Main features Per-route and per-method Rate Limit In the new version, protection is configured not only globally, but also according to specific rules. You can set limits separately for: GET; POST; PUT; PATCH; DELETE; ALL. This allows you to flexibly protect different parts of your website. For example: for the login page, you can set a strict limit; for registration, you can set a separate limit; for the API, you can set a limit for reading and a limit for changing data; for regular website pages, you can set a soft limit or not set a limit at all. This approach reduces the risk of accidentally blocking regular users and makes the protection more accurate. Flexible rule system The module supports setting rules in the following format: METHODS|PATTERN|LIMIT|WINDOW|BURST_LIMIT|BURST_WINDOW|BLOCK_SECONDS|IDENTITY|NAME Example of rules: POST|*login*|10|60|5|10|600|ip|login_post POST|*register*|8|60|4|10|600|ip|register_post GET|*api*|300|60|80|10|120|ip|api_get PUT,PATCH,DELETE|*api*|80|60|20|10|300|ip|api_write This allows you to specify exactly: which HTTP methods to protect; which URLs or URL patterns to consider; how many requests are allowed; over what time period; what burst limit to use;  how many seconds to block the offender;  by which ID to count the limit;  what the rule is called. Burst protection against sharp spikes  In addition to the regular request limit, the module monitors sharp spikes of activity.  This is useful when a bot makes many requests in a few seconds. In this case, the protection can be activated faster, without waiting for the overall limit per minute.  Burst protection is especially useful for: authorization pages; registration; API; search; data submission forms; administrative sections. Support for different types of requests DDoS Guard Pro v2.0 works not only with POST requests. The module can control: GET — regular pages, API requests, search; POST — forms, login, registration, data submission; PUT — updating data via API; PATCH — partial data update; DELETE — data deletion; ALL — all methods at once. This makes the module suitable not only for regular sites, but also for CMS with API, personal accounts, game panels and administrative actions. Limit storage: Redis, APCu and file fallback In the new version, the module supports several options for storing temporary data. Available modes: Redis; APCu; file fallback. The auto mode tries to use the most suitable option: Redis; APCu; file storage as a fallback. Redis or APCu are suitable for more efficient operation, while the file storage is left as a fallback option for simple hosting environments that do not have additional extensions. JSONL logging The module records protection events in JSON Lines format. Logs are saved in the following file: storage/logs/ddos_guard.jsonl This format is more convenient than a regular text log, because each event is stored as a separate JSON record. The logs can record the following information: event time; IP address; HTTP method; URL; name of the triggered rule; reason for blocking; number of requests; action status; user-agent; protection mode. The JSONL format is convenient for analysis by external tools, log agents, and monitoring systems. Prometheus metrics DDoS Guard Pro v2.0 adds an endpoint for receiving metrics in Prometheus format. Endpoint: /?ddos_guard_metrics=TOKEN The token is set in the module settings. Metrics allow you to track: the number of processed requests; the number of rule activations; the number of blocks; activity by limits; protection events; module status. This allows you to connect monitoring and configure alerts so that the administrator can see when suspicious activity starts on the site. LOG ONLY mode The module has a LOG ONLY mode. In this mode, DDoS Guard Pro does not block users, but only records events and potential triggers in the log. This mode is recommended to be used after installation, in order to first see which rules are triggered, and only then to enable the real blocking.  This helps to avoid too strict limits and random blocking of regular users.  Support for Cloudflare and proxy  The module supports working behind Cloudflare or another reverse proxy.  With proper configuration, it is possible to take into account the real IP of the user, and not the IP of the proxy server.  This is important for sites that use:  Cloudflare; nginx reverse proxy; load balancers; CDN; hosting proxy protection. Nginx-recommendations DDoS Guard Pro v2.0 contains an example nginx-config: modules/ddos_guard/nginx-ddos-guard-example.conf This allows you to use the module as an additional application layer of protection, and to move the main coarse limits to the nginx level. Recommended protection scheme: Cloudflare / nginx / firewall → DDoS Guard Pro → PlayMMO CMS This approach is more correct than trying to solve all problems only at the PHP level.
  • 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..