Jump to content

Recommended Posts

Posted

Octopusswf.jpg

This approach will also let you add extra elements to the game easily, and the technique can be applied to a variety of different game types: the principles are largely the same whether you’re creating a driving game or a shoot-‘em-up. If that all sounds a bit scary, don’t worry – it will start to make sense as we work through the steps.

 

step01.jpg

 

01. Open your FLA from last month (or open start.fla from the cover disc). First, we need to allow the player to control our character, Madame Octopus (MO). We need to control her using ActionScript, so open your library (Cmd/Ctrl + L) then locate your Madame Octopus MovieClip. Right-click (Ctrl + click) on the MovieClip, choose Properties and then under Advanced, tick the Export for ActionScript checkbox. Give it an Identifier of ‘MO’ and a class of ‘MO’.

 

step02.jpg

 

02. A class, in this context, is a text file with a set of instructions and information about an object. In this case, we need to create a file for the class we just created: ‘MO’. Choose File > New, then from the Type list select ActionScript File. We’ll enter all the code for MO into this file. Save the file as MO.as.

 

Step03.jpg

03. Enter the following code into your MO.as file (you can copy and paste it from the file Step 3 on the cover CD), then save the file and return to the main Flash movie. class MO extends MovieClip { var movedelta = 10; function onEnterFrame() { if( Key.isDown(Key.RIGHT) ) { _x = _x + movedelta; } if( Key.isDown(Key.LEFT) ) { _x = _x - movedelta; } if( Key.isDown(Key.UP) ) { _y = _y - movedelta; } if( Key.isDown(Key.DOWN) ) { _y = _y + movedelta; } } } Select Control > Test Movie to test whether the movement works when you press the arrows on your keyboard.

 

Step04.jpg

 

04. The code we just created sets up the class MO as a sub-class of the MovieClip class; that is to say, we’re using the existing MovieClip class and giving it some extra instructions. We create a variable called movedelta and give it a value of 10. This is the amount, in pixels, that the character will move each time a button is depressed. We also added four conditional statements inside a function. The function is special, as it’s built into the MovieClip class. onEnterFrame executes every time a frame is encountered in the movie. As our movie is running at 30fps, this function will execute 30 times a second. The conditional statements check each arrow key in turn to see if it is pressed down and if it is, the position of the character is updated on the X or Y axis, as appropriate.

 

step05.jpg

 

05. We’ve now got Madame Octopus happily moving around the screen in response to the arrow keys. The next stage is to add some objects for her to avoid. We’ll make use of the bubble movie clip that we used last month. Locate the bubble MovieClip in your library, right-click (Ctrl + click) on it and choose Duplicate. Name the duplicate ‘evilBubble’, and again tick Export for ActionScript, giving the MovieClip an identifier of ‘EB’ and a class of ‘EB’. If you didn’t complete last month’s tutorial, open the file EB.as from the cover CD.

 

Step06.jpg

06. Double-click on the evilBubble symbol in the library, and remove all but the first frame of the timeline by highlighting the frames, right-clicking and selecting Remove Frames. Delete the motion guide layer, then reposition the bubble so that its centre aligns with the origin crosshairs on the stage. Select the bubble and use the Tint colour effect to give it a colour.

 

step07.jpg

 

07. The evil bubble doesn’t yet appear on stage; it’s in the library waiting to be used. We’re going to create lots of evil bubbles using ActionScript. Go to File > New, select ActionScript file, and save the resulting document as EB.as.

 

step08.jpg

 

08. Enter the following code into the EB.as file (you can copy and paste it from the file Step 8 on the cover CD). This code is similar to that for the MO class, but has a few differences we’ll look at in a moment: class EB extends MovieClip { var speed; function onLoad() { _x = 800; _y = Math.random()*490; _xscale = _yscale = Math.random()*80 + 20; _alpha = 60; speed = Math.random()*5 + 5; } function onEnterFrame() { _x -= speed; if(_x < -60) { this.removeMovieClip(); } } }

 

step09.jpg

 

09. The code we’ve just added sets up a variable called speed that represents how quickly the bubble moves across the screen. When the bubble is first created, we set it to appear off the right-hand side of the screen (at an X position of 800 pixels) and we randomly set the Y position somewhere between 0 and 490 pixels (the height of our movie). We create a random scale and speed for the bubble, then each time the onEnterFrame function runs we update the position of the bubble and if it’s moved out of sight (60 pixels to the left of the screen) we remove it.

 

Step10.jpg

10. The bubble is ready to go now, but we need something to make it appear. We’ll use the MO class to do this, as the character is always on screen. Edit the MO.as file, and add a new variable underneath the var movedelta = 10 code as follows: var bubbleCounter = 0; Next, after the code that checks for the arrow key presses (within the onEnterFrame function) enter the following additional code (or get it from the CD file Step 10): bubbleCounter += 1; if(bubbleCounter > 30) { bubbleCounter = 0; _root.attachMovie(“EB”, “EB”+_root.getNextHighestDepth(), _root. getNextHighestDepth()); } } }

 

