Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 02/06/2011 in Posts

  1. 11 points
    AlterEgo

    Some changes going on.

    We are dropping support for SkyFire one and SkyFire 4.0.6a to focus on the current patch "5.4.8" and also to work on the upcoming "6.x.x" Versions. You will also notice some changes going on in the forums as well. Like all your avatars have been reset. The forum will also be cleaned and rearranged to make more user friendly. Wiki is set to get an overhaul too.
  2. 7 points
    AlterEgo

    Back to 5.x.x

    We decided to resurrect our 5.x.x core due to TC deciding to work on 6.x.x. It's still a great expansion to play around on.
  3. 7 points
    AlterEgo

    5.4.7 Limited Support

    We are pleased to announce limited support for Mists of Pandaria 5.4.7 Build: 18019. Please submit constructive bug reports in the bug tracker so we may compile a list of stuff to fix. DO NOT USE THE FORUM AS A BUG TRACKER The GitHub repository has a bug tracker.
  4. 7 points
    AlterEgo

    Project Information and Links

    IRC CHAT irc.rizon.net #project_skyfire  List of IRC clients. Windows: IceChat  -- http://www.icechat.net mIRC      -- http://www.mirc.com  Mac: Colloquy -- http://colloquy.info/ LimeChat -- http://limechat.net/mac/  CORE SOURCES: 4.0.6a core source and Bug tracker. NO LONGER SUPPORTED! https://github.com/SkyFireArchives/SkyFireEMU_406a  5.4.8core source SUPPORTED https://github.com/ProjectSkyfire/SkyFire.548  DATABASE: Database files are only downloadable by forum members. http://www.projectskyfire.org/index.php?/files/  WIKI: http://wiki.projectskyfire.org  RECOMMENDED FILE SERVICES:  Dropbox -- https://db.tt/Zw76Fr6 Filebeam -- http://www.filebeam.com
  5. 5 points
    Section I - General Policy: By registering and participating in Project SkyFire Forums discussions you agree to the following code of conduct. If you are unable to agree you have the right not to participate in forum discussions at any time. This is YOUR community. Most people have a common sense feel for what is and what is not appropriate in our forums and you folks generally do a great job of policing yourselves. We do, however, need to have a few set policies for everyone to refer to when the need arises. While the administrators and moderators of this forum will attempt to remove or edit any generally objectionable material as quickly as possible where acceptable, it is impossible to review every message. Therefore you acknowledge that all posts made to these forums express the views and opinions of the author and not the administrators, moderators or web-master (except for posts by these people) and they will not be held liable. You agree not to post any abusive, obscene, vulgar, slanderous, hateful, threatening, sexually-orientated material or any other material that may violate any applicable laws. (Please note that the backyard has some additional rules specific to that venue.) Doing any of these may lead to you being temporarily or permanently banned from these forums (and your service provider may also be informed). Posts which violate any part of this Code of Conduct may be edited or moved to a special holding area called "The Jail". Posts in The Jail are only visible to staff members and the original poster. If you were to continue to break this code of conduct your account would be reviewed and you could be banned. It is the sole discretion of the forum resolution team (currently the administrators) to ban violating accounts. Accounts will not be deleted, although email addresses can be removed from accounts by request if the account is not going to be used any longer. The IP addresses of all posts are recorded to aid in enforcing these conditions. You agree that the web-master, administrators and moderators of this forum have the right to remove, edit, move or close any post, topic or thread at any time they see fit following the guidelines outlined below. You agree that the web-master, administrators and moderators of this forum have the right to send a private message with a warning and/or censor any forum user who is in violation of forum policy* Be respectful of all users at all times. This means please use etiquette and politeness. Treat people with kindness and gentleness. If you do this the rest of the code of conduct won't need more than a cursory mention. Respect the forum staff. We provide a service in our free time to keep the forums running efficiently. We will occasionally ask for input, but in some cases we will not, please respect our decisions. Also, we do edit for content, if you have an issue with our moderation, please open a request in the forum resolution center.Profanity: Remember that the forums are used by people of all age groups and of all tolerance levels regarding profanity usage. When in the support areas of the forum, please try to keep your language polite and courteous and refrain from the usage of profanities. In the General Discussion area, mild profanity/swearing is allowed in the context of general speech. Explicit profanity/swearing is not allowed, and under no circumstances will we allow any profanity to be directed toward another person. Please see the Project SkyFire Code of Conduct requirements to "Be Considerate" and to "Be Respectful" and the descriptions given there for more exact specifications. A language filter is in place to catch any profanities that you may have accidentally used. Do not attempt to circumvent the language filter by using variations or slight misspellings of profanities.Flaming and condescending messages: Flames are messages that personally attack, call people names, or otherwise harass another forum member (or any person). These, along with any generally condescending posts will be moved or removed at the moderators discretion.If the thread is flame-bait (appears to be intended to start an argument or is likely to cause an argument rather than enhance discussion), it will be locked or removed without notice. Individual flame-bait may be deleted or edited at the moderators discretion. Any users who continue to post in this manner or engage in other questionable practices, like trolling (posting in an attempt to engage people in arguments) may be subject to more serious sanctions.If the thread turns into an argument, it can be locked or removed without notice. Sometimes a moderator may split the thread or delete certain portions in order to keep the discussion going, but that is not always possible.If a post or thread contains spam (unsolicited advertising) it will be moved to the forum jail and the poster may be banned. Active users in good standing are allowed to have links to personal sites in their signatures, in their profile, and may post them in threads on occasion (just not often, please) as long as the content of those links does not include abusive, obscene, vulgar, slanderous, hateful, threatening, sexually-orientated material or any other material that may violate any applicable laws.Adult Content/Violence/Illegal Activity: Messages containing sexually oriented/violent/illegal dialogue, images, content, or links to these things will be deleted. Messages with links to or suggesting illegal activity will also be deleted. Posting or linking to any of these could result in a ban.Thread Drifting/Steering: Please keep discussions on topic. Non-technical and non-3rd party project discussions belong in the General Discussion. Please remember that these forums are inclusive of ALL people, and we strive to maintain accessibility to everyone. Please strive to communicate with other users as effectively as possible. Please try to write your posts in English unless you are participating in a Localization Forum, where you are permitted to use another language if it is in common use in that Localization Forum and understood by the Localization Forum staff. We have many users from many different countries that visit here and English is the common language of these forums. When writing a post, please space paragraphs with a blank line in between them for better readability. Please do not write posts in all upper-case letters, as it looks as if you are screaming at the people reading your post. Please refrain from using "leet" speak or slang.* Please do not shorten your words to acronyms or abbreviations. It is very difficult to read and understand. Please use color and font properties for highlighting portions of your text, and not for all of the text in your post. Typos and other errors can cause miscommunication between users on the forums, please preview your text before posting. If you have found a post that you feel is inappropriate or that violates the forum code of conduct, please use the report post function. Do not attempt to moderate discussions or correct other users yourself. Please be prudent in your use of images; they may help to explain something more clearly or indicate a problem you are experiencing better but you have to remember that not everyone has the same bandwidth. If an image is the best way of handling the information, please keep your image to less than 100kb. Forum signatures are limited to three lines of text, 10pt maximum font size. Signatures are also not a place for inappropriate material such as attacks, slander, harassment, political or religious remarks. We regret that users are not allowed to use images in their signatures (see staff signature guidelines below in Section III for an exception to this policy). The use of political images in avatars is also prohibited.If you feel someone has violated the Project SkyFire Code of Conduct you may open a complaint with the administrators. However, forum related issues will need to be dealt with in the forums resolution center. The administrators will refer all forum-specific issues back to the forums resolution center. The web-master, administrators and moderators of this forum will preserve forum content when possible. However editing, locking and deleting content may be necessary and if so will be done at the discretion of the web-master, administrators and moderators when the forum code of conduct has been violated. Private Messaging users for support is strongly discouraged. It is also unlikely that users will respond to these requests.Users should only have one active account. If you feel you have justification for requiring a new account, please contact an administrator to discuss your situation. Users who have multiple accounts without approval of an administrator may be subjected to infractions or bans without notice.
  6. 4 points
    socra2

    5.4.8 Limited Support

    We are pleased to announce limited support for Mists of Pandaria 5.4.8 Build: 18291. Please submit constructive bug reports in the bug tracker so we may compile a list of stuff to fix. DO NOT USE THE FORUM AS A BUG TRACKER The GitHub repository has a bug tracker.  The master branch is now 5.4.8 - 18291, a branch called 5.4.7 was created as an archive for the old version.  If you need any help, feel free to contact us on irc: irc.rizon.net in the channel #project_skyfire  Support for 5.4.7 has been dropped.  PS: Do not compain that we are no longer working on 5.4.7, it was our own choice and we are not your personal fixers.
  7. 3 points
    Section III - Forum Staff Policies and Expectations: Staff duties are based upon the following Dealing with Profanity: Mild profanity/swearing is allowed in the context of general speech. Explicit profanity/swearing is not allowed, and under no circumstances will we allow any profanity to be directed toward another person. If you feel a user is out of line please contact an administration with the details, they will issue a warning to the user.Dealing with spam and potential "jailed" posts: If its a user trying to advertise something move the post to the jail and issue a spam infraction. Posts that are used to flame, harass or harm another person should be reported to an administrator asap. We do not encourage staff to partake in conversation in these types of situations and the administration will handle the issue.Editing of posts: When a post breaks guidelines and requires editing in order to bring it back under compliance with the rules, the moderator should generally copy the un-edited post to the jail first or issue an infraction which will keep a copy of the original post in the staff area. Only then should the original post be edited after the original content was preserved as evidence. In the private message automatically sent when the infraction is issued the moderator should specify or describe which guideline(s) the post did not follow.Thread Closing: If a thread has run it's course and posts have begun repeating themes a thread may be closed - if possible, announce that the thread has run it's course before closing so that people may add closing statements - don't forget to thank all users involved in the discussion. If a thread has become a situation where people are simply too personally involved in the issue a thread may be closed and / or jailed. If a thread is a duplicate of another thread, it may be closed (please provide a link to another open thread on the same topic.) It is always a good idea to post an explanation in a thread that is closed.Jailing of posts/thread: If a post/thread would require a lot of work to bring it into compliance, or if editing the violations would result in a nearly blank post/thread, the post/thread should be moved to the jail instead.Adult Content/Violence/Illegal Activity: Messages containing offensive / sexually oriented / violent / illegal dialogue, images, content, or links to such will be moved to the backyard or jailed depending on the information it contains, use your best judgement. Messages with links to or suggesting illegal activity will soft deleted by an administrator. These actions could result in a ban for the user.RTFM/I hate SkyFire/I hate Ascent threads: As the community has grown these types of threads seem to be more prominent. We need to make sure we can try to steer these conversations into a positive discussion, however in many cases these threads will only end in hurt feelings and will be locked. If the thread cannot be steered into a clean discussion the staff member who locks it needs to be fully supported by staff.Thread Steering: It will become necessary to steer threads away from becoming damaging towards the poster and other users. Our policy is that we do not allow threads to veer too far off topic, even in community chat, to areas where it would be very easy to get ugly fast; for example, "I hate Ascent" threads. Please do your best to keep posters from getting too personal during heated debates.Keeping an open mind: Sometimes you will be faced with a thread you might not agree with it's imperative you keep an open mind towards all inclusive people, and keep a neutral focus when replying. It is our duty to steer the conversations back into a positive nature without engaging in negative behavior.Posting and moderating in the same thread: This is generally discouraged. If you have participated in a discussion and later find there is a problem in the thread contact the other staff and have someone else who is uninvolved moderate. The exception would be if no one is available, you can close the thread temporarily with a post stating that it will be looked at by a non-involved staff member as soon as possible. If you aren't sure what to do, get an administrator.Signatures: While we do not have guidelines for staff signatures, please try to keep them moderate and within reason. Staff are chosen by the site administrators. Users who have demonstrated a consistent attitude of friendliness and kindness and who have shown a pattern of helpfulness in their posts may be contacted and invited to serve in an even more official manner. Recommendations can be made by current staff in the staff forums or other users by private message. All recommendations are considered. Due to time constraints and privacy issues the administrators are unlikely to comment publicly on these recommendations. It should be noted that, like all things, this code of conduct will continue to change and evolve with constructive feedback from users and from experience. It is our hope that these policies will create open, honest, and civil discussion. As always, we welcome feedback about any concerns that you may have so feel free to post in the forum feedback section of the forums. It is the users responsibility to check this page for updates. We require that the forum code of conduct be followed at all times since this is an official SkyFire resource. Public forum data is released under the GNU Free Documentation License.
  8. 3 points
    Section II - Technical Support Policies: When asking for technical support: * There are no stupid questions. You're not a stupid person simply because you do not know how to do something, or do not have the answer to a question. Everyone was a green user at one point in time. * Try to give information in the title of your post, instead of using a title like "it's broken," use a title that is specific, such as, "Unable to get sound to play in World." A clear title will attract more views to your thread, as it gives a clear indication of the content of the post to the people that are willing to help you. Ultimately this will allow you to get more help of a better quality. * Searching the SkyFire Forums is a quick way to see if someone has had your issue and if it has been answered. In a forum as large and active as this one, there's a good chance your question has been answered before, and you can get the information you want quickly. * When requesting help, please include as many details as you can. Include as much information as you know. If people are asking for version numbers, consider checking the sources to find out specific information about the revision you have installed. For example, if you're having trouble with SkyFire, you can search in your Git log and look up the revision hash using git to give the people helping you more information. If you do not know how to find out the information that a user is requesting of you, you might want to ask them how to find the information they have requested. Attach screen shots or other files if you think it might be useful. * It's always nice to let the people that help you know that you appreciate their help. It's extra nice if you then share that information to another user that has the same question you just had. If your question is resolved (which is hopefully always the case!), it would be helpful for other users and the people helping you to label which procedure worked for you by quoting or clearly referring to it. Giving feedback as to what procedures worked not only makes the person helping you feel a sense of accomplishment, you will also be helping any other user with your same issue searching for an answer. When answering technical support issues: * Be considerate to the person asking the question. We were all a green user at one point. Yes, some users are harder to help than others, but please be respectful to all users. * Try to avoid acronyms and jargon when giving instructions. New, or "green" users may not be able to follow you, and many will not ask you for an explanation in order to avoid looking stupid. RTFM, "Go look on google" are two inappropriate responses to a question. If you don't know the answer or don't wish to help, please say nothing instead of brushing off someone's question. Politely showing someone how you searched or obtained the answer to a question is acceptable, even encouraged. * If the users question has been covered in one of the community documents, please give them a description and the links. Some useful sites to point green users are: https://github.com/ProjectSkyfire. You can also show the user how to search the forums or tell them about the forum search utility. If you wish to remind a user to use search tools or other resources when they have asked a question you feel is basic or common, please be very polite. Any replies for help that contain language disrespectful towards the user asking the question, i.e. "STFU" or "RTFM" are unacceptable and will not be tolerated. * Always assume the the user has a default installation unless you're told otherwise. If you tell people to use an application outside of the official SkyFire installation, please give instructions on how to install it. * Always assume that the user is a green user unless you're certain the user is not. Please remember to give detailed instructions some users do not know how to get to a terminal yet. * To avoid confusion and auto-formatting issues, please use CODE tags around terminal commands. If an image speaks a thousand words and can show exactly what you mean, by all means, include an image. * Please wrap long outputs from commands or other text to prevent users from needing to scroll through the content inside CODE tags. * Please remember to do things the SkyFire way. There are always more than one solution to a problem, choose the one you think will be the easiest for the user. Try to think as a green user and choose the simplest solution. * Explain each step of the solution. If possible, try to teach the user while giving a solution to them. Teaching begets more teaching. * If you're uncertain if a procedure is correct, please tell users so. If your procedure has inherent risks, please tell users what they are. For example, if you're teaching someone how to change a database table, please include a disclaimer that it MAY occasionally cause data loss. * Replies to questions that ask for help running legitimate software (albeit closed source or proprietary) that do not answer the question, but instead instruct the user that they should not be using that software on the grounds that it is not free serve only to frustrate and confuse the user and will be removed to make room for answers to the question the user asked at the moderator's discretion. The goal of this forum is to first provide technical assistance and then to educate users on the benefits of free software.
  9. 2 points
    bootz

    SFO - 2.4.3

    From out of the Ashe s, our TBC core has re-emerged, and is now back on the supported cores list. this core is still in limited support phase, until the code has been caught up and stable. When core is given full community support, the community forums section will be re-opened, as well as a bug-tracker. Until then Project is @ our Projects GitHub pages and the public Db is in the downloads section. Feel like helping with the project, Fork and submit a (PR)Pull Request, got something to say... post it on commit comments, see someone on the forums having a hard time ... lend a hand. |Dev Note| Posting to GitHub keep it clean, supportive, and on topic, otherwise comment it will be deleted. Also keep in mind were not all experts at programming some are still beginners, here everyone has a place. That is what the project is for (Educational Purposes), to help teach and to help others learn the selected art of code. There are other projects to use if you just wish to shine your epeen, and troll others you deem under your coding level. On this project you shine by what you commit, and how you help others on this board. We Do not cater to pirate servers, if you need something made custom, go make it yourself, or wait until the sub-forum for custom patches for this core is opened, hell you can even go hug google maybe what you need is there. and above all manage to have some fun. ~Bootz
  10. 2 points
    Due to some recent abuse of our kindness all users must make account to view the forums. Guests will no longer be permitted to view the forums. If you have any trouble creating an account or receiving an conformation e-mail. Just send a message to admin@projectskyfire.org.
  11. 2 points
    Fucking spammers. Guests can no longer post content reports. Thanks assholes for trying to exploit the moderators to clicking on your links to malware sites. Rot in hell!
  12. 2 points
    AriDEV

    SQL Guidelines

    HOW TO GIVE YOUR CONTRIBUTION TO THE SKYFIRE DATABASE PROJECT: It is most important that suggested fixes in this section do not take an enormous amount of time to check and test, otherwise they are useless if they take up as much time as writing them from scratch by a Dev (hence also a waste of time for you suggesting the fix). METHOD: All the fixes should be done in a "New Ticket" on our tracker: http://www.projectskyfire.org/bugtracker Before being able to a do a ticket you need to register, it's simple: http://www.projectskyfire.org/bugtracker/signup_page.php If any aspect of the following method is not PRECISELY followed, your ticket might be deleted. DO NOT WASTE DEVS' TIME AND YOUR TIME: Use the search function to see if the fix you want to provide hasn't already been posted or already accepted and comitted. Use multiple words search if necessary, do not stop at the first attempt just because the search engine does not return any result. (Search both on the forums and on the tracker)Always state the SkyFire Rev you are using, make sure you are using the latest SFDB release and state any addon you are using.Cross-check a bug you found with a clean world DB. Any custom addition or change you may have done on your DB could cause your bug, you never know.Always state the source of your fixes (website, offy account, another project, etc) and provide as many links or details as possible. Always pretend that the Dev reading doesn't know the quest/npc/etc you are trying to fix. MAKE YOUR FIX USEFUL: Always comment your queries for better understanding with the -- format.The ticket will not support too many queries. Attach a link to a sql file to your ticket whenever necessary.DO NOT leave more then 1 space between values or field names.Any INSERT INTO query must be preceded by a DELETE query to prevent import errors. Always write the fields in the query to better trace any structure change and adapt your fix to newer core revs.If you are modifying an existing line, use an UPDATE query. We do not delete and re-insert a full line just to modify a few fields. Be as precise as you can to make sure your query updates ONLY the line expected.If you are writing a text, make sure you use '' instead of ' when writing an apostrophe or it will give an import errorIf you are providing an SQL query fix, please advise if it has been tested or not (be honest). Others might then test it for you and give feedback, this is a Community work! If you have tested your own work.DO NOT CHANGE ANY WDB FIELD! TICKET EXAMPLE: Category: Loot Summary: [iTEM] Broken Longbow (Patch/Fix) Priority: Normal Severity: Minor Description: Missing from Abjurist Belmara's loot Core: b77ae2fd2d7dd81d110674e8ef265db56090dd9d Database: SFDB 11_06_04 Addons: Anticheat 1 Abjurist Belmara should drop Broken Longbow but doesn't. Additional Information: Patch/Fix: http://projectskyfire.org/pastebin/index.php?show=24 Source: http://www.wowhead.com/item=25406 CONCLUSION: Use the wiki to learn more about the DB structure. Although new things are added more quickly than the wiki is updated to explain them, it is very very useful. We will be very harsh if we realise that a suggested fix is just a copy-paste from another project without linking the original post. We do not tolerate leeching. Credits must always be given. Finally, thank you, because if you are reading this it means you really care about helping and wish not to waste the Devs' time! EXAMPLES: Note: This may not be a working code, it is used for this thread as an example. Notice how table and field names are not included in `` symbols, and how values are written plainly, only texts are included in '' symbols. Delete before insert into and always put fields in the query. Wrong: INSERT INTO creature_loot_template VALUES (19546,25406,24,0,1,1,0,0,0);[/SQL] Correct: [SQL] -- Add item Broken Longbow to Abjurist Belmara loot in Netherstorm DELETE FROM creature_loot_template WHERE entry=19546 AND item=25406; INSERT INTO creature_loot_template (entry, item, chanceOrQuestChance, lootmode, groupid, mincountOrRef, maxcount, lootcondition, condition_value1, condition_value2) VALUES (19546, 25406, 24, 1, 0, 1, 1, 0, 0, 0);[/SQL] Make sure your update queries are precise. You might and up changing more lines then you thought of. Wrong: [SQL]UPDATE creature_loot_template SET ChanceOrQuestChance=100 WHERE item=25406;[/SQL] Correct: [SQL] -- Changing droprate for Broken Longbow dropped by Abjurist Belmara from 24 to 100. UPDATE creature_loot_template SET ChanceOrQuestChance=100 WHERE entry=19546 AND item=25406;[/SQL] Remember to use '' instead of a single apostrophe when writing texts, or there will be import errors. Wrong: [SQL]UPDATE page_text SET text='Hello Morgan, you shouldn't be here' WHERE entry=15;[/SQL] Correct: [SQL]-- Correcting text for item William's Shipment. UPDATE page_text SET text='Hello Morgan, you shouldn''t be here' WHERE entry=15;[/SQL] SIDENOTES: Remember that a query must always end with a semicolon( ; ). In general, always import your own queries into you DB to check if there are any import errors and also any startup errors! Various authors (H3ad3r, AriDEV) Template (TrinityCore)
  13. 1 point
    We can only support SkyFire DB. It doesn't have anything to do with conflicts from other projects. We do not have the time to test each DB project nor do we care. When you make a bug report and you are using another DB other than SkyFire DB it will be closed. We can only troubleshoot our own problems with the core/db if it's ours.

Announcements

  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.