Jump to content

Chawaka

Banned
  • Content Count

    19
  • Joined

  • Last visited

  • Days Won

    1
  • Yangs

    0 [ Donate ]

Chawaka last won the day on June 9 2014

Chawaka had the most liked content!

Community Reputation

23 Neutral

About Chawaka

  • Rank
    Neutral
  • Birthday September 30

Informations

  • Gender
    Male
  • Location
    Cairo

Recent Profile Visitors

836 profile views
  1. I think the problem is that I'm on 64 bit.. Gonna try 32bit and see if that works out...
  2. I went to compile the mainline source on FreeBSD 9.2 64bit and that's what I got.. Does anyone by a slim chance know a fix for this? compile BattleArena.cpp compile FSM.cpp compile MarkConvert.cpp compile MarkImage.cpp In file included from debug_allocator.h:5, from stdafx.h:7, from MarkConvert.cpp:1: /usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:100: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:105: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:106: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter compile MarkManager.cpp In file included from BattleArena.cpp:6: char.h:729: error: integer constant is too large for 'long' type In file included from debug_allocator.h:5, from stdafx.h:7, from BattleArena.cpp:1: /usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:100: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:105: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:106: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter In file included from debug_allocator.h:5, from stdafx.h:7, from MarkImage.cpp:1: /usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:100: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:105: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:106: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter gmake: *** [OBJDIR/MarkConvert.o] Error 1 gmake: *** Waiting for unfinished jobs.... gmake: *** [OBJDIR/MarkImage.o] Error 1 In file included from debug_allocator.h:5, from stdafx.h:7, from MarkManager.cpp:1: /usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:100: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:105: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter /usr/include/c++/4.2/new:106: error: 'operator new' takes type 'size_t' ('unsigned int') as first parameter gmake: *** [OBJDIR/BattleArena.o] Error 1 gmake: *** [OBJDIR/MarkManager.o] Error 1
  3. Humm the db structure from Shogun has problems it'll bring you connection refused, fdwatch and apples and oranges..
  4. chmod 777 your auth, game and db cores. i doubt that the files are actually in the called path from the sh script. you could also be missing on the shortcuts.
  5. That's been helpful to me shedding some light on the flaws, thank you man. I agree with you about the effects, they indeed feel overloaded on the render and are pretty much taking over it. The surrounding flame ring was also kind of a mess and lacking that kind of realisticness in effect, so I adjusted all that in this new Sexy version with one more render being finished as well!
  6. Include the effect in the NPC's msm.
  7. Heyhey! So I just finished manipulating this bad boy render and I wanted to hear your opinions about it
  8. I don't think such tools are ever helpful for beginners cause they are rather unlikely to learn anything from using eased tools and stuff..
  9. the else statement I contributed is for when the else statement above it isn't the right statement to be called since you are logged in, the registration is enabled, and it shows error as though the registration is closed, this however slows down the server response - but now it checks if the register is set to true or false, if it's true and you are logged in, then it'll return true but with notification that you are logged in and that's what the else statement you're referring to is for, not returning false as that widely used registration script responds to it. If you take a look at the full PHP code of your registration you should get it right. It couldn't be simpler. This also stabilizes the PHP code, no more retrieving of invalid statements.
  10. There's already an if statement at the very top and beginning of the script that checks for the registration status, no need for more if statements otherwise we're validating a complete another form. Yeah I'm sure this should work for every script I tested it.
  11. So last night I came up with a good idea for registration scripts, applied it and thought I would share it with you. This is a very simple yet useful modification that will tell players whether the registration system is activated, disabled, or they are already logged in. No more guessing! So basically open up your registration script - look for the line that tells users if they cannot create a new account cause they are already logged in, or the registration system is disabled, which will probably look like this: <?PHP } else { echo 'You are either already logged in, or the registration system is currently disabled.</div></div>'; } ?> And replace it with: <?PHP } else { echo 'You can not create a new account while being logged in.</div></div>'; } } else { echo 'Registration system is currently disabled.</div></div>'; } ?> And that's it.
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / 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.