step11.jpg

11. Test your movie: you should see an evil bubble appear on screen every second, travel across the screen and disappear off the left-hand edge of the screen. As it takes more than one second for the travel to happen, it’s possible to have many bubbles on screen at once. The code we’ve just added controls how often (in frames) a new bubble is created. If you want more, lower the “>30” bit of the code to, say, “>20”. If you want fewer, increase that number.

 

step12.jpg

 

12. We’re going to add some collision detection to the bubbles. When they hit Madame Octopus, we want to end the game (the aim being to avoid the bubbles for as long as possible). To do this, we need to first give MO an instance name so we can refer to her from the bubble class. Click on the Madam Octopus then enter an instance name of ‘octopus’ in the Properties panel.

 

step13.jpg

 

13. Create a new symbol (Insert > New Symbol), drag it onto the stage and give it an instance name of endGamePanel. Inside the endGamePanel, create a ‘Game Over’ screen to suit (or check out our version). Set the alpha property of your symbol to 0. Create a new layer in your main timeline. Name it actions, then add the following code, or copy and paste it from the cover CD file Step 13a: Var tmpscore = 0; var playing = true; function endGame() { playing = false; _root.endGamePanel._alpha = 100; } Edit EB.as and enter the code below inside the onEnterFrame function, or copy and paste it from file Step 13b on the cover CD. This uses the built-in hitTest function to check if a bubble is touching MO. If it is, the bubble is removed and the endGame() function is called: if(this.hitTest(_root.octopus)) { this.removeMovieClip(); _root.endGame(); }

 

step14.jpg

 

14. In the main timeline, add a text field set to Dynamic. Name the field ‘score’. In your EB.as file, immediately after if(_x < -60) {, enter the following code: _root.tmpscore+=10; _root.score.text = tmpscore; Finally, we can stop the score from growing when the game ends by adding a conditional statement around the score code and the bubbles code. Add the following code around your existing statements: If (_root.playing) { // existing code is in here } Check our sample files on the disc to make sure you’ve inserted this code correctly.

 

step15.jpg

 

15. Taking it to the next level from here isn’t hard; the basics are all in place. Why not add a ‘Play Again’ button to the endGamePanel? This would need to reset ‘playing’ to true, tmpscore to 0 and hide the endGamePanel again. You could also add characters that squirt ink, and arm your octopus with a weapon. The code we used for the bubbles will work for these.

 

 

Credits: Digital Art

Posted

Sorry if this is considered as spam but im very angry..

 

Ok you c/p a guide from a site ok but c/p 20 guides from a site that becomes annoying.

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

    • Update: Advanced Rate Limiting Rate limiting is now applied to: Login attempts Account registration Password recovery Email confirmation resends WhatsApp verification Checkout access The system maintains independent counters by IP address and user identity, helping prevent traditional brute-force attacks as well as distributed credential-stuffing attempts using multiple proxies. Brute-Force and Credential-Stuffing Protection Protection is not limited to the visitor's IP address. The system also tracks attempts associated with the account, username, or email address, reducing the effectiveness of attacks performed through rotating IP addresses, proxies, or VPN services. Global HTTP Security Headers Security headers are applied across the entire website: X-Frame-Options X-Content-Type-Options Referrer-Policy HTTP Strict Transport Security These headers help protect the website against clickjacking, MIME-type confusion, insecure referrer exposure, and HTTP downgrade attempts. Secure Error Handling Internal exceptions are recorded in protected security logs while visitors receive sanitized error messages. This prevents the accidental exposure of: Internal file paths Database information SQL errors Server configuration Application stack traces Private Storage Exposure Monitoring The system automatically checks whether the private storage directory is publicly accessible in production. If exposure is detected, a security warning is recorded for the administrator without interrupting the website. This directory may contain licensing information, rate-limit records, and security logs and must never be publicly accessible. OAuth Request Protection Google and Facebook authentication flows use cryptographically random state values stored in the user's session. Returned state values are validated using constant-time comparison, helping prevent OAuth request forgery and unauthorized account-linking attacks. Telegram Authentication Validation Telegram login information is protected through: HMAC signature validation Constant-time hash comparison Authentication timestamp verification Expired-login rejection Secure Verification Tokens Email, password recovery, and WhatsApp verification systems include: Cryptographically secure random tokens Hashed WhatsApp verification codes Automatic expiration Limited verification attempts Resend cooldowns One-time token invalidation Account Activation Protection When email or WhatsApp verification is required, the game account remains restricted until all required verification steps are completed. Unverified users cannot bypass the confirmation process through standard or social login. Secure Upload Processing Administrative image uploads include: Real MIME-type inspection Image-content validation File-size limits Extension allowlists Server-generated random filenames Rejection of invalid or disguised files Original user-provided filenames are never used as the final stored filename. Path Traversal Protection Theme and template identifiers are restricted to validated slugs and must exist in the internal list of allowed themes. This prevents directory traversal and unauthorized local-file access through manipulated template names. Atomic Ticket Transfer Protection Ticket transfers use transactional and durable delivery processing. The balance is conditionally debited, the delivery is recorded before communication with the game database, and failed deliveries remain pending for safe reprocessing. This helps prevent: Free-item delivery Inconsistent balances Duplicate delivery Partial transaction failures Lost transfer records Concurrent Balance Protection Administrative balance adjustments use database transactions and row-level locking. This prevents simultaneous balance operations from overwriting each other or creating inconsistent account balances. Secure Redirect Handling Redirect values are sanitized against header injection, and external redirects are restricted to HTTPS destinations. Password Security Improvements The website uses modern password hashing for player-panel accounts and bcrypt with a configurable cost for supported game-server account systems. Compatibility is included for game-server implementations requiring the $2a$ bcrypt prefix. Duplicate Payment Prevention Built-in protections include: Idempotency control Transaction reference validation Payment status verification Unique external payment references Database transactions and rollback Durable payment history Completed-order verification These protections prevent: Double credits Repeated processing Duplicate payment callbacks Incomplete financial operations Signed Payment Callback Protection Payment callbacks are protected through: HMAC-SHA256 authentication Constant-time signature comparison Signed callback timestamps Callback freshness validation Shared callback secrets This helps prevent forged payment notifications, callback manipulation, and replay attacks. SQL Injection Protection The database layer uses: PDO Prepared statements Parameter binding Controlled internal allowlists for dynamic identifiers User-controlled values are not directly concatenated into SQL queries. XSS Protection Output and form data are protected through: HTML escaping Attribute escaping Input filtering HttpOnly session cookies MIME-sniffing protection Frame embedding restrictions These measures reduce the risk of Cross-Site Scripting, malicious HTML injection, session theft, and clickjacking. CSRF Protection Sensitive forms and administrative operations use session-based CSRF tokens. Requests without a valid token are rejected, helping prevent unauthorized actions performed through malicious external websites. Secure Session Protection The session system includes: HttpOnly cookies Secure cookie support SameSite restrictions Session ID regeneration Authentication state validation Session timeout controls These protections reduce the risks of session fixation, session theft, and unauthorized account reuse. reCAPTCHA Protection Google reCAPTCHA may be enabled on sensitive public forms to reduce: Automated account registrations Spam submissions Bot login attempts Automated password recovery abuse Confirmation Resend Limits Email and WhatsApp confirmation resends are protected through: Cooldown periods Rate limiting Expiring verification codes Attempt counters This prevents verification-message flooding and excessive external API usage. Licensing and Anti-Cloning Protection The website includes centralized licensing controls with: License-key validation Domain binding Signed license responses Cached license validation Temporary offline grace period Circuit-breaker protection Unauthorized-domain rejection These measures help prevent unauthorized installation, cloning, and redistribution of the system.
    • Tool that allows you to download the Lineage 2 game client directly from the official publisher CDNs. It fetches the CDN's file list and downloads every patch file, decompresses it (LZMA / Zip) and writes the finished client to disk — and can resume or repair an existing installation instead of starting over. It runs several client downloads at once through a batch queue, so you can prepare multiple regions or versions in a single session.   Supported: NCSoft CDNs (TW / KR / JP / NA) and  4game CDNs(RU / EU)   Download: https://drive.google.com/file/d/11SDcNASqO2GKOBT79LFu7mqvSRSJZvBS
    • https://l2avokado.com/ Hello everyone,   After some time of development, we've decided to open L2Avokado to the public in its current development stage. We're looking for players who enjoy Interlude and would like to help shape the project before its official release.   This isn't a "launch" announcement. Instead, we're inviting the community to log in, explore the server, test the systems we've built, and provide honest feedback. Whether it's bug reports, balance suggestions, progression ideas, or quality-of-life improvements, we'd love to hear them.   Our goal has always been to create an Interlude server that feels familiar while offering a fresh progression experience. We've intentionally avoided custom weapons, armor, and client modifications. Instead, we've focused on redesigning progression through reworked hunting grounds, quests, crafting, and gameplay systems while remaining compatible with a clean Interlude client.   At this stage, the core progression path has been implemented, including the main hunting grounds, quests, custom systems, and events. However, as the project is still under active development, there will inevitably be bugs, balance issues, and areas that require further polishing.   This is exactly why we'd like your help.   We're looking for players who are willing to: Test gameplay and progression. Report bugs and exploits. Suggest balance improvements. Share ideas for new features or quality-of-life changes. Help us build a server that the community genuinely enjoys playing.   The Client and System downloads are already available on our website, so you can jump straight into the game. We're also working on a dedicated launcher that will simplify installation and future updates.   If you're interested in helping develop a unique Interlude project and want your feedback to genuinely influence the direction of the server, we'd love to have you with us.   We look forward to seeing you in-game and hearing your thoughts on Discord. https://l2avokado.com/
  • 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